Minikube: nested VM's: This computer doesn't have VT-X/AMD-v enabled

[mithunmohanan1982]

mithun@mithun-VirtualBox:~$ sudo minikube start
[sudo] password for mithun:
Starting local Kubernetes v1.10.0 cluster...
Starting VM...
E0530 09:23:57.311484 3063 start.go:159] Error starting host: Error creating host: Error executing step: Running precreate checks.
: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory.

Retrying.
E0530 09:23:57.311686 3063 start.go:165] Error starting host: Error creating host: Error executing step: Running precreate checks.
: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
E0530 09:23:57.312273 3063 util.go:151] Error uploading error message: : Post https://clouderrorreporting.googleapis.com/v1beta1/projects/k8s-minikube/events:report?key=AIzaSyACUwzG0dEPcl-eOgpDKnyKoUFgHdfoFuA: dial tcp: lookup clouderrorreporting.googleapis.com on 127.0.0.53:53: server misbehaving
mithun@mithun-VirtualBox:~$

Also please note:My system settings

1. Windows 10 and Configured virtual environment to "Enabled" in BIOS

2. Installed oracle Virtual Box

3. ubuntu-18.04-desktop-amd64 ISO image in Virtual Box

4. Tried with VMware worksation as well but similar error

[dlorenc]

The error comes from here: https://github.com/kubernetes/minikube/blob/master/vendor/github.com/docker/machine/drivers/virtualbox/virtualbox_windows.go#L19

Are you able to start VMs in virtualbox without minikube?

[mithunmohanan1982]

Yes I am able to start VM in virtual box

[mudasirahmed2018]

I am facing the same issue. I have Windows 10 -->VirtualBox --> Linux CentOS7 --> VirtualBox 5.1 -->minikube

Any help would be appreciated. THanks

[hana-shin]

Hi,
I also encountered the same log.
So, I have enabled Intel VT-x/EPT of guest machie.
The minikube command has completed successfully.

Please check my website (Japanese).
https://qiita.com/hana_shin/items/e7a1c3fa18ad5889af8a

[TestLinux]

Hello,

Thanks hana-shin. Your Japanese site helped me in clearing below error by enabling the VT-X/AMD-v in virutal box settings. I have shared the settings image.

E0910 06:43:15.483575 2605 start.go:174] Error starting host: Error creating host: Error executing step: Running precreate checks.
: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory.

But after enabling VT-X/AMD still I encountered another new error, Please help me if anyone knows about this.

E0910 07:00:07.497729 2205 start.go:300] Error starting cluster: kubeadm init error
sudo /usr/bin/kubeadm init --config /var/lib/kubeadm.yaml --ignore-preflight-errors=DirAvailable--etc-kubernetes-manifests --ignore-preflight-errors=DirAvailable--data-minikube --ignore-preflight-errors=Port-10250 --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml --ignore-preflight-errors=FileAvailable--etc-kubernetes-manifests-etcd.yaml --ignore-preflight-errors=Swap --ignore-preflight-errors=CRI &&

[sandeep450]

I have same issue. in macbook pro >> VirtualBox >> Linux CentOS7 >> VirtualBox 5.2.18 >>minikube start

ERROR:-
This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory.

Retrying.
E0530 09:23:57.311686 3063 start.go:165] Error starting host: Error creating host: Error executing step: Running precreate checks.
: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

Any help is appreciated
Thanks in Advance

[tstromberg]

You can confirm whether or not your VM environment is properly configured for nested VM's by running:

wmic cpu get VirtualizationFirmwareEnabled

The previous comments point to the right place for VMware to set nested VT. For subsequent failures, please open a new issue. For example: https://github.com/kubernetes/minikube/issues/2861#issuecomment-419924935 may be indicative of a networking issue, but it's hard to tell from the lack of logs.

[SeenuMathew]

Solution that worked for me is
minikube start --vm-driver=none

[rahulkohli23]

@SeenuMathew the same worked for me as well Thanks.

minikube start --vm-driver=none

[azizzoaib786]

minikube start --vm-driver=none

solves the issue.

[heyritesh017]

minikube start --vm-driver=none solves the issue
please ensure that you have placed the minikube in the right path so that it can locate when you run with root user
sudo cp /usr/local/bin/minikube /usr/bin