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

virtualbox: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #6171

Closed
atanu2531 opened this issue Dec 29, 2019 · 6 comments
Labels
co/virtualbox kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@atanu2531
Copy link

minikube start --vm-driver=virtualbox

  • minikube v1.6.2 on Microsoft Windows 10 Home Single Language 10.0.18362 Build 18362
  • Selecting 'virtualbox' driver from user configuration (alternates: [])
  • Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...

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

@tstromberg
Copy link
Contributor

Have you tried enabling virtualization (VT-x/AMD-v) in your BIOS?

@tstromberg tstromberg added co/virtualbox triage/needs-information Indicates an issue needs more information in order to work on it. kind/support Categorizes issue or PR as a support question. labels Jan 8, 2020
@tstromberg tstromberg changed the title X Unable to start VM. Please investigate and run 'minikube delete' if possible virtualbox: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory Jan 8, 2020
@priyawadhwa
Copy link

Hopefully it's OK if I close this - there wasn't enough information to make it actionable, and some time has already passed. If you are able to provide additional details, you may reopen it at any point by adding /reopen to your comment.

Here is additional information that may be helpful to us:

  • Whether the issue occurs with the latest minikube release
  • The exact minikube start command line used
  • The full output of the minikube start command, preferably with --alsologtostderr -v=3 for extra logging.
  • The full output of minikube logs

Thank you for sharing your experience!

@gillespiejim78
Copy link

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

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
*

/reopen

@k8s-ci-robot
Copy link
Contributor

@gillespiejim78: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

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

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
*

/reopen

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.

@Randikaviraj
Copy link

I am using the cloud flatform and cannt start minikube it's give as

😄 minikube v1.15.1 on Ubuntu 18.04
✨ Using the virtualbox driver based on existing profile

⛔ Requested memory allocation (978MB) is less than the recommended minimum 1907MB. Deployments may fail.

🧯 The requested memory allocation of 978MiB does not leave room for system overhead (total system memory: 978MiB). You may face stability issues.
💡 Suggestion: Start minikube with less memory allocated: 'minikube start --memory=978mb'

👍 Starting control plane node minikube in cluster minikube
🔄 Restarting existing virtualbox VM for "minikube" ...
🤦 StartHost failed, but will try again: driver start: 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.225083 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))
🔄 Restarting existing virtualbox VM for "minikube" ...
😿 Failed to start virtualbox VM. Running "minikube delete" may fix it: driver start: 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.226152 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

❌ Exiting due to HOST_VTX_UNAVAILABLE: Failed to start host: driver start: 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.226152 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))
💡 Suggestion: Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS
🍿 Related issues:
#1994
#5326

@3ch01c
Copy link

3ch01c commented Aug 15, 2021

I had to remove Windows features Hyper-V, Virtual Machine Platform, and Windows Hypervisor Platform to be able to use VirtualBox. Unfortunately, removing Virtual Machine Platform means you won't be able to use WSL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/virtualbox kind/support Categorizes issue or PR as a support question. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

7 participants