Nested virtualization is not supported on arm based machines

Open sr-kai opened this issue 1 month ago • 1 comments

Windows Version

Microsoft Windows [Version 10.0.26100.7171]

WSL Version

2.6.1.0

Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version

No response

Distro Version

Debian/Ubuntu

Other Software

Even with the option enabled, WSL on snapdargon processor doesn't seem to support nested virutalization

Repro Steps

Enable nested virtualization, launch any WSL container

Expected Behavior

INFO: /dev/kvm exists KVM acceleration can be used

Actual Behavior

INFO: /dev/kvm does not exist HINT: sudo modprobe kvm modprobe: FATAL: Module msr not found in directory /lib/modules/6.6.87.2-microsoft-standard-WSL2

Diagnostic Logs

No response

Nov 28 '25 03:11 sr-kai

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to [email protected] with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

Nov 28 '25 03:11 github-actions[bot]

This is a hardware limitation of most ARM64 chips

Dec 04 '25 03:12 benhillis