I apologise, I miss interpreted the log, for Linux vm virtaio driver not an issue (mostly).
I would consider using Virtio and investigating further, e.g:
Check journalctl log in pve and vm.
consider enabling multiqueue.
Make sure the path...
I wonder if this is might be due to page cache pressure or dirty page writeback stalls? A reboot might clear transient memory fragmentation.
Did you notice it occurs after sometimes or it was always like this?
I have no experience on this, but I found this thread which explains it can causes issue:
https://forum.proxmox.com/threads/web-ui-shell-disconnects-with-code-1006-%E2%80%93-root-cause-igmp-proxy-snooping.178761/
You are right, for corosync the recommendation is to have latancy below 5ms.
I would not activate HA in such setup because it might lead to a lot of fences (reboot).
Would not be wrong, ensuure low latency.
if switch support qos then you can attempt too configure the switch so that it prioritise corosync traffic.
Do not forget to configure migration network, Ideally should be on a separate nic as well...
Found the issue - was my fault - from an prior installation on other hardware (without boss card), there was still "GRUB_CMDLINE_LINUX="root=ZFS=rpool/ROOT/pve-1 boot=zfs" in the grub-default-file…
Thanks for comments!!
Thank you for the suggestion.
Unfortunately I cannot test with an older kernel at the moment because this is my production homelab. However, I can schedule a maintenance window and test both kernel 6.14 and 7.0.14-8-pve if this would help narrow...
I had a different issue while importing Debian11 and Ubuntu 12, for me it didn't boot at all, and only after switching to SATA it worked.
therefore this is Just my 2 cent here, I would try since its quick change to switching the virtual disk bus...
Could you share:
~# efibootmgr -v
Could it be related to:
https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#GRUB_Might_Fail_To_Boot_From_LVM_in_UEFI_Mode
?
From which version you upgraded?
So, you didn't need to wait a lot to see your speculation was correct:
https://forum.proxmox.com/threads/proxmox-virtual-environment-now-available-for-64-bit-arm-arm64.185526/
We are excited to announce the first release of Proxmox Virtual Environment with official support for a second CPU architecture: 64-bit ARM (arm64/aarch64). Until now, Proxmox VE was available for x86-64 (amd64) only.
Proxmox VE 9.2 for arm64...
Offline storage migration is not yet implemented for qcow2 on LVM: https://bugzilla.proxmox.com/show_bug.cgi?id=7554
You can use online migration instead.
Thanks for the input, you are completely right that a raw socket is not a Telnet server, and that it can be accessed via nc or socat.
I will edit it with that.
The reason for doing this is i encountered for specific external automation and...