Hyper-V: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)

[mamudragon]

This a BUG REPORT
Environment: Windows 10-Pro 64-bit

Docker on Windows installed already, docker is running fine and the containers are running fine.

Docker stopped and made running as well , for running K8s setup. Both scenarios, same status- minikube did not start.

Trying to run K8S locally on my laptop using https://kubernetes.io/docs/getting-started-guides/minikube/ and observed the issues below.

1. Started kubectl cluster-info.

C:>kubectl cluster-info
Kubernetes master is running at https://192.168.99.100:8443

and then exited after sometime.

2. minikube version command was run.
   Output is as follows :

---

C:>minikube-windows-amd64 version
minikube version: v0.21.0

---

3. minikube start command was run.
   Output is as follows :

---

C:>minikube-windows-amd64 start
Starting local Kubernetes v1.7.0 cluster...
Starting VM...
E0921 18:52:12.921824 10592 start.go:129] Error starting host: Error starting stopped host: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm minikube --type headless failed:
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:01.552591 Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005)).

Retrying.
E0921 18:52:12.924743 10592 start.go:135] Error starting host: Error starting stopped host: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm minikube --type headless failed:
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:01.552591 Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005))

---

I then ran kubectl cluster-info dump. Output is as follows :

---

C:>kubectl cluster-info dump
Unable to connect to the server: dial tcp 192.168.99.100:8443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

---

Then, I ran status of minikube. Output is as follows :

---

C:>minikube-windows-amd64 status
minikube: Saved
localkube:
kubectl:

---

[mamudragon]

I installed Google Cloud SDK and then started minikube/kubectl for setting K8S, FYI.
Hyper-V was running all along these setup, in my laptop.

[mamudragon]

---

#1523 similar issue

https://technology.amis.nl/2017/07/17/virtualization-on-windows-10-with-virtual-box-hyper-v-and-docker-containers/

https://rominirani.com/tutorial-getting-started-with-kubernetes-on-your-windows-laptop-with-minikube-3269b54a226

---

Links above used for minikube install on windows 10

Using "minikube delete" did the trick, as pointed by someone here. There was an instance already available , which prevented minikube to start. But, it messed up my Docker install on the same wintel PCand Docker failed to restart. Had to reset my Windows 10 to get docker working.

Observation : virtualbox installed as addl package when Docker was installed and "MobyLinuxVM" vm created by Docker on Hyper-V. Minikube created a separate VM, but messed up HyperV settings (virtual switch etc) and other VMs. Had to reset my Windows 10 to get docker working. what a pain in the a*s!

Final comment : It looks like virtualbox and hyper-v does not coexist on the same PC and so does, docker and kubernetes-minikube.