This computer doesn't have VT-x/AMD-v enabled. Enabling it in the BIOS is mandatory
up vote
3
down vote
favorite
I have a Windows 8.1 Dell laptop with virtualization enabled. Below is the picture of intel processor identification utility.
I have Fedora 24 installed in my virtual box. It also has virtualization enabled.
When I run the cat /proc/cpuinfo | grep 'vmx|svm'
and minikube start command, it display below error message and I am not able to proceed.
Any suggestion on this how to resolve this error?
virtualbox bios virtualization
add a comment |
up vote
3
down vote
favorite
I have a Windows 8.1 Dell laptop with virtualization enabled. Below is the picture of intel processor identification utility.
I have Fedora 24 installed in my virtual box. It also has virtualization enabled.
When I run the cat /proc/cpuinfo | grep 'vmx|svm'
and minikube start command, it display below error message and I am not able to proceed.
Any suggestion on this how to resolve this error?
virtualbox bios virtualization
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I have a Windows 8.1 Dell laptop with virtualization enabled. Below is the picture of intel processor identification utility.
I have Fedora 24 installed in my virtual box. It also has virtualization enabled.
When I run the cat /proc/cpuinfo | grep 'vmx|svm'
and minikube start command, it display below error message and I am not able to proceed.
Any suggestion on this how to resolve this error?
virtualbox bios virtualization
I have a Windows 8.1 Dell laptop with virtualization enabled. Below is the picture of intel processor identification utility.
I have Fedora 24 installed in my virtual box. It also has virtualization enabled.
When I run the cat /proc/cpuinfo | grep 'vmx|svm'
and minikube start command, it display below error message and I am not able to proceed.
Any suggestion on this how to resolve this error?
virtualbox bios virtualization
virtualbox bios virtualization
edited Oct 26 '16 at 11:47
Luka Kerr
17019
17019
asked Oct 26 '16 at 2:24
Rajkumar Natarajan
12016
12016
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
7
down vote
accepted
VirtualBox does not support nested virtualization, so the guest VM will not support VMX or SVM even though the host machine does. You can't run a VM inside a VM.
From your screenshot, it looks like you're trying to run Kubernetes in your VirtualBox VM. I'm not a Kubernetes expert, but my understanding is that it's meant to manage a cluster of virtual machines. The lack of nested virtualization means you can't run the cluster within a VM; you have to install it on real hardware. Basically, Kubernetes is something you'd use instead of VirtualBox, as a different way of creating and managing your VMs.
If you really need to run Kubernetes in a VM, VMware Workstation and Player seem to support nested virtualization.
add a comment |
up vote
-1
down vote
enter image description here
Try this one in Bios settings and re-run minikube start
1
This does not answer the author's question. The author was attempting to enable hardware virtualization within a VirtualBox virtual machine, VirtualBox, does not support nest virtualization. The author clearly indicated the VT-x option did not exist in the firmware settings.
– Ramhound
Nov 28 at 14:44
add a comment |
protected by Ramhound Nov 28 at 14:47
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
7
down vote
accepted
VirtualBox does not support nested virtualization, so the guest VM will not support VMX or SVM even though the host machine does. You can't run a VM inside a VM.
From your screenshot, it looks like you're trying to run Kubernetes in your VirtualBox VM. I'm not a Kubernetes expert, but my understanding is that it's meant to manage a cluster of virtual machines. The lack of nested virtualization means you can't run the cluster within a VM; you have to install it on real hardware. Basically, Kubernetes is something you'd use instead of VirtualBox, as a different way of creating and managing your VMs.
If you really need to run Kubernetes in a VM, VMware Workstation and Player seem to support nested virtualization.
add a comment |
up vote
7
down vote
accepted
VirtualBox does not support nested virtualization, so the guest VM will not support VMX or SVM even though the host machine does. You can't run a VM inside a VM.
From your screenshot, it looks like you're trying to run Kubernetes in your VirtualBox VM. I'm not a Kubernetes expert, but my understanding is that it's meant to manage a cluster of virtual machines. The lack of nested virtualization means you can't run the cluster within a VM; you have to install it on real hardware. Basically, Kubernetes is something you'd use instead of VirtualBox, as a different way of creating and managing your VMs.
If you really need to run Kubernetes in a VM, VMware Workstation and Player seem to support nested virtualization.
add a comment |
up vote
7
down vote
accepted
up vote
7
down vote
accepted
VirtualBox does not support nested virtualization, so the guest VM will not support VMX or SVM even though the host machine does. You can't run a VM inside a VM.
From your screenshot, it looks like you're trying to run Kubernetes in your VirtualBox VM. I'm not a Kubernetes expert, but my understanding is that it's meant to manage a cluster of virtual machines. The lack of nested virtualization means you can't run the cluster within a VM; you have to install it on real hardware. Basically, Kubernetes is something you'd use instead of VirtualBox, as a different way of creating and managing your VMs.
If you really need to run Kubernetes in a VM, VMware Workstation and Player seem to support nested virtualization.
VirtualBox does not support nested virtualization, so the guest VM will not support VMX or SVM even though the host machine does. You can't run a VM inside a VM.
From your screenshot, it looks like you're trying to run Kubernetes in your VirtualBox VM. I'm not a Kubernetes expert, but my understanding is that it's meant to manage a cluster of virtual machines. The lack of nested virtualization means you can't run the cluster within a VM; you have to install it on real hardware. Basically, Kubernetes is something you'd use instead of VirtualBox, as a different way of creating and managing your VMs.
If you really need to run Kubernetes in a VM, VMware Workstation and Player seem to support nested virtualization.
answered Oct 26 '16 at 2:44
Wyzard
5,64822223
5,64822223
add a comment |
add a comment |
up vote
-1
down vote
enter image description here
Try this one in Bios settings and re-run minikube start
1
This does not answer the author's question. The author was attempting to enable hardware virtualization within a VirtualBox virtual machine, VirtualBox, does not support nest virtualization. The author clearly indicated the VT-x option did not exist in the firmware settings.
– Ramhound
Nov 28 at 14:44
add a comment |
up vote
-1
down vote
enter image description here
Try this one in Bios settings and re-run minikube start
1
This does not answer the author's question. The author was attempting to enable hardware virtualization within a VirtualBox virtual machine, VirtualBox, does not support nest virtualization. The author clearly indicated the VT-x option did not exist in the firmware settings.
– Ramhound
Nov 28 at 14:44
add a comment |
up vote
-1
down vote
up vote
-1
down vote
enter image description here
Try this one in Bios settings and re-run minikube start
enter image description here
Try this one in Bios settings and re-run minikube start
answered Nov 28 at 14:17
Rupeshrams
1
1
1
This does not answer the author's question. The author was attempting to enable hardware virtualization within a VirtualBox virtual machine, VirtualBox, does not support nest virtualization. The author clearly indicated the VT-x option did not exist in the firmware settings.
– Ramhound
Nov 28 at 14:44
add a comment |
1
This does not answer the author's question. The author was attempting to enable hardware virtualization within a VirtualBox virtual machine, VirtualBox, does not support nest virtualization. The author clearly indicated the VT-x option did not exist in the firmware settings.
– Ramhound
Nov 28 at 14:44
1
1
This does not answer the author's question. The author was attempting to enable hardware virtualization within a VirtualBox virtual machine, VirtualBox, does not support nest virtualization. The author clearly indicated the VT-x option did not exist in the firmware settings.
– Ramhound
Nov 28 at 14:44
This does not answer the author's question. The author was attempting to enable hardware virtualization within a VirtualBox virtual machine, VirtualBox, does not support nest virtualization. The author clearly indicated the VT-x option did not exist in the firmware settings.
– Ramhound
Nov 28 at 14:44
add a comment |
protected by Ramhound Nov 28 at 14:47
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?