Search results

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

Hi! Seems like there was something in the way of writing it to disk, you can try to gather the log on a separate console, e.g. netconsole [0], so that the information persists if there block io is unavailable. [0] https://www.kernel.org/doc/Documentation/networking/netconsole.txt

It would be helpful for the kernel stacktrace to be a bit longer, e.g. upload a whole boot and crash log (journalctl can also export a log from a whole boot). I can only see that ZFS seems involved, maybe some ZFS I/O worker panicked? Which CPU is installed on that system?

Either way, I'd first check if your hardware is alright, e.g. all cables and the RAM modules are connected correctly and aren't loose, there BIOS configuration is reset (no overlocking, etc.), and so forth. If it doesn't fix the problem, then a full boot log would be beneficial in finding the...

Hi! journalctl with PAGER set will usually open in that pager (typically it's less) and therefore you need to page down for journalctl --since="1 hour ago". For a better view of the log from the end of the last boot, you can run journalctl -b -1 -e. What is the output there?

From the provided log in log-pve540-1.zip it also seems like there's quite a few connection issues, e.g. to the InfluxDB right at the start. I assume that proxmoxW540 is one of the nodes that has the problems starting up? Is the network stable for that/these nodes?

Are these all nodes in the cluster? What does pvecm status output? Keep in mind that it is not recommended to have a even amount of nodes in a cluster, see e.g. [0]. This seems like a clustering issue first of all. Are the HA resources with node "---" running somewhere unnoticed? Or were these...