Windows 10 VM Hypervisor error after Windows Update

paulmorabi

Member
Mar 30, 2019
81
8
13
45
Hi,

i'm not sure what happened with my prior post as it possibly got deleted. I am using a Windows 10 VM in latest Proxmox and after applying the May 2020 update recently am suddenly unable to boot. I get a "STOP CODE: Hypervisor Error". I can't roll back to any previous feature or quality version and can only get a terminal.

I did try to enable WSL2 in Windows 10 but this failed because it saud the hypervisor was not supported so I left it at that.

My VM config is:

Code:
agent: 1
args: -cpu host
balloon: 0
bios: ovmf
boot: dcn
bootdisk: scsi0
cores: 16
hostpci0: 1c:00,x-vga=1,pcie=1
ide2: none,media=cdrom
kvm: 1
machine: q35
memory: 16384
name: Windows
net0: virtio=96:DB:30:3F:3F:91,bridge=vmbr0
numa: 1
ostype: win10
scsi0: local-lvm:vm-100-disk-0,cache=writeback,iothread=1,replicate=0,size=200G,ssd=1
scsi1: shared:vm-100-disk-0,backup=0,iothread=1,replicate=0,size=500G
scsihw: virtio-scsi-single
smbios1: uuid=6c528219-7221-4008-b880-7b23b7302b2e
sockets: 1
usb0: host=1e7d:2f76,usb3=1
usb1: host=04d9:fc58,usb3=1
usb2: host=1-3,usb3=1
vga: none
vmgenid: 17177e2a-bb1b-4326-8763-eed5028c9a61

Host is a Ryzen 2700.

I saw on the Proxmox documentation that passing +svm is supposed to enable nested virtualization but this did not work. Is there any other flags I can try?

Any help would be really appreciated!
 
Hi,

as you wrote WSL2 is not compatible. So you have to get rid of this binary in the VM.
There is nothing that you can do from Proxmox VE side.