Search results

Thanks for clarification ! (and I was afraid you'll confirm it :( ) About setting the core count to "0" - GUI doesn't even allow this. Is that a "supported" feature, or something that works from config level just because it was overlooked and in near future it could break all my CT ? Also for...

Hi, I was researching intel P&E arch issues & config with proxmox, and there was a statement (at least for PVE7) that on startup, container cores are allocated and can't be switched over during operation if for example higher load is required. here at 6:43 So my questions are: 1. is that true...

☝️ namely: EDID block 0 is all zeroes just eating 100% of one core and floding the syslog. It’s an old issue that rears it’s head from time to time on headless and some ipmi chips (for me an old supermicro mobo)

Hi, If after an upgrade from 7 to 8, or a fresh install of your interface seem to die randomly (minutes to hours), and only indication you see in your syslog is: NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out possibly you've got a Realtek network interface that seem to be affected...

Nope, didn't ask about default target link, however I thought that I will report it.

To admin: if I'm wrong here, please delete this thread. Hi just a slight request, can somebody add in 7to8 documentation: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8 that after upgrade the default target may need changing back to multiuser ? All of my nodes on upgrade changed to graphical...

bump ? Any additional logs I can search for and provide in this case ? Asking before those will get rotated out.

I've removed the description section since includes some sensitive information. $ pct config 113 --current arch: amd64 cores: 4 features: nesting=1 hostname: data-logger memory: 4096 net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=6A:7C:73:9E:7A:F2,ip=dhcp,type=veth onboot: 1 ostype: ubuntu...

So this seems to happen after a backup. For some reason backup fails, and finishes with "unexpected status" INFO: Starting Backup of VM 113 (lxc) INFO: Backup started at 2023-07-11 06:00:14 INFO: status = running INFO: CT Name: data-logger INFO: including mount point rootfs ('/') in backup...

Hi, I'm getting similar issue, however in happens from time to time on same container. Container is NOT really funky, has no special options, it's unprivileged. Any advise on how I could diagnose why this specific container get's locked for no reason ?

Better and continuously maintained documentation. Continuous automated testing. Also you make it sound like somebody is suggesting implementing orbital guidance. Is that's why vm vs ct shutdown varies greatly in reliability in web gui vs cli ? is that why some have scripts walking the nodes...

That workaround is really suboptimal since fast storage nodes will be slow down by a slowest nodes in cluster. Why I would slow down backups to 50MBps if some nodes hapille can handle 4GBps ? and still have the slow nodes suffer.

If people want different compressions - let’s give them that, BUT i would still strongly opt for NO Compression - since pbs can get hammered down with decompression tasks, and in many cases that significant slow down for maybe 5% space saving is pointless.

Forgot to add: “through GUI” Also when I tried manually setting it in config corosync would often ignore / remove this part. At the moment, only reliable was is to assign large amount of votes to one node that is always on, but when this one goes for down for updates, the cluster goes down.

Hi, After some testing and feedback from proxmox staff, I would suggest: 1. reenable change of compression level during backup to PBS (now it's locked to ZSTD, but in the past it allowed uncompressed). At this point forcing compressions can make CPU bottleneck and also increase load on the node...

Hi, It would be nice to allow admins of a cluster to define either: - a minimum votes required for a quorum (yes, admins might be aware of pitfalls and are prepared to deal with consequences) OR - define behaviour when quorum is not achieved - current "stop everything and just sit there" is a...

First @Dunuin, thanks for confirming that. Second, that sounds sub optimal, if backing up CT (where I assume PVE and PBS is aware of internal file structure) there could be an master hash for a file, stored somewhere - and where backup is being performed, PBS only needs to garnish PVE with list...

That is maybe a one VM in prod. Everything else is filled out with files starting at one gig. And test CT / VM was filled with similar size files. Bottom line is my prod doesn't compress or dedup (all pools have compression disabled because there is no point for it). I know that my prod might be...

No I didn't because I don't test it now on anything close to production hardware ... but it looks like soon I'll have to zone out a rack and start real testing (at least now I now that CT's have some backup limitations, but will need to compare production performance vs vm's). What I have...

I'll give you that. And also I'm starting to see why. Anyway, back to the backup. I still believe that backup process is cpu bottle necked (even if it's not compression / decompression). It's visible on scrap test setup - makes me wonder how much horse power a pbs server will need when in...