This seems to be exactly the same issue as the one described on this thread. Enabling SR-IOV in the BIOS seems to help: I was able to start all the VMs and only got the soft lockup alert on startup for the first VM.
IMHO this issue is probably caused by a bug in network drivers or the network...
I am using Proxmox VE 7.1 (up to date) on two brand new Atom C3758 motherboards with integrated Intel X553 GbE adapters. The servers were migrated from C2758 motherboards which were working fine until their replacement.
Trying to start a KVM guest on those nodes results in a timeout error...
Thanks. I'll use pvenode in the future.
I made a typing mistake. The command I ran had the correct file name (in fact, I used autocompletion, which does see the ghost file, while rm does not).
Any idea about how I can remove those files before I start again using pvenode ?
I'm running a freshly installed & up-to-date 3-node Proxmox VE 5.3 cluster. Everything was fine until I tried to deploy custom SSL certificates for the web UI.
The process detailed in the documentation implies to add new files (pveproxy-ssl.pem & pveproxy-ssl.key) to the...