-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Comments
Have you tried enabling virtualization (VT-x/AMD-v) in your BIOS? |
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:
Thank you for sharing your experience! |
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.
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."
/reopen |
@gillespiejim78: You can't reopen an issue/PR unless you authored it or you are a collaborator. In response to this:
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. |
I am using the cloud flatform and cannt start minikube it's give as 😄 minikube v1.15.1 on Ubuntu 18.04 ⛔ 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. 👍 Starting control plane node minikube in cluster minikube Details: 00:00:00.225083 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005)) 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: Details: 00:00:00.226152 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005)) |
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. |
minikube start --vm-driver=virtualbox
X Unable to start VM. Please investigate and run 'minikube delete' if possible
The text was updated successfully, but these errors were encountered: