• minikube v1.25.1 on Microsoft Windows 10 Home Single Language 10.0.19043 Build 19043
  • MINIKUBE_HOME=C:\os\minikube\Minikube
• Automatically selected the virtualbox driver
• Starting control plane node minikube in cluster minikube
• Creating virtualbox VM (CPUs=2, Memory=4000MB, Disk=20000MB) ... ! StartHost failed, but will try again: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
• Creating virtualbox VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
• Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

X Exiting due to HOST_VIRT_UNAVAILABLE: Failed to start host: 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=docker'. Otherwise, consult your systems BIOS manual for how to enable virtualization.
• Related issues:
  • https://github.com/kubernetes/minikube/issues/3900
  • https://github.com/kubernetes/minikube/issues/4730

CodePudding user response：

I struggled with above error on Windows 10 (Lenovo Ideapad). Finally, when I ran this command:

minikube start --driver=virtualbox

It worked in one go and created the minikube machine in my VirtualBox.

CodePudding user response：

Those "VT-X/AMD-v" are instructions that need to be enabled, nowadays, running virtualization software such as VirtualBox.

Short answer: as suggested by the error message, those instructions are unavailable. Either because the hardware is just too old, or most likely because those instructions were disabled in your BIOS.

In the latter case, reboot your computer and enter the BIOS. Dig through your BIOS menus, look for CPU options, something about VT-X, AMD-v, virtualization instructions, ... depending on your motherboard, the name could differ slightly.

I'm not sure why adding "--driver=virtualbox" would help, considering your initial message already mentions VirtualBox was to be used, while suggesting to change this to "--driver=docker"