-
Notifications
You must be signed in to change notification settings - Fork 847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wsl2.processors cannot exceed the number of logical processors on the system (6 > 24) #12346
Comments
Logs are required for review from WSL teamIf this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. How to collect WSL logsDownload and execute collect-wsl-logs.ps1 in an administrative powershell prompt:
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 here Once completed please upload the output files to this Github issue. Click here for more info on logging View similar issuesPlease 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:
|
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue. Thank you! |
I'm having the same issue. I set the processors to 2 and I'm getting this error (checking on the Event Viewer):
|
Agreed this bot is being too agressive. |
Windows Version
Microsoft Windows [ Version: 10.0.19045.5198 ]
WSL Version
2.4.5
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
Ubuntu 24.04
Other Software
No response
Repro Steps
Upgrade WSL to latest release (ver 2.4.5)
Set
wsl2.processors=6
(in my case)Expected Behavior
No errors when launching WSL
Actual Behavior
wsl: wsl2.processors cannot exceed the number of logical processors on the system (6 > 24)
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: