You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ran 'wsl --shutdown' in powershell
Waited about 15 seconds and restarted linux distro from terminal (Ubuntu or Kali, it happens with both)
Expected Behavior
No errors
Actual Behavior
"wsl: wsl2.processors cannot exceed the number of logical processors on the system (4 > 8)
The same thing happens no matter what I set it to, 1, 2, 4, 8. I get the same error every time. The only time i dont get the error is when I either, completely remove the processor option from my .wslconfig file, or I comment it so it gets ignored.
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!
Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.
Windows Version
Microsoft Windows [Version 10.0.26100.2314]
WSL Version
2.4.5.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.167.4-1
Distro Version
Ubuntu 24.04 and Kali Linux 2024.4
Other Software
No response
Repro Steps
wslconfig.txt - my config file I'm using
ran 'wsl --shutdown' in powershell
Waited about 15 seconds and restarted linux distro from terminal (Ubuntu or Kali, it happens with both)
Expected Behavior
No errors
Actual Behavior
"wsl: wsl2.processors cannot exceed the number of logical processors on the system (4 > 8)
The same thing happens no matter what I set it to, 1, 2, 4, 8. I get the same error every time. The only time i dont get the error is when I either, completely remove the processor option from my .wslconfig file, or I comment it so it gets ignored.
Diagnostic Logs
WslLogs-2024-12-16_18-58-03.zip - Kali
WslLogs-2024-12-16_19-15-58.zip - Ubuntu
The text was updated successfully, but these errors were encountered: