Search results

Hi! This is a known issue and tracked by the Bugzilla entry [0]. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7053

Hi! Es scheint als gäbe es insgesamt Lese/Schreibfehler auf dem Speichermedium, welches Dateisystem und Speichermedium wird unter / und /mnt/pve/backup-opnsense/ verwendet? Gibt der syslog mehr Aufschlüsse über die I/O errors über die hier berichtet werden? Ist diese Proxmox VE node in einem...

Could you try upgrading to pve-container version 6.1.2, which is currently available on the pve-no-subscription repo? This makes the attribute preservation code opt-in via the "Keep attributes" flag on mountpoints and should resolve this issue entirely.

Hi! I'm not sure whether this will fit into the concept of HA itself, but if the guest is already on shared storage only, then it easily possible to recover that VM to a running node by just moving the guest's configuration file to the running node without needing to configure HA for that...

Hi! As for the other post, even though the Proxmox forum can be a good place to start some discussions or see whether other users are running into some scenario as well, our Bugzilla [0] is the best place to share requests for feature enhancements and bugs. Please make sure to check first if a...

Hi! Even though the Proxmox forum can be a good place to start some discussions or see whether other users are running into some scenario as well, our Bugzilla [0] is the best place to share requests for feature enhancements and bugs. Please make sure to check first if a similar bug already...

In total, the HA stack requires users to have Sys.Audit on / to view the HA status and view the HA resources and HA rules, and requires users to have Sys.Console on / to edit the latter two. It's important that it is the ACL path / as there's no fine-grained permissions for the HA stack yet so...

Dieser Bug sollte mit pve-container Version 6.1.2, verfügbar in der pve-test repository, behoben sein.

Hi! I assume that /dev/sda through /dev/sdh are exposed through the SATA controller? At least these are reported after VM 100 is started: Feb 12 18:31:31 nasty pvedaemon[3129]: start VM 100: UPID:nasty:00000C39:00001EA3:698E1C83:qmstart:100:root@pam: Feb 12 18:31:31 nasty pvedaemon[2954]...

Hi! To create HA resources (i.e., add VMs/containers to the HA stack), a user needs the Sys.Console permission on path /, see the POST request description in [0]. The permissions for the HA stack are very coarse grained at the moment, but there is a Bugzilla entry for the feature request to add...

Hi! One more thing, is it possible that the ignored HA resource's underlying guest has "Start at boot" set? Otherwise I could not reproduce the issue at hand and more information about a minimal and working reproducer would be needed to investigate further.

Hi! As far as I can remember, there was a patch applied for that specific SATA controller. Could you post the syslog before, at and after the VM hangs and the output of lspci -s 0000:01:00 -vvnnk?

Hi! Das dürfte mit den Bugzilla entry [0] zusammenhängen, aber hat eine etwas andere Ursache. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7271

Hi! Which package versions are the source and target node of the VM running on? Is there more information in the syslog of the source or target node in that time frame? pveversion -v returns a full list of the package versions of a node.

Hi! This error should be resolved with pve-container version 6.1.1 available on the pve-test repository.

Thanks for the reports! The errors described by @zhouu, @capnspacehook and @agross should be fixed with pve-container version 6.1.1 available on the pve-test repository.

Yes, the problem from your log is different from the one that is fixed by the linked patches, but there is already a Bugzilla report for this [0] and this will be fixed by a separate patch set. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7271

Hi! Thanks for the report! Sent a patch in for review to fix the issue [0]. [0] https://lore.proxmox.com/pve-devel/20260204091740.102914-2-d.kral@proxmox.com/

Hi! The first warning indicates that the iothread option is set on a disk that is not a virtio disk or a virtio-scsi-single controller. The error which causes the VMs fail to start is the second error about the bridge not being set up correctly. Does the syslog indicate whether the network...

I'm not sure when the reboot happened here, did it happen before the syslog excerpt (before 2026-02-03T14:52:36.278369+01:00) or in the middle at 2026-02-03T14:56:46.362744+01:00? If it's the latter I don't see vm:118 being started here after the reboot. Can you also post the HA configuration...