search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.48k stars 822 forks source link

Error : Wsl/Service/CreateInstance/CreateVm/HCS/0x80070142 after upgrading to Win11 24H2 #12116

Closed pquiring closed 1 month ago

pquiring commented 1 month ago

Windows Version

Microsoft Windows [Version 10.0.26100.1742]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

Kernel Version

5.15.153.1-2

Distro Version

All

Other Software

none

Repro Steps

wsl

Expected Behavior

Get bash prompt.

Actual Behavior

The target device has insufficient resources to complete the operation. Error code: Wsl/Service/CreateInstance/CreateVm/HCS/0x80070142

Diagnostic Logs

No response

github-actions[bot] commented 1 month ago

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](https://github.com/Microsoft/WSL/blob/master/diagnostics/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](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Open similar issues:

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

pquiring commented 1 month ago

[Uploading WslLogs-2024-10-02_10-12-41.zip…]()

pquiring commented 1 month ago

Tried to uninstall and reinstall - no change. (took an unusual long time to do that).

pquiring commented 1 month ago

Unable to start a VM in Hyper-V : same error code.

pquiring commented 1 month ago

Just for comparison, VirtualBox is working fine. So not a hardware issue.

OneBlue commented 1 month ago

@pquiring: The above link doesn't actually point to logs.

/logs

pquiring commented 1 month ago

WslLogs-2024-10-02_10-12-41.zip

github-actions[bot] commented 1 month ago
Diagnostic information ``` Appx package is not installed Detected user visible error: Wsl/Service/CreateInstance/CreateVm/HCS/0x80070142 ```
OneBlue commented 1 month ago

Thank you @pquiring. I wonder if the limitation is coming from CPU cores.

Can you try writing: 

[wsl2]
processors=1
memory=1GB
nestedVirtualization=false

To %USERPROFILE%/.wslconfig and collect /logs if that fails again ?

pquiring commented 1 month ago

WslLogs-2024-10-02_20-04-16.zip

.wslconfig had no effect.

github-actions[bot] commented 1 month ago
Diagnostic information ``` .wslconfig found Detected appx version: 2.3.24.0 ```
pquiring commented 1 month ago

Found this in event log: Virtual machine '' cannot be started on this server. The virtual machine NUMA topology requirements cannot be satisfied by the server NUMA topology. Try to use the server NUMA topology, or enable NUMA spanning. (Virtual machine ID A879800A-4440-4534-BBBD-6BE6A106AAE6).

pquiring commented 1 month ago

Fixed it! Enabled NUMA spanning in HyperV management and then restarted all HyperV services.

Nate-Mina commented 6 days ago

Fixed it! Enabled NUMA spanning in HyperV management and then restarted all HyperV services.

thanks i had same issue this was the only help