I see these messages
Jul 05 11:56:26 host3 kernel: x86/split lock detection: #AC: kvm/797055 took a split_lock trap at address: 0xfffff80016761edd
as well, but I don't notice any storage or connectivity issue (VM's storage is located on local disks).
Should I be concerned about these messages?
Since the upgrade to kernel 5.15.x, due to issue like these,
I would like to try to install and boot the 5.13 kernel.
apt install pve-kernel-5.13...
Try to perform an fstrim insidie the VM with 10tb disk.
But I suspect that this is due to zfs block size and/or how data replication works on raidz1, that is a bit complicated to explain for me (write amplification and so on).
Installing Proxmox 6.1-2 instead of 6.2-1, I'm able to boot the server.
Then, I updated the system with apt-get dist-upgrade (enabling the no-subscription repository), and now I'm able to boot in pve 6.2-10