Windows 11 24H2 WSL2 - wsl: Nested virtualization is not supported on this machine message

A

AnalogKid

New Member
Oct 1, 2024
5
1
3
Hello, hoping that someone here knows how to fix this. It is not debilitating. It still works, but it is annoying.

I have a Windows 11 24H2 virtual machine machine running on Promox (proxmox-ve: 8.2.0 (running kernel: 6.8.12-2-pve)) that I have configured to also run WSL2.

The machine currently has Ubuntu 22.04 and 24.04 WSL2 OS instances installed. Both instances start and run fine. Everything works except there is this message the first time that I start up a WSL instance:

wsl: Nested virtualization is not supported on this machine

This only happens for the first instance launched. Any additional instances launched do not have this error.

To be clear, this the setup:
Computer Hardware > Proxmox installed directly > Win11 VM running on Proxmox server > WSL2 inside Win11 VM

This is the message that I get the first time the I launch a WSL VM. This is Ubuntu 24.04

1733714261653.png

There is no message for any subsequent WSL VM's launched during the same session.

This is Ubuntu 22.04

1733714369447.png

It does not matter what order they are launched in. Whichever one is launched first get the error message.

Does anyone know how to fix this?

Thanks!
 
  • Like
Reactions: RedKage
Yes, I have enabled the Nested Virtualization as per the Proxmox documentation. I believe that the necessary Proxmox configurations are set correctly and the VM guest CPU is set to host


1734197904390.png

The physical CPU is 16 x AMD Ryzen 7 8845HS w/ Radeon 780M Graphics (1 Socket)

An Internet search says that this CPU does support nested virtalization.

1734197999814.png

Any other thoughts?
 
Hi!

Is there a specific reason that you added -hypervisor to your CPU flags? Does the warning persist if you remove it? If not, does the warning show with all Hyper-V enlightenments removed? Is there any log information in the VM's start task log?
 
Hi!
I have exactly the same situation: just warning 'wsl: Nested virtualisation is not supported on this machine.'.
Maybe others also have this, but nobody care?
And yes: I removed -hypervisor, but warning remains.
Log is empty.

What are the possible consequences of this warning? What are they caused by?
Do you have any suggestions as to whether this is more of a WSL or Proxmox issue?
 
  • Like
Reactions: RedKage
Same here. Never figured it out.
Win 11 guest with WSL2, Proxomox host with CPU=host on an AMD Ryzen 9 7940HS.
Nested virt would make my WSL2 run faster
 
What does this on the node say?
Bash: 
grep -H . /sys/module/kvm*/parameters/nested
 
I haven't used it myself, so I'm not sure, but wouldn't the following work?

I suspect it's flagging virtualization as recognized in Task Manager.

Virtualization : enabled or Virtual Machine : yes

Even when the CPU is set as the host, the virtual machine is still recognized as a virtual machine.
Using the following options will change the Task Manager display.

Code: 
qm set vmid -args '-cpu host,hv_passthrough,level=16,-hypervisor,+svm'
 
Last edited:
Bash: 
1309.222902] fwbr103i0: port 2(tap103i0) entered blocking state

[ 1309.222905] fwbr103i0: port 2(tap103i0) entered forwarding state

[ 1382.399576] kvm_pr_unimpl_wrmsr: 54 callbacks suppressed

[ 1382.399581] kvm_amd: kvm [5973]: vcpu0, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1383.452638] kvm_amd: kvm [5973]: vcpu1, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1383.576213] kvm_amd: kvm [5973]: vcpu2, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1383.699764] kvm_amd: kvm [5973]: vcpu3, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1383.823417] kvm_amd: kvm [5973]: vcpu4, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1383.947085] kvm_amd: kvm [5973]: vcpu5, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1384.070704] kvm_amd: kvm [5973]: vcpu6, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1384.194373] kvm_amd: kvm [5973]: vcpu7, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1384.318067] kvm_amd: kvm [5973]: vcpu8, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1384.441738] kvm_amd: kvm [5973]: vcpu9, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1387.419571] kvm_pr_unimpl_wrmsr: 23 callbacks suppressed

[ 1387.419579] kvm_amd: kvm [5973]: vcpu33, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1387.544868] kvm_amd: kvm [5973]: vcpu34, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1387.669357] kvm_amd: kvm [5973]: vcpu35, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1387.795108] kvm_amd: kvm [5973]: vcpu36, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1387.920193] kvm_amd: kvm [5973]: vcpu37, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1388.045734] kvm_amd: kvm [5973]: vcpu38, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1388.171184] kvm_amd: kvm [5973]: vcpu39, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1388.296957] kvm_amd: kvm [5973]: vcpu40, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1388.422478] kvm_amd: kvm [5973]: vcpu41, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

[ 1388.547944] kvm_amd: kvm [5973]: vcpu42, guest rIP: 0xfffff829cc53db41 Unhandled WRMSR(0xc0010115) = 0x0

root@32core:/etc# cat ./pve/nodes/32core/qemu-server/103.conf

audio0: device=ich9-intel-hda,driver=spice

bios: ovmf

boot: order=sata0;ide2

cores: 64

cpu: host

efidisk0: asgard-2tb:103/vm-103-disk-1.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K

ide2: asgard-2tb:iso/virtio-win-0.1.285.iso,media=cdrom,size=771138K

machine: pc-q35-10.0+pve1

memory: 65536

meta: creation-qemu=6.2.0,ctime=1653366068

name: win10

net0: virtio=AE:79:28:76:97:65,bridge=vmbr0,firewall=1

numa: 0

ostype: win10

sata0: asgard-2tb:103/vm-103-disk-0.qcow2,aio=native,size=1T

sata1: local-lvm:vm-103-disk-0,aio=native,size=800G

smbios1: uuid=4c41c8f9-f14b-4751-a1b8-43e2a2ab667f

sockets: 1

tpmstate0: asgard-2tb:103/vm-103-disk-2.raw,size=4M,version=v2.0

vga: qxl

vmgenid: d033a4b2-864d-4171-8fc8-d00f93697f93

agent:1

args: -cpu host,hv_passthrough,level=16,-hypervisor,+svm

still wsl2 can start, but with log `wsl: Nested virtualization is not supported on this machine.`
 
You must log in or register to reply here.
Top Bottom