Search results

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

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

Does the problem also happen with SeaBIOS, or only with the UEFI firmware ?

Did you try replacing the EFI disk ? Another user reported that replacing the EFI disk fixed the issue.

Hi, Adding an EFI disk to the VM fixed the issue, at least on my nodes. UEFI VMs used to boot without this disk, but it seems to be required now, probably because of improved support for secure boot.

Hi, Adding an EFI disk to the VM fixed the issue, at least on my nodes. UEFI VMs used to boot without this disk, but it seems to be required now, probably because of improved support for secure boot.

Well, I tried to remove the files again, and it worked. I still don't understand why. Thanks anyway!

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 ?

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