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

Minikube Error: [VBOX_VERR_VMX_NO_VMX] driver start: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed: #7069

Closed
sharuk123 opened this issue Mar 17, 2020 · 10 comments
Labels
cause/nested-vm-config When nested VM's appear to play a role kind/support Categorizes issue or PR as a support question.

Comments

@sharuk123
Copy link

I installed oracle virtual Box and using oracle linux environment and trying to set up the environment for new oracle BRM 12 CNE.

while starting minikube i am facing below problem , please guide me to complete this .

[ocbrmcne@localhost ~]$ minikube start --driver=none
😄 minikube v1.8.2 on Oracle 8.0
✨ Using the virtualbox driver based on existing profile
⌛ Reconfiguring existing host ...
🔄 Starting existing virtualbox VM for "minikube" ...

💣 Unable to start VM. Please investigate and run 'minikube delete' if possible
❌ Error: [VBOX_VERR_VMX_NO_VMX] 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.665477 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=none'. Otherwise, enable virtualization in your BIOS
⁉️ Related issues:
#1994
#5326

@sharuk123
Copy link
Author

if i use with --driver=none below is the issue

[ocbrmcne@localhost ~]$ minikube start --driver=none
😄 minikube v1.8.2 on Oracle 8.0
✨ Using the virtualbox driver based on existing profile
⌛ Reconfiguring existing host ...
🔄 Starting existing virtualbox VM for "minikube" ...

💣 Unable to start VM. Please investigate and run 'minikube delete' if possible
❌ Error: [VBOX_VERR_VMX_NO_VMX] 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.602569 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=none'. Otherwise, enable virtualization in your BIOS
⁉️ Related issues:
#1994
#5326

@afbjorklund
Copy link
Collaborator

If you want to use the "none" driver, you need to delete the machine with the "virtualbox" driver.

@afbjorklund afbjorklund added kind/support Categorizes issue or PR as a support question. cause/nested-vm-config When nested VM's appear to play a role labels Mar 17, 2020
@sharuk123
Copy link
Author

Please check as per my installation step i need to start minikube with as given memory .
want to know why this error am getting and how to go ahead with this . request to support

[ocbrmcne@localhost ~]$ minikube start –disk-size=’800g’ –memory=’8192m’
😄 minikube v1.8.2 on Oracle 8.0
✨ Using the virtualbox driver based on existing profile
⌛ Reconfiguring existing host ...
🔄 Starting existing virtualbox VM for "minikube" ...

💣 Unable to start VM. Please investigate and run 'minikube delete' if possible
❌ Error: [VBOX_VERR_VMX_NO_VMX] 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.344649 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=none'. Otherwise, enable virtualization in your BIOS
⁉️ Related issues:
#1994
#5326

@sharuk123
Copy link
Author

sharuk123 commented Mar 18, 2020 via email

@afbjorklund
Copy link
Collaborator

If you want to run a VM in a VM, you need to make sure your system supports nested virtualization.

In order to change resource allocation (disk and memory size), you need to first delete the old one.

Related to #4730, better docs needed

This is not a standard minikube platform

@sharuk123
Copy link
Author

how to ensure my system supports nested Virtualization .

i could see enable nested VT-x/AMD-V is checked in my desktop VM and even inside my linux box VM , please suggest .

please suggest ,what is the best way to install minikube platform?

@sharuk123
Copy link
Author

sharuk123 commented Mar 18, 2020 via email

@medyagh
Copy link
Member

medyagh commented Apr 22, 2020

@sharuk123 seems like a connection error, are you using virtualbox driver on windows?
there are some issues with virtualbox networking.

could you try docker driver with latest version of minikube? (v 1.9.0 or higher) ?
minikube start --driver=docker

@medyagh
Copy link
Member

medyagh commented May 28, 2020

@sharuk123
I haven't heard from you, I am gonna close this issue
Meanwhile have you tried out newest driver Docker Driver with latest version of minikube?
you could try
minikube delete
minikube start --driver=docker

for more information on the docker driver checkout:
https://minikube.sigs.k8s.io/docs/drivers/docker/

@medyagh medyagh closed this as completed May 28, 2020
@venki2804
Copy link

Hi @sharuk123 ,

I am also facing the same issue. Can you please let me know who you solved it?
#20059

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cause/nested-vm-config When nested VM's appear to play a role kind/support Categorizes issue or PR as a support question.
Projects
None yet
Development

No branches or pull requests

4 participants