minikube: Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

Do you mind trying this:

minikube start --no-vtx-check

It’s hard to check from here if it’s due to the new upstream checks in place, or if things might actually work. Also, I suspect that passing in that small amount of memory might yield further issues down the line.

I am having the same issue on a Windows 10 Home machine. Virtualization is enabled, and I am able to run other VMs using VirtualBox.

C:\Users\gille>minikube start

• minikube v1.8.1 on Microsoft Windows 10 Home 10.0.19577 Build 19577
• Using the virtualbox driver based on existing profile
• Downloading VM boot image …
• Creating virtualbox VM (CPUs=2, Memory=4057MB, Disk=20000MB) …

X Unable to start VM. Please investigate and run ‘minikube delete’ if possible

• Error: [VBOX_VTX_DISABLED] creating host: create: precreate: This computer doesn’t have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

• Suggestion: Virtualization support is disabled on your computer. If you are running minikube within a VM, try ‘–driver=none’. Otherwise, consult your systems BIOS manual for how to enable virtualization.

• Related issues:

  • #3900
  • #4730

I have tried using the --no-vtx-check, and I end up getting a timeout. Looking at the VM in VirtualBox, it appears to be stuck at “Booting the kernel.”

C:\Users\gille>minikube start --no-vtx-check

• minikube v1.8.1 on Microsoft Windows 10 Home 10.0.19577 Build 19577
• Using the virtualbox driver based on existing profile
• Downloading VM boot image …
• Creating virtualbox VM (CPUs=2, Memory=4057MB, Disk=20000MB) …

X Unable to start VM. Please investigate and run ‘minikube delete’ if possible: creating host: create > host timed out in 120.000000 seconds *

• minikube is exiting due to an error. If the above message is not useful, open an issue:

  • https://github.com/kubernetes/minikube/issues/new/choose

Hey , I had a same issue , i try something it s work for me : i specified where i need to install minikube on windows 10 (in my virtualbox)

1. First i did the purge of old version of minikube : minikube delete --all --purge
2. i installed minikube without vtx : minikube start --driver=virtualbox --no-vtx-check
3. i checked my status: minikube status

---

minikube type: Control Plane host: Running kubelet: Running apiserver: Running kubeconfig: Configured timeToStop: Nonexistent

Do you mind trying this:

minikube start --no-vtx-check

It’s hard to check from here if it’s due to the new upstream checks in place, or if things might actually work. Also, I suspect that passing in that small amount of memory might yield further issues down the line.

Hi @tstromberg, I tried your suggestion but encounter an error:

minikube start --no-vtx-check
😄  minikube v1.0.1 on linux (amd64)
🤹  Downloading Kubernetes v1.14.1 images in the background ...
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...

💣  Unable to start VM: 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.759580 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new

Do you know what is this about? I’m trying to run kubernetes in VPS.

i try to download virtualbox , and use cmd(Administrator) keyin bcdedit /set hypervisorlaunchtype off and restart pc
and use cmd keyin minikube start and its work Win10 home 2004

other cmd ->cd C:\Program Files\Oracle\VirtualBox keyin VBoxManage.exe modifyvm "minikube" --nested-hw-virt on

I am using minikube on a newly launched EC2 - Ubuntu 18.04, I met the same errors, here’s what I did to fix:

1. sudo minikube start --no-vtx-check and got original errors.

2. sudo minikube start --vm-driver=none and got new errors:

   😄 minikube v1.20.0 on Ubuntu 18.04 ✨ Using the none driver based on user configuration

   ❌ Exiting due to GUEST_MISSING_CONNTRACK: Sorry, Kubernetes 1.20.2 requires conntrack to be installed in root’s path

3. Then I type sudo apt-get install -y conntrack

4. Try again sudo minikube start --vm-driver=none and got succeed messages.

Thanks, this works for me

also getting the same issues:

$ minikube start
😄  minikube v1.2.0 on linux (amd64)
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
E0723 13:38:57.444511    3837 start.go:559] 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

Check virtualisation :

$ lscpu | grep -i virt
Virtualisation:      AMD-V

BIOS has virtualisation enabled

running with --no-vtx-check flag works:

$ minikube start --no-vtx-check
😄  minikube v1.2.0 on linux (amd64)
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
🐳  Configuring environment for Kubernetes v1.15.0 on Docker 18.09.6

For more context, just trying to run minikube on my local machine.

This issue only crept up for me on minikube v1.2.0