Search results

Hm, then it could be a kernel panic inside the VM that is causing it and isn't written to the disk anymore if it doesn't show up in the syslog, e.g. journalctl -b -1... Maybe you can setup netconsole [0] [1] or some other log-persisting setup to capture the log when the freeze happens. [0]...

Hi! There is no simple way to move VMs and CTs under a single root cgroup as for VMs the code already depends on the VM's cgroups to be under the /qemu.slice cgroup and the /lxc cgroup is given by LXC itself, which has many intricacies that make this a requirement. So it can only be limited for...

I've proposed a patch for this on the mailing list [0]. [0] https://lore.proxmox.com/pve-devel/20260225143514.368884-1-d.kral@proxmox.com/

Hi! It seems like the initramfs is missing at boot, are there any other kernel versions installed on the system and bootable by selecting them in the bootloader menu? Booting another version and then reinstalling the one that panics should resolve this issue.

I don't know IPfire itself, but are there any logs within the VMs themselves? As their website states that they are based on Linux, the VMs own syslog or other logs could give some hint what the reason for the freezes are. 4 GiB seems good enough for such a use case, but might that be something...

I'm sorry, the pve-container package in version 6.1.2 is still in the trixie/pve-test repo as of now, if you want to try the new version to fix the issue.

Grundsätzlich ist eine Auslastung über 100% möglich, da nun seit Proxmox VE 9.0 auch die Host Memory Usage hinzugerechnet wird, was besonders bei VMs ohne Ballooning bedeutet, dass das konfigurierte, maximale Memory Assignment überschritten werden kann. Siehe dazu [0]. Läuft auf dem Windows...

Ja, grundsätzlich hat auch eine einzelne Proxmox VE Node eine pmxcfs Instanz, um /etc/pve mit den gleichen Pfaden wie in einem Cluster Environment zu Verfügung zu stellen. In wie weit wird das System auf read-only gesetzt? Ist das Dateisystem dann nur mehr als ro gemounted? Zeigt ls -lha...

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?