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

hyperv : Hyper-v commands have to be run as an Administrator #4511

Closed
Raj27Borra opened this issue Jun 17, 2019 · 5 comments
Closed

hyperv : Hyper-v commands have to be run as an Administrator #4511

Raj27Borra opened this issue Jun 17, 2019 · 5 comments
Assignees
Labels
co/hyperv HyperV related issues good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@Raj27Borra
Copy link

Raj27Borra commented Jun 17, 2019

The exact command to reproduce the issue:

The full output of the command that failed:

 Unable to start VM: create: precreate: Hyper-v commands have to be run as an Administrator  * Sorry that minikube crashed. If this was unexpected, we would love to hear from you:

The output of the minikube logs command:

The operating system version:

@medyagh medyagh changed the title Unable to start VM: create: precreate: Hyper-v commands have to be run as an Administrator * Sorry that minikube crashed. If this was unexpected, we would love to hear from you: hyperv : Hyper-v commands have to be run as an Administrator Jun 19, 2019
@medyagh
Copy link
Member

medyagh commented Jun 19, 2019

Thanks for taking the time to create this issue, to me it sounds like you need to run your powershell as administrator, could you please run your powershell as admin ?
btw what is the verison of minikube you are using ?

would you please paste the output of minikube version ?

@medyagh medyagh added co/hyperv HyperV related issues needs-solution-message Issues where where offering a solution for an error would be helpful good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. labels Jun 19, 2019
@medyagh
Copy link
Member

medyagh commented Jun 19, 2019

I think issues like this could be handled with a better formatted error message and skip crashing with a good solution message. I would be happy to review a PR

@sharifelgamal sharifelgamal added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jun 27, 2019
@blueelvis
Copy link
Contributor

I will pick this up and submit a PR shortly.

/assign

@tstromberg
Copy link
Contributor

Hopefully it's OK if I close this - there wasn't enough information to make it actionable, and some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment.

Here is additional information that may be helpful to us:

  • Whether the issue occurs with the latest minikube release
  • The exact minikube start command line used
  • The full output of the minikube start command, preferably with --alsologtostderr -v=3 for extra logging.
  • The full output of minikube logs

Thank you for sharing your experience!

@tstromberg tstromberg removed the needs-solution-message Issues where where offering a solution for an error would be helpful label Apr 3, 2020
@schguille
Copy link

The exact command to reproduce the issue:

The full output of the command that failed:

 Unable to start VM: create: precreate: Hyper-v commands have to be run as an Administrator  * Sorry that minikube crashed. If this was unexpected, we would love to hear from you:

The output of the minikube logs command:

The operating system version:

ejecuta como administrador el powershell

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/hyperv HyperV related issues good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants