Search results

If the HA status report from above is the exact same as it was before setting pve1 in maintenance mode (the HA status report's timestamp is later than the syslog), then I cannot reproduce it with this configuration either. Are you sure that the rules are complete/not in conflict with other...

Thanks! If it's possible, it would be great to have a more complete reproducer for this to investigate the issue. The names can be changed, the only important part is that the changed names have the same alphabetical ordering (e.g. SN140 -> pve2, PVE003 -> pve1).

Hi! I have recreated your exact setup as described by the status output and rules config above and couldn't reproduce this either. What should happen is that as soon as pve1 is put in maintenance mode, the vm:102 will select a new node (it will be pve2 here as it's empty), vm:104 will select...

See my reply above, the syslog on the current HA Manager (master) node should show a regular error that the HA groups couldn't be migrated and the reason why. This should point you in the direction what is missing (e.g. maintenance mode, not quorate, non-existent nodes, etc.). All nodes must...

Hi! The versions of the node seem a bit out of date, pve-manager 9.0.5 is from mid-August. Could you try upgrading the nodes to see if this is fixed in a more current version? The HA groups should have been migrated with the upgrade from PVE 8 to PVE 9 automatically. The HA Manager tries this...

Was there any console output for the qmstart task for the VM 410? Is there anything shown at boot on the machine? Is the boot disk (scsi0) still intact (e.g., no fs corruption, system files are readable)? Else I could not see anything off from the syslog itself between start and end of the...

I cannot see anything obviously wrong about the config. Can you post the VM start log and the syslog around the VM startup?

From the error message it seems like that a random byte sequence was introduced... When you restart your machine / restart the pveproxy/pvedaemon services, then the Perl files are recompiled. I have never seen something similar before and can only guess that there must have been some corruption...

+ What is the VM config of the VM that fails to start (e.g. cat /etc/pve/qemu-server/<vmid>.conf)?

Hi! Have you installed any additional software, which actively uses the landlock kernel module? This warning is only reported, if one of the landlock syscalls (landlock_create_ruleset, landlock_add_rule, landlock_restrict_self) are trapped directly and AFAIK we don't use them directly. I'll...

Hi! LLMs are inherently incapable of maintaining any semantic or logical relationships and will interpolate beyond facts. libpve-guest-common-perl 6.0.2 is the correct version for Proxmox VE 9.1. Has the source file /usr/share/perl5/PVE/QemuMigrate.pm been changed in any way? It seems like it...

Hi! The HA group to HA node affinity rules migration is done every 6 HA rounds, i.e., around every minute with an HA round lasting ~10 seconds. To be sure that everything is fine, it will only do the migration if the cluster is quorate, all nodes are online, the LRMs are active or idle, and all...

Hi! Thanks for the report! This should be resolved with proxmox-kernel-6.17.2-2-pve (see [0] for more information). [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7083

Hi! Thanks for the input! This was and is still planned for both types of resource affinity rules, you can track the status here [0]. It's always helpful to have more views on this, so feel very free to add your perspective there as a comment. Hm, can you send an excerpt for the relevant HA...

Great that it doesn't freeze anymore, hope it stays that way! This is also a good time to check if there are any updates to the BIOS/firmware for the mainboard.

Hi! Can you share the specific VM config with the expected and actual behavior? If there is no given boot config property, then the VM will fallback to the legacy boot order default, which is CD-ROMs, bootable hard disks (i.e. set with the deprecated bootdisk config property) and network...

Hi! How did you try to gather the logs? Are there no logs at the end for e.g. journalctl -b <boot-nr>? If this is block-related in any way it might happen, because the kernel panics and cannot write to any storage media anymore. In these cases, setting up some form of external console (e.g...

Hi! Proxmox VE abstracts away paths with storages, so that users can store VM images, backups, etc. on various storage types (e.g. ext4, zfs, LVM, RBD, iSCSI, etc.). There's a help command to show you the correct command line usage of the command: qm help importdisk USAGE: qm disk import...

Hi! Thanks for the input! Unfortunately, this fails on any device, which does not have the capabilities. We usually only put values in the time series, which are collectable by any system independent from the hardware configuration (e.g. generic task utilization, pressure), especially since...

Hm, unfortunately it doesn't seem like there's anything valuable in those logs either. I guess that 4ba997d4d49c4298937fd85fb41c866a was the boot which ended in the kernel stack trace above (at least from the timestamps and the abrupt end of log)? As this seems block-related, you could try to...