VM Reboot Issue - VM stuck on Proxmox start boot option screen

[complexplaster27]

Hey everyone subscribed to this thread, I believe @sir4ndr3w and his proposed solution is the way to go, I've switched a fair few of my VMs away from the Writeback Cache mode, specially the ones I know that had the issue and almost a month including Patch Tuesday reboots and they don't experience that issue anymore and restart without a problem.

I'm not sure what the actual cause is but perhaps the Windows server best practices wiki article should be changed to keep the Cache mode on default, especially when using UEFI bios settings?

 

[bluzel]

Hey,
we have exactly the same problem. Some (UEFI) Windows-Server VMs on a ceph storage stuck sometimes at the "Proxmox"-Logo Boot-Screen. Unfortunately all vm disks are on "Default (no cache)" mode. So this doesn't fix anything for us.

 

[complexplaster27]

Yeah so no dice for me still, I wish I knew what the cause of this was because I just have to sit here and wait until it decides to proceed with booting the operating system, surely the solution isn't to use BIOS booting...

Just sits here at max CPU usage:



Hardware settings and boot logo stuck:

 

[prmadmax]

Yeah so no dice for me still, I wish I knew what the cause of this was because I just have to sit here and wait until it decides to proceed with booting the operating system, surely the solution isn't to use BIOS booting...

Just sits here at max CPU usage:

View attachment 84066

Hardware settings and boot logo stuck:

View attachment 84068View attachment 84067

I recently had this high cpu usage and editing my processor and enabling numa support fixed it for me, still no idea why.

 

[complexplaster27]

I recently had this high cpu usage and editing my processor and enabling numa support fixed it for me, still no idea why.

I really wish this was the solution but I have a lot of my VMs with numa support enabled still happens. The same VMs that all have BIOS boot instead of UEFI whether or not they have numa enabled or not never experience this problem.

So far the only real workaround i've had was installing this which will forcefully stop and start the VM stuck in that state, as it usually happens overnight when nobody is around this at least ensures the VM is up and running when the day starts (script), not ideal but I have no other ideas on what to do or what kind of troubleshooting needs doing.