Windows 11 guest nested virtualization not working

proxsea

New Member
Jul 9, 2024
1
0
1
* Proxmox VE 8.2.2
* Windows 11 Pro enterprise guest (up to date)
* i7-8750H Coffee Lake

I can see my host CPU in guest task manager, it also says virtualization is enabled:
1720545774662.png

Here is my conf:
Code:
agent: 1
bios: ovmf
boot: order=ide0;ide2;net0
cores: 4
cpu: host,hidden=1
args: -cpu 'host,+svm,-hypervisor,hv_passthrough,level=30,-waitpkg'
efidisk0: win11_storage:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: mapping=GPU
ide0: win11_storage:vm-100-disk-3,size=128G
ide2: local:iso/Windows-11.iso,media=cdrom,size=5307M
machine: pc-q35-8.1,viommu=intel
memory: 8192
meta: creation-qemu=8.1.5,ctime=1720041318
name: win11
net0: rtl8139=BC:24:11:CE:22:45,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
parent: predeployment
scsihw: virtio-scsi-single
smbios1: uuid=fe2cfd2d-b7c5-407e-8549-f256121aaac3
sockets: 1
tpmstate0: win11_storage:vm-100-disk-2,size=4M,version=v2.0
vmgenid: d377a22b-dfc6-4ee6-a903-90aeaad51d60

I get Y when I execute:
Code:
root@pve:~# cat /sys/module/kvm_intel/parameters/nested
Y

I also resolved blue screens via:
Code:
root@pve:~# cat /sys/module/kvm/parameters/ignore_msrs
Y

systeminfo output:
Code:
Hyper-V Requirements:      VM Monitor Mode Extensions: Yes
                           Virtualization Enabled In Firmware: Yes
                           Second Level Address Translation: Yes
                           Data Execution Prevention Available: Yes

bcdedit output:
Code:
PS C:\Windows\system32> bcdedit /enum | findstr -i hypervisorlaunchtype
hypervisorlaunchtype    Auto

I have the necessary windows features enabled:
1720547312710.png

However, when I try to start wsl:
Code:
PS C:\Windows\system32> wsl --install -d Ubuntu
Ubuntu is already installed.
Launching Ubuntu...
Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x80370102
Please enable the Virtual Machine Platform Windows feature and ensure virtualization is enabled in the BIOS.
For information please visit https://aka.ms/enablevirtualization
Press any key to continue...

If I started nested Win11 hyper-v VM I get:
Code:
Failed to set security info for 'C:\ProgramData\Microsoft\Windows\Virtual Hard Disks\Win11.vhdx': 'Access is denied. '('0x80070005').
Virtual machine 'Win11' could not be started because the hypervisor is not running (Virtual machine ID D588A0D2-4F1E-4796-AA07-03AD28F79C46). The following actions may help you resolve the problem: 1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization. 2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer.  (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on.  Resetting the physical computer is not sufficient.) 3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.
'Win11' failed to start. (Virtual machine ID D588A0D2-4F1E-4796-AA07-03AD28F79C46)

Furthermore, when I inspect event viewer, I can see the following errors on boot:
Code:
Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase 0x7), and was not started.  This initialization failure may be the result of a platform configuration or firmware issue.  Contact your system vendor for more information or updated firmware.
The virtualization infrastructure driver (VID) is not running.
However, I do see other services starting:
Code:
Virtual Machine Management service is started successfully.
The WMI provider 'VmmsWmiInstanceAndMethodProvider' has started.
The WMI provider 'VmmsWmiEventProvider' has started.

Some additional things I've verified:
* Memory Integrity is disabled in Win11 guest.
* DMA (Enabled in bios)
* Intel (R) Virtualization Technology (Enabled in bios)
* Intel (R) VT-d Feature (Enabled in bios)
* Memory Protection Execution prevention (Enabled in bios)

That's my exhaustive list. I feel like I'm soo close, been trying to resolve this for hours and hours, but it's just not working. What am I missing?

Thank you,
 
Last edited:
Same problem. Any workaround?
I tried changing hv_* to several combinations but it didn't work.
 

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!

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!