Windows VMs stuck on boot after Proxmox Upgrade to 7.0

I have 2 VMs running Windows 10 LTS, and one bluescreen after update and reboot, other stuck on boot. I've upgrade Proxmox and reboot my Server and voila, 2 VMs working. This is my packet version:

Code: 
proxmox-ve: 7.2-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.4: 6.4-4
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-5-pve: 5.13.19-13
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.11.22-1-pve: 5.11.22-2
pve-kernel-5.4.124-1-pve: 5.4.124-1
pve-kernel-5.4.106-1-pve: 5.4.106-1
ceph: 16.2.9-pve1
ceph-fuse: 16.2.9-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: not correctly installed
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-4
libpve-guest-common-perl: 4.1-4
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.2-10
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-3
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-5
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
 
ozdjh said:
Ok, thanks @fiona. We were just experiencing the "Windows update never completes" issues. We'll have a look at upgrading pve-qemu-kvm and see how it goes.
Click to expand...
it is not the same problem.
imo, you havn't the efi disk with pre-enrolled keys.
you need to delete it then recreate it, pre-enrolled will be installed then Windows can be updated.
 
  • Like
Reactions: weehooey-bh
This morning my Windows 10 VM was stuck again after automatically installing Windows updates. Is this issue really fixed? Can it have something to do with the kernel version? I haven't rebooted my host in some time.
Code: 
proxmox-ve: 7.2-1 (running kernel: 5.15.53-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-5.15: 7.2-13
pve-kernel-helper: 7.2-13
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.0: 6.0-11
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-3
libpve-guest-common-perl: 4.1-4
libpve-http-server-perl: 4.1-4
libpve-storage-perl: 7.2-10
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-3
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1
 
And this morning my VM was unreachable again. This time with a fully updated and rebooted host. The last my VM showed in de system logs was that it had installed updates, so I guess it was an automatic reboot again.

My backup for this VM fails with the following reason: VM 101 qmp command 'cont' failed - unable to connect to VM 101 qmp socket - timeout after 451 retries
Maybe that message is of any use. When trying to connect the web-console it fails. Any commands to the VM also fails because no connection can be made. I just stop the VM and start it again. That's the only solution.

pveversion -v
Code: 
proxmox-ve: 7.3-1 (running kernel: 5.15.74-1-pve)
pve-manager: 7.3-3 (running version: 7.3-3/c3928077)
pve-kernel-5.15: 7.2-14
pve-kernel-helper: 7.2-14
pve-kernel-5.13: 7.1-9
pve-kernel-5.11: 7.0-10
pve-kernel-5.0: 6.0-11
pve-kernel-5.15.74-1-pve: 5.15.74-1
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.53-1-pve: 5.15.53-1
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-5.11.22-7-pve: 5.11.22-12
pve-kernel-5.0.21-5-pve: 5.0.21-10
pve-kernel-5.0.15-1-pve: 5.0.15-1
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve2
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.3-1
libpve-guest-common-perl: 4.2-3
libpve-http-server-perl: 4.1-5
libpve-storage-perl: 7.3-1
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.3.1-1
proxmox-backup-file-restore: 2.3.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.0-1
proxmox-widget-toolkit: 3.5.3
pve-cluster: 7.3-1
pve-container: 4.4-2
pve-docs: 7.3-1
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-7
pve-firmware: 3.5-6
pve-ha-manager: 3.5.1
pve-i18n: 2.8-1
pve-qemu-kvm: 7.1.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.3-1
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+2
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

qm config 101
Code: 
agent: 1
bootdisk: ide0
cores: 2
description: IP%3A 192.168.10.21
ide0: local-lvm:vm-101-disk-0,size=100G,ssd=1
ide2: none,media=cdrom
memory: 4096
name: beheer02
net0: e1000=DA:EC:F1:D0:41:2F,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win10
parent: Clean_install
scsihw: virtio-scsi-pci
smbios1: uuid=87f8a0a5-af7b-4e94-8041-fa798ae8f79e
sockets: 1
startup: order=6
usb0: host=10c4:ea60
vga: vmware
vmgenid: 9dfcbb19-38a7-4f8b-bcba-faef38f85d1a
 
I also still had this issue with Windows Server on 7.2.11 after a full host reboot on three different hosts this morning.
 
Same here. After Windows reboot triggered by updates, the VMs have an boot issue, unrelated which version: w10/w2k16/w2k19.
They are stuck in boot screen.
 
Last edited:
getcom said:
Same here. After Windows reboot triggered by updates, the VMs have an boot issue, unrelated which version: w10/w2k16/w2k19.
They are stuck in boot screen.
Click to expand...
This is fixed in 7.3.x
 
  • Like
Reactions: fireon
Hi All

just for some extra info.

we have RDS clusters that are set to reboot every evening at 1am.
we see this issue mostly after some windows updates are installed (but not exclusive to updates but they do seem to be a trigger) and then a reboot from OS happens based on the 1am scheduler.

have had this process running for over a year and i can conform that it's not about the uptime of the VM as we reboot every day at 1am.

we have a mix of PVE 7 & QEMU versions so will get them all up to date and report back.

""Cheers
G
 
Morning All

so far a week later Proxmox 7.3.3 performing daily reboots on our RDS clusters we can advise that none have been stuck so far.

we will keep monitoring and if there have been any stuck Win VM's will report back.

thank you.

""Cheers
G
 
velocity08 said:
so far a week later Proxmox 7.3.3 performing daily reboots on our RDS clusters we can advise that none have been stuck so far.

we will keep monitoring and if there have been any stuck Win VM's will report back.
Click to expand...

Hi

Can we assume that everything is still working fine for you on 7.3.3?

Can anyone else here confirm that this problem is resolved when running 7.3.3?
 
Confirm Windows 2022 VM stuck after update even running latest 7.4-3.

After update stuck with "Start boot option".
From cold boot "Guest has not initialized the display (yet)" remains for many minutes (10 minutes or more).
 
Last edited:
DRCURA said:
Confirm Windows 2022 VM stuck after update even running latest 7.4-3.

After update stuck with "Start boot option".
From cold boot "Guest has not initialized the display (yet)" remains for many minutes (10 minutes or more).
Click to expand...
have you rebooted host ?
at least, VMs require shutdown then start (no reboot) to use latest qemu version.
 
_gabriel said:
have you rebooted host ?
at least, VMs require shutdown then start (no reboot) to use latest qemu version.
Click to expand...
I have this issue for windows 10 vms with previous succssful gpu passthrough. im on proxmox 7.4-3

yes i have tried shutting down and also migrating back and fourth between nodes which has not worked either
 
Hello, I am also having the same problem. Everything worked fine until I upgraded to 7.4-3, and now my Windows Server 2019 does not get past the boot screen. I have tried rebooting the VM, the node, and the other node in the cluster, with still no luck. Any help would be appreciated.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back