In the end, this was mostly a BIOS issue. I have downgraded to the latest non-Beta version 5.60 for my motherboard (ASRock X570M Pro4), and now even on the latest kernel I can get full p-state, including passive mode.
Hmm.. Komisch. Ist das normal, dass zum Backup eine VM kurz eingeschaltet wird?
Feb 08 04:19:56 pve02 pvescheduler[1163243]: INFO: Starting Backup of VM 512 (qemu)
Feb 08 04:19:56 pve02 systemd[1]: Started 512.scope.
Feb 08 04:19:57 pve02...
Running stuff in an unsupported setup does not count. You also cannot sink your car in the river and complain to the manufacturer, that the car did not float.
How would having a subscription solve the problems you faced?
The resolving commit for mentioned vioscsi (and viostor) bug was merged 21 Jan 2026 into virtio master (commit cade4cb, corresponding tag mm315).
So if the to-be-released version will be tagged as >= mm315, the patch will be there.
As of me...
Well, maybe so, but a breaking change such as this one (which is NOT the first by a long Shot) which causes Containers to not start should be treated more carefully and not just forced upon Users.
It clearly doesn't work. System is uptodate...
copy folder and all fiels from
/var/lib/pmg/templates
to
/etc/pmg/templates
Edit the files: /etc/pmg/templates/main.cf.in
at the smtpd_sender_restrictions part,
add below content:
check_sender_access regexp:/etc/postfix/Blocked_Sender_Domain...
Most probably: https://bugzilla.proxmox.com/show_bug.cgi?id=7271
Please try downgrading pve-container like that apt install pve-container=6.0.18 which should fix the problem. A patch is already on the way.
Meistens liegt es an nicht zuzverlässigen Netzwerk-Storages (wie bei dir die NetApp). Hier wird es zu Problemen & Abbrüchen bei den Backups kommen. Bitte probier deine Backups einmal durch, nur weil Sie da aufgelistet sind heißt es ja nicht, dass...
Well, maybe so, but a breaking change such as this one (which is NOT the first by a long Shot) which causes Containers to not start should be treated more carefully and not just forced upon Users.
It clearly doesn't work. System is uptodate...
I tried everything suggested above, nothing helped. Only adding this line worked for me.
ProxMox 9.1.4, GPU 3090 pass-through to Win11 VM, for Star Citizen EAC.
I confirm I was also just affected by this
I opened another Issue a few Minutes ago about it:
https://forum.proxmox.com/threads/lxc-fails-to-start-when-using-read-only-mountpoint.180440/
I have a Mountpoint /tools_nfs that is mounted read-only on most of my Systems, and I want to be able to pass it to each Container.
It used to work OK until now.
I suspect one of the last System Updates messed it up :( .
Attached is the Debug...