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

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

Closed
mithunmohanan1982 opened this issue Jun 1, 2018 · 11 comments
Closed

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

mithunmohanan1982 opened this issue Jun 1, 2018 · 11 comments
Labels
cause/vm-networking Startup failures due to VM networking kind/bug Categorizes issue or PR as related to a bug.

Comments

@mithunmohanan1982
Copy link

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
Copy link
Contributor

dlorenc commented Jun 4, 2018

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
Copy link
Author

Yes I am able to start VM in virtual box

@mudasirahmed2018
Copy link

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
Copy link

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
Copy link

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.

image

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
Copy link

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 tstromberg changed the title Minikube not getting started - even after setting BIOS virtualization configuration nested VirtualBox: This computer doesn't have VT-X/AMD-v enabled Sep 19, 2018
@tstromberg tstromberg added kind/bug Categorizes issue or PR as related to a bug. drivers/virtualbox/linux cause/vm-networking Startup failures due to VM networking labels Sep 19, 2018
@tstromberg tstromberg changed the title nested VirtualBox: This computer doesn't have VT-X/AMD-v enabled nested VM's: This computer doesn't have VT-X/AMD-v enabled Sep 19, 2018
@tstromberg
Copy link
Contributor

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: #2861 (comment) may be indicative of a networking issue, but it's hard to tell from the lack of logs.

@SeenuMathew
Copy link

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

@raulkozy
Copy link

raulkozy commented Apr 4, 2019

@SeenuMathew the same worked for me as well Thanks.

minikube start --vm-driver=none

@azizzoaib786
Copy link

minikube start --vm-driver=none

solves the issue.

@heyritesh017
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cause/vm-networking Startup failures due to VM networking kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests