Recent content by dakralex

  1. dakralex

    VM failback with cloudinit and ZFS replication fails

    To mitigate this for now, zfs2/vm-101-cloudinit can be removed on the failed node to be able to migrate it back there.
  2. dakralex

    VM failback with cloudinit and ZFS replication fails

    Hi! Thanks for the report! I suppose there is a HA node affinity rule which makes the HA resource failback to the old node. As the node fails, the HA Manager will move the HA resource but not clean up the cloudinit image from the failed node as it would happen in normal circumstances... I...
  3. dakralex

    <span>nodename</span> showing up in front of everything

    Hi! Could you try force refreshing the web interface with Ctrl+F5 or Ctrl+Shift+R? Which version of pve-manager is running on the node?
  4. dakralex

    [SOLVED] PVE 9.1.5: Linux VM Freeze Randomly

    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]...
  5. dakralex

    How to modify cgroup trees of LXCs and VMs?

    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...
  6. dakralex

    conntrack not working when HA is enabled

    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/
  7. dakralex

    Kernel Panic (Dell Server, Debian)

    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.
  8. dakralex

    [SOLVED] PVE 9.1.5: Linux VM Freeze Randomly

    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...
  9. dakralex

    Starting LXC Container with bind mount changes the owner of that mount on the filesystem

    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.
  10. dakralex

    Nach Upgrade von 8.4 auf 9.1.4 und 9.1.5 falsche RAM-Auslastungs Anzeige bei einzelnen Windows VMs

    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...
  11. dakralex

    implausibly old time stamp

    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...
  12. dakralex

    conntrack not working when HA is enabled

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

    implausibly old time stamp

    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...
  14. dakralex

    Starting LXC Container with bind mount changes the owner of that mount on the filesystem

    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.
  15. dakralex

    Display VMs as shutdown on cluster node failure instead of HA-restart

    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...