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

Whitespace after processors= global option causes option to be ignored #4367

Closed
Bleeping opened this issue Aug 1, 2019 · 3 comments
Closed
Assignees
Labels
bug wsl2 Issue/feature applies to WSL 2

Comments

@Bleeping
Copy link

Your Windows build number: Microsoft Windows [Version 10.0.18945.1001]

What you're doing and what's happening: Testing the global options feature recently announced.

For the processors option, you cannot have whitespace after the value.

For example, this option will not work:

processors=2 # How many processors to assign to the WSL2 VM.

The memory option, though, has no issue when adding it like this:

memory=3GB # How much memory to assign to the WSL2 VM.

Removing the whitespace after the processors value, works fine:

processors=2

What's wrong / what should be happening instead:

Amount of processors shown using top should reflect the global option value. Instead it shows that the VM is using all of the available processors on the host.

image

@benhillis benhillis self-assigned this Aug 1, 2019
@benhillis benhillis added bug wsl2 Issue/feature applies to WSL 2 labels Aug 1, 2019
@benhillis
Copy link
Member

Thanks, I'll sort this out.

@jrnewton
Copy link

Is this bug still open?

Copy link
Contributor

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug wsl2 Issue/feature applies to WSL 2
Projects
None yet
Development

No branches or pull requests

3 participants