Skip to content
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

wsl: wsl2.processors cannot exceed the number of logical processors on the system (4>8) #12386

Closed
1 of 2 tasks
coldsreign opened this issue Dec 16, 2024 · 3 comments
Closed
1 of 2 tasks

Comments

@coldsreign
Copy link

Windows Version

Microsoft Windows [Version 10.0.26100.2314]

WSL Version

2.4.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

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

Image

"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

Copy link

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.

Diagnostic information
Multiple log files found, using: https://github.com/user-attachments/files/18156215/WslLogs-2024-12-16_18-58-03.zip
.wslconfig found
Detected appx version: 2.4.5.0

@benhillis
Copy link
Member

/dupe #11860 (and fixed in 2.4.8)

Copy link
Contributor

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.

Thanks for your report!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants