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

Does WSL2 plan to support dual CPUs? #12323

Closed
hyjforesight opened this issue Nov 27, 2024 · 8 comments
Closed

Does WSL2 plan to support dual CPUs? #12323

hyjforesight opened this issue Nov 27, 2024 · 8 comments

Comments

@hyjforesight
Copy link

hyjforesight commented Nov 27, 2024

Is your feature request related to a problem? Please describe.
WSL2 doesn't support dual/multiple sockets of CPUs. Change settings by .wslconfig doesn't work. This issue persists and remain unsolved. See below:
#4137
#3314
#5423
#5472

Describe the solution you'd like
LET WSL2 SUPPORT DUAL SOCKETS OF CPUS. PLZ!

Describe alternatives you've considered
Give up Windows and use Ubuntu. This is definitely not what we Windows fans look forward to.

Additional context
AGAIN, LET WSL2 SUPPORT DUAL SOCKETS OF CPUS. PLZ!

Copy link

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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] 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'.

@muratyurdakul75
Copy link

I am also expecting this. Even if it uses dual CPU, WSL does not currently support more than 64 processors. But even using dual CPUs would be a good development. Half of the server's resources are wasted right now. 1 CPU is working and the other is idle.

@sirredbeard
Copy link
Contributor

sirredbeard commented Nov 27, 2024

This is a duplicate of #1115.

@muratyurdakul75 There is a workaround for more than 64 cores, which is a separate issue. @xieyubo has a solution and I have pre-built patched .dll's for both amd64 and arm64 you can grab on my fork.

@benhillis
Copy link
Member

/dupe #1115

@benhillis
Copy link
Member

This is a duplicate of #1115.

@muratyurdakul75 There is a workaround for more than 64 cores, which is a separate issue. @xieyubo has a solution and I have pre-built patched .dll's for both amd64 and arm64 you can grab on my fork.

Thanks! FYI I've sorted out a fix for this which should be coming soon.

@benhillis
Copy link
Member

@sirredbeard and @xieyubo - after the fix goes live would you mind making a note in your project / fork that the workaround is no longer needed?

@xieyubo
Copy link

xieyubo commented Dec 3, 2024 via email

@hyjforesight
Copy link
Author

Hi @benhillis and @sirredbeard , thank you for making this workaround. BTW, is there any plan for supporting dual CPUs?

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

5 participants