VBOX_VERR_VMX_NO_VMX: Point users to better documentation

[varkalaramalingam]

The exact command to reproduce the issue:

The full output of the command that failed:

The output of the minikube logs command:

The operating system version:

[varkalaramalingam]

ram@minikube:~/Downloads$ minikube start

😄  minikube v1.1.1 on linux (amd64)
💿  Downloading Minikube ISO ...
 131.29 MB / 131.29 MB [============================================] 100.00% 0s
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
E0619 17:42:20.633776    9103 start.go:529] StartHost: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

💣  Unable to start VM
❌  Error:         [VBOX_VTX_DISABLED] create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
💡  Advice:        In some environments, this message is incorrect. Try 'minikube start --no-vtx-check'
⁉️   Related issues:
    ▪ https://github.com/kubernetes/minikube/issues/3900

😿  If the above advice does not help, please let us know: 
👉  https://github.com/kubernetes/minikube/issues/new
ram@minikube:~/Downloads$ minikube start --no-vtx-check
😄  minikube v1.1.1 on linux (amd64)
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
E0619 17:43:45.636765    9145 start.go:529] StartHost: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:00.251427 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

💣  Unable to start VM
❌  Error:         [VBOX_VERR_VMX_NO_VMX] create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:00.251427 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))
💡  Advice:        Please check your BIOS, and ensure that you are running without HyperV or other nested virtualization that may interfere
⁉️   Related issues:
    ▪ https://github.com/kubernetes/minikube/issues/1994

😿  If the above advice does not help, please let us know: 
👉  https://github.com/kubernetes/minikube/issues/new

[varkalaramalingam]

minikube starting error

[medyagh]

I am curious are you running this inside a VM?
does the solution in this issue help you ?

minikube start --no-vtx-check

#3900

[ankushgarg28794]

Hi Medyagh,

I have run the above command and getting the below error, can you please help me to resolve the below error for minikube.

[root@localhost kubernates]# minikube start --no-vtx-check

• minikube v1.2.0 on linux (amd64)
  ! Please don't run minikube as root or with 'sudo' privileges. It isn't necessary.
• Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
  E0703 10:46:25.289226 6346 start.go:559] StartHost: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
  VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
  VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:00.707013 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

X Unable to start VM

• Error: [VBOX_VERR_VMX_NO_VMX] create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
  VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
  VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:00.707013 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

• Advice: Please check your BIOS, and ensure that you are running without HyperV or other nested virtualization that may interfere

• Related issues:

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

• If the above advice does not help, please let us know:

  • https://github.com/kubernetes/minikube/issues/new
    [root@localhost kubernates]# lscpu | grep Virtualization
    Virtualization type: full

[afbjorklund]

Sounds like you are trying to run minikube with nested virtualization ? (VirtualBox from a VM)

[ankushgarg28794]

Yes,

[ankushgarg28794]

I want to run minikube on centos 7 which is on Windows VM. And for that i am facing the above issue. I have installed vm on linux as well. Could you please suggest how to proceed with the above mentioned error.

[Maxiaoyu0]

same issue

[ankushgarg28794]

Do we have any resolution over here on github for the mentioned issue.

[medyagh]

we currently do not support running minikube inside windows vm (nested vm). however we have support for ruining minikube inside VM but it currently only supports linux. please checkout this doc

https://github.com/kubernetes/minikube/blob/master/docs/vmdriver-none.md

[tstromberg]

We can do a better job about detecting and documenting this issue. Leaving open for now.

[varkalaramalingam]

To install minikube with dashboard in 5 minutes in ubuntu $ sudo su ####Install Docker 17.12 CE apt-get install apt-transport-https ca-certificates curl software-properties-common curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" apt-get update apt-get install docker-ce=17.12.0~ce-0~ubuntu ###Install kubectl and Minikube curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl chmod +x ./kubectl mv ./kubectl /usr/local/bin/kubectl curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.25.0/minikube-linux-amd64 && chmod +x minikube && sudo mv minikube /usr/local/bin/ minikube start --vm-driver=none minikube dashboard http://localhost:30000

…

On Thu, Jul 18, 2019 at 10:31 PM Thomas Strömberg ***@***.***> wrote: We can do a better job about detecting and documenting this issue. Leaving open for now. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4530?email_source=notifications&email_token=ALJJEHW2NV4V75M45C7ZTJ3QACOXTA5CNFSM4HZI66FKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2JEJIA#issuecomment-512902304>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALJJEHV3SVHQ3VDQCYD3D2LQACOXTANCNFSM4HZI66FA> .

-- Regards, Ramalingam Vrakala, 8142256226.

[afbjorklund]

Those versions look outdated... Anyway, there will be better documentation provided for none etc.

If you no longer care about running minikube in nested virtualization, maybe this issue can be closed ?

[tstromberg]

As of minikube v1.4, the advice this error output now reads:

Your host does not support virtualization. If you are running minikube within a VM, try '--vm-driver=none'. Otherwise, enable virtualization in your BIOS"