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

What should we substitue for <VMName> #1795

Closed
dlech opened this issue Aug 1, 2023 · 3 comments
Closed

What should we substitue for <VMName> #1795

dlech opened this issue Aug 1, 2023 · 3 comments
Assignees

Comments

@dlech
Copy link

dlech commented Aug 1, 2023

Documentation Issue

In the following command, it appears that <VMName> is meant as a placeholder, but the surrounding documentation does not say what to replace it with.

Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true

Link to documentation page

https://learn.microsoft.com/en-us/windows/wsl/troubleshooting#error-0x80370102-the-virtual-machine-could-not-be-started-because-a-required-feature-is-not-installed

Suggested Improvements

No response

@Biswa96
Copy link
Contributor

Biswa96 commented Aug 1, 2023

The name is shown in the Hyper-V Manager (image is just an example).

image

That command is only required if you are running WSL inside of a Windows VM.

@dlech
Copy link
Author

dlech commented Aug 1, 2023

Thanks. The docs aren't clear if the command should be run on the host or the guest. Since the error occurs on the guest, I assumed the command needed to be run there as well, but now I see that it needs to be run on the host system.

@mattwojo
Copy link
Collaborator

Thanks for filing this issue @dlech and for the assist @Biswa96! Updated the doc with more context to resolve this in #1848

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

No branches or pull requests

3 participants