Windows 21h2 updates borks Windows VM

J

JLH1825

New Member
Oct 20, 2021
13
0
1
54
Have a windows Vm, that's been working great until the latest windows updates that were run. Afterwards the VM will not start and I get an error as attached. If I roll back to a backup where the update is not installed all work great.

Any ideas?

Thanks!

J
 

Attachments

  • Screen Shot 2021-12-30 at 12.41.07 PM (1).png
    Screen Shot 2021-12-30 at 12.41.07 PM (1).png
    56.1 KB · Views: 17
Hi,

Can you reproduce the issue? I think the issue itself is on the Windows side not from the PVE side.
 
Moayad said:
Hi,

Can you reproduce the issue? I think the issue itself is on the Windows side not from the PVE side.
Click to expand...
I just can't get any of my Windows 10 VMs to start at all now , I just get a QEMU returned a error 1 , so something is now up ?
 
Moayad said:
What the pve-kernel version are you using pveversion -v?
are you using pve-kernel 5.13.19-2? if so please try to use the pve-kernel 5.15 [0] version


[0] https://forum.proxmox.com/threads/opt-in-linux-kernel-5-15-for-proxmox-ve-7-x-available.100936/
Click to expand...
Output of PVEversion - What's the best way to upgrade to the new kernel? Do I need to upgrade PVE first?


proxmox-ve: 7.0-2 (running kernel: 5.11.22-4-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-5.11: 7.0-7
pve-kernel-helper: 7.0-7
pve-kernel-5.11.22-4-pve: 5.11.22-8
ceph-fuse: 15.2.14-pve1
corosync: 3.1.2-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.21-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-6
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-9
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-2
pve-firmware: 3.3-1
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-13
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1
 
Hi , I think you need to add the pve-no-subscription repository , before you can upgrade to 7.1.8 which I think is the latest .

Which you need to a update / upgrade after and reboot , which should update to 7.1.8 which includes the new kernel.
 
Last edited:
peter247 said:
Hi , I think you need to add the pve-no-subscription repository , before you can upgrade to 7.1.8 which I think is the latest .

Which you need to a update / upgrade after and reboot , which should update to 7.1.8 which includes the new kernel.
Click to expand...
Sorry, didn't follow. Add the No sub repository then just upgrade to latest version and that should have the new kernel?
 
birdy said:
You're already on PVE7x so I"m assuming your repositories are ok, but just to check could you please provide output of:

apt update

If you want to try the 5.15 kernel please check this:

https://forum.proxmox.com/threads/opt-in-linux-kernel-5-15-for-proxmox-ve-7-x-available.100936/
Click to expand...
Output from apt update:
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.us.debian.org/debian bullseye InRelease
Get:3 http://ftp.us.debian.org/debian bullseye-updates InRelease [39.4 kB]
Get:4 http://download.proxmox.com/debian/pve bullseye InRelease [3,053 B]
Get:5 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 Packages [191 kB]
Err:6 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 144.217.225.162 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@hitprox:~#

I did add the no sub repository in the gui. This appears to show that it is enabled?
At this point do I just update and I'll eventually get the new kernal?

Thanks all!
 
JLH1825 said:
Output from apt update:
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.us.debian.org/debian bullseye InRelease
Get:3 http://ftp.us.debian.org/debian bullseye-updates InRelease [39.4 kB]
Get:4 http://download.proxmox.com/debian/pve bullseye InRelease [3,053 B]
Get:5 http://download.proxmox.com/debian/pve bullseye/pve-no-subscription amd64 Packages [191 kB]
Err:6 https://enterprise.proxmox.com/debian/pve bullseye InRelease
401 Unauthorized [IP: 144.217.225.162 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@hitprox:~#

I did add the no sub repository in the gui. This appears to show that it is enabled?
At this point do I just update and I'll eventually get the new kernal?

Thanks all!
Click to expand...
That looks o.k now and you should be up to the latest version . ( a guess you haven't a subscription )

Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bullseye/InRelease 401 Unauthorized [IP: 144.217.225.162 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

This can be stopped by add a # in front of the "deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise" in /etc/apt/sources.list.d/pve-enterprise.list

eg - nano /etc/apt/sources.list.d/pve-enterprise.list

But you will still get the nag screen .
 
Last edited:
JLH1825 said:
I did add the no sub repository in the gui. This appears to show that it is enabled?
Click to expand...

Default the Enterprise repository is enabled. If you don´t have a subscription you have to configure the no-subscription repository.

At the monent you have both (Enterprise and No-subscription) active. You can change this either by editing the config files (like peter247 wrote) or in the GUI (Datacenter->Node->Updates->Repositories).

JLH1825 said:
At this point do I just update and I'll eventually get the new kernal?
Click to expand...

Exactly. :)
 
birdy said:
Default the Enterprise repository is enabled. If you don´t have a subscription you have to configure the no-subscription repository.

At the monent you have both (Enterprise and No-subscription) active. You can change this either by editing the config files (like peter247 wrote) or in the GUI (Datacenter->Node->Updates->Repositories).



Exactly. :)
Click to expand...
I think it is a yes and a no .
You will be on the latest version on proxmox stable , But the version of the kernel for that is "proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)"
So if you want kernel 5.15 you need to do a "apt update && apt install pve-kernel-5.15" in the Shell .
BUT ... I'm not sure if the 5.15 kernel will fix your windows 10 blue screen problem.
 
Last edited:
Hi folks...

I finally got around to updating proxmox it is now at latest stable and the 5.15 kernel. However this doesn't seem to fix the issue. No, even if I restore an old backup of the VM, It starts and then immediately updates and I get the blue screen. Screen Shot 2022-02-03 at 12.01.03 PM.png

I'm not able to start in safe mode using the startup options. Kind of stuck.
Any ideas?

Thanks!

J
 
You must log in or register to reply here.
Top Bottom