Unable to start VM - This computer doesn't have VT-X/AMD-v enabled

[gcsaba2]

What Happened?

Related to issue #4816

Running with --no-vtx-check seems to solve the issue.

Virtualization is enabled in BIOS and I'm able to start VMs and Docker on my Windows.

PS C:\WINDOWS\system32> minikube start

• minikube v1.25.2 on Microsoft Windows 10 Pro 10.0.19044 Build 19044
• Using the virtualbox driver based on existing profile
• Starting control plane node minikube in cluster minikube
• Creating virtualbox VM (CPUs=2, Memory=6000MB, 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=6000MB, 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:
  • Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #3900
  • Better documentation needed for virtual desktop #4730

Attach the log file

PS C:\WINDOWS\system32> minikube start

• minikube v1.25.2 on Microsoft Windows 10 Pro 10.0.19044 Build 19044
• Using the virtualbox driver based on existing profile
• Starting control plane node minikube in cluster minikube
• Creating virtualbox VM (CPUs=2, Memory=6000MB, 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=6000MB, 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:
  • Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #3900
  • Better documentation needed for virtual desktop #4730

Operating System

Windows

Driver

VirtualBox

[afbjorklund]

Probably a bug in libmachine, not recognizing newer cpuid or something similar like that.

If VirtualBox is working fine (and has hardware acceleration), it's a bug in "virtualbox" driver.

---

So one would need to look at the VirtualBox.log, for details why it was disabled ?

https://github.com/machine-drivers/machine/blob/master/drivers/virtualbox/vtx.go

It could also be something specific to the CPU type, not recognizing the extensions:

https://github.com/machine-drivers/machine/blob/master/drivers/virtualbox/vtx_intel.go

[afbjorklund]

Similar to:

• Windows 10: minikube start errors #13935

Running with --no-vtx-check seems to solve the issue.

That would be the workaround, until the bug can be fixed.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.