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

Unable to start VM: Error getting state for host: machine does not exist #3864

Closed
Nikjz opened this issue Mar 12, 2019 · 5 comments
Closed
Labels
kind/support Categorizes issue or PR as a support question. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@Nikjz
Copy link

Nikjz commented Mar 12, 2019

I tried executing minikube start and got the following error -

C:\Users\Nikhil Singh>minikube start
o minikube v0.35.0 on windows (amd64)
i Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
! Unable to start VM: Error getting state for host: machine does not exist

  • Sorry that minikube crashed. If this was unexpected, we would love to hear from you:

Windows 10

@tstromberg
Copy link
Contributor

I think what's happened here is that you have an old minikube configuration laying around, but have deleted the underlying VM in Virtualbox.

You should be able to get passed this by running minikube delete to delete the old minikube config and then minikube start will be able to create a new configuration and VM.

Please let me know if this helps!

@tstromberg tstromberg added kind/support Categorizes issue or PR as a support question. needs-solution-message Issues where where offering a solution for an error would be helpful priority/backlog Higher priority than priority/awaiting-more-evidence. labels Mar 12, 2019
@tstromberg tstromberg removed the needs-solution-message Issues where where offering a solution for an error would be helpful label May 2, 2019
@tstromberg
Copy link
Contributor

I believe this issue was resolved in the v1.1.0 release. Please try upgrading to the latest release of minikube and run minikube delete to remove the previous cluster state.

If the same issue occurs, please re-open this bug. Thank you opening this bug report, and for your patience!

@CloudCrusader
Copy link

I manually removed a VM called minikube from Hyper-V on W10 Enterprise 1903 ,
running the 'minikube delete' command results in error.

[stderr =====>] : Hyper-V\Get-VM : Hyper-V was unable to find a virtual machine with name "minikube".

running the 'minikube delete -p minikube' results in same error.
(minikube v1.2.0)

@wildanr
Copy link

wildanr commented Dec 6, 2019

I'm using Windows 10, minikube version v1.5.2, with Virtual Box and facing this problem after several attempt of minikube stop, minikube delete, deleting .minikube, and repeat.

After several minutes of frustration, I finally get it to work by simply restarting the computer.

@msalaslo
Copy link

I was using Windows 10 + minikube v1.5.2 and was facing the same issue.
After upgrading minikube to v1.12.1 and executing:

minikube delete
minikube start 

everything worked fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/support Categorizes issue or PR as a support question. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Development

No branches or pull requests

5 participants