Windows VM freeze on start after reboot

[GeorgeCZZZ]

Hello, I'm new to proxmox, I use only ESXI before, and never had such issue. On two my VMs, with UEFI Bios, I have problem, that after reboot (like Windows update do), VM doesnt start. It stuck with 50% Cpu utilisation and black screen. In Spice is flashing screen. I'm on PVE 7.0.13 . What can couse this?
When I make normal shutdown, it shutdown corectly. When I start VM, it start coretly. Only restart is problem.

 

[GeorgeCZZZ]

Only message in syslog in time when VM reboot itself and doesnt start is this: Nov 10 22:24:43 px1 pvedaemon[1666325]: VM 103 qmp command failed - VM 103 qmp command 'guest-ping' failed - got timeout

Is there some VM log with more informations?

 

[rodww]

I noticed the same problem... I haven't figured out the cause yet either. I had to power off and back on a couple VMs that were stuck in this state trying to reboot from an update. Anyone have any thoughts on this one? The VM just flickers black and white indefinitely. I did notice one thing interesting - for me it only seems to happens to VMs with standard UEFI (one with no EFI for TPM 2 attached) and not with BIOS VMs. However hoping to avoid having to create a new VM for these with one of those configs if there is a fix.

 

[GeorgeCZZZ]

I noticed the same problem... I haven't figured out the cause yet either. I had to power off and back on a couple VMs that were stuck in this state trying to reboot from an update. Anyone have any thoughts on this one? The VM just flickers black and white indefinitely. I did notice one thing interesting - for me it only seems to happens to VMs with standard UEFI (one with no EFI for TPM 2 attached) and not with BIOS VMs. However hoping to avoid having to create a new VM for these with one of those configs if there is a fix.I think, those

Seems, bug can affect i legacy bios - https://forum.proxmox.com/threads/w...ing-reboots-after-patching.99547/#post-429926 , as I think that those people have simmilar problem like we.

 

[rodww]

Oh, ok thanks. Touch wood, I haven't had this issue on my legacy BIOS VMs yet.

 

[GeorgeCZZZ]

Another guy who has similar issue: https://forum.proxmox.com/threads/proxmox-ve-7-freebsd-guest-reboot-shutdown-problem.99680/ .

 

[ayozeve]

i 've the same problem... i upgraded to 7.1.4 from 6.4 and when i reboot from a vm with Windows Server 2012 R2 (UEFI) it show black screen and it not boot anymore. If i reboot from proxmox (with qemu guest agent) it boot correctly.

UPDATED: I have just to removed efi disk and added another one and it solved to me !!!!

 

[tarkal]

I noticed the same problem... I haven't figured out the cause yet either. I had to power off and back on a couple VMs that were stuck in this state trying to reboot from an update. Anyone have any thoughts on this one? The VM just flickers black and white indefinitely. I did notice one thing interesting - for me it only seems to happens to VMs with standard UEFI (one with no EFI for TPM 2 attached) and not with BIOS VMs. However hoping to avoid having to create a new VM for these with one of those configs if there is a fix.

I ran into the same problem where the VM with Windows 10 did not restart correctly and the SPICE screen flashed. The resolving came after I changed the version of the VM chipset from Hardware - Advanced - pc-i440FX-6.1 to pc-i440FX-6.0 pve is ver 7.1-8

 

[lps90]

I ran into the same problem where the VM with Windows 10 did not restart correctly and the SPICE screen flashed. The resolving came after I changed the version of the VM chipset from Hardware - Advanced - pc-i440FX-6.1 to pc-i440FX-6.0 pve is ver 7.1-8

yeah, v7.1-8 is problematic.
My VM's are with problems and the entire dedicated server keeps crashing with this latest proxmox version.
I do not recommend it at all.
I think i'll need to format my dedicated server with an older proxmox version to solve all the problems.

 

[tom]

yeah, v7.1-8 is problematic.
My VM's are with problems and the entire dedicated server keeps crashing with this latest proxmox version.
I do not recommend it at all.
I think i'll need to format my dedicated server with an older proxmox version to solve all the problems.

There are no known issues which are not addressed and fixed or can be workarounded, so please tell a bit more with which package do you see issues (v7.1.8 is not that clear).

 

[lps90]

There are no known issues which are not addressed and fixed or can be workarounded, so please tell a bit more with which package do you see issues (v7.1.8 is not that clear).

I already described it.
Read my detailed info already published in other thread.
Cause i'm still waiting for an answer or some kind of feedback.
Link: https://forum.proxmox.com/threads/proxmox-v7-1-8-problems.101423/

 

[tom]

I already described it.
Read my detailed info already published in other thread.
Cause i'm still waiting for an answer or some kind of feedback.
Link: https://forum.proxmox.com/threads/proxmox-v7-1-8-problems.101423/

I answered in your thread.

It makes no sense to add your LXC container issue to a thread about a Windows guest as qemu VM.

 

[lps90]

I answered in your thread.

It makes no sense to add your LXC container issue to a thread about a Windows guest as qemu VM.

LXC issue?
My issue is with windows VM!
(The truth is the dedicated machine is randomly rebooting after some time... like described, this latest update caused all this problems...)
Anyway, i see there will be no correction update soon, so i'll format my dedicated machine with an older proxmox version without this kind of problems. Thanks for your time.