Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #3900

nekooei · 2019-03-18T19:17:58Z

I am using Centos 7 VPS
I run this command
minikube start --cpus 1 --memory 1024 --kubernetes-version v1.13.0
but the result is :

😄 minikube v0.35.0 on linux (amd64)
🔥 Creating virtualbox VM (CPUs=1, Memory=1024MB, Disk=20000MB) ...
💣 Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

😿 Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉 https://github.com/kubernetes/minikube/issues/new

also I run lscpu | grep Virtualization and the result is:
Virtualization type: full

my cpu model is

The text was updated successfully, but these errors were encountered:

afbjorklund · 2019-03-18T19:34:04Z

Looks like your VMware doesn't have nested virtualization supported fully ?

nekooei · 2019-03-18T21:24:22Z

how can i check that ?

tstromberg · 2019-03-19T18:53:31Z

Do you mind trying this:

minikube start --no-vtx-check

It's hard to check from here if it's due to the new upstream checks in place, or if things might actually work. Also, I suspect that passing in that small amount of memory might yield further issues down the line.

nekooei · 2019-03-19T19:01:54Z

Thanks, this works for me

MateuszZiolek · 2019-04-01T17:11:49Z

well i have next step issue, but looks like this is done by using vbox inside vbox =]
nested vm is still under development ...

VBoxManage.exe modifyvm debiandev --nested-hw-virt on

is not helping in this case.

root@debiandev:/home/x# lscpu | grep Virtualization
Virtualization type:   full
root@debiandev:/home/x# minikube start --no-vtx-check
o   minikube v1.0.0 on linux (amd64)
$   Downloading Kubernetes v1.14.0 images in the background ...
>   Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...

!   Unable to start VM: create: creating: 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.631564 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

*   Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
-   https://github.com/kubernetes/minikube/issues/new

darrylsepeda · 2019-05-12T10:13:12Z

Do you mind trying this:

minikube start --no-vtx-check

It's hard to check from here if it's due to the new upstream checks in place, or if things might actually work. Also, I suspect that passing in that small amount of memory might yield further issues down the line.

Hi @tstromberg, I tried your suggestion but encounter an error:

minikube start --no-vtx-check
😄  minikube v1.0.1 on linux (amd64)
🤹  Downloading Kubernetes v1.14.1 images in the background ...
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...

💣  Unable to start VM: create: creating: 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.759580 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new

Do you know what is this about? I'm trying to run kubernetes in VPS.

gbraad · 2019-05-12T10:37:53Z

Your provider would need to offer 'Nested virtualization' or virtualization passthrough.

…

On Sun, May 12, 2019 at 6:13 PM Darryl ***@***.***> wrote: Do you mind trying this: minikube start --no-vtx-check It's hard to check from here if it's due to the new upstream checks in place, or if things might actually work. Also, I suspect that passing in that small amount of memory might yield further issues down the line. Hi @tstromberg, I tried your suggestion but encounter an error: minikube start --no-vtx-check minikube v1.0.1 on linux (amd64) 🤹 Downloading Kubernetes v1.14.1 images in the background ... Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ... Unable to start VM: create: creating: 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.759580 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005)) Sorry that minikube crashed. If this was unexpected, we would love to hear from you: https://github.com/kubernetes/minikube/issues/new Do you know what is this about? I'm trying to run kubernetes in VPS. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

-- Gerard Braad | http://gbraad.nl [ Doing Open Source Matters ]

rakeshnambiar · 2019-06-22T20:22:09Z

I am facing the same issue on AWS Ubuntu 18.

ubuntu@ip-172-31-12-250:~$ lscpu | grep Virtualization
Virtualization type: full
Please check your BIOS, and ensure that you are running without HyperV or other nested virtualization that may interfere

So should I choose the EC2 instance which supports this?

ankushgarg28794 · 2019-07-03T05:35:10Z

Hi Team,

I am getting the below error while running the below mentioned command. I am running this command on centos 7 and bios settings is also enabled . Please help and provide the resolution.

[root@localhost kubernates]# minikube start --no-vtx-check

minikube v1.2.0 on linux (amd64)
! Please don't run minikube as root or with 'sudo' privileges. It isn't necessary.
Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
E0703 10:46:25.289226 6346 start.go:559] StartHost: create: creating: 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.707013 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

X Unable to start VM

Error: [VBOX_VERR_VMX_NO_VMX] create: creating: 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.707013 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

Advice: Please check your BIOS, and ensure that you are running without HyperV or other nested virtualization that may interfere
Related issues:
- Hyper-V: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX) #1994
If the above advice does not help, please let us know:
- https://github.com/kubernetes/minikube/issues/new
  [root@localhost kubernates]# lscpu | grep Virtualization
  Virtualization type: full

WesleyCharlesBlake · 2019-07-23T11:44:17Z

also getting the same issues:

$ minikube start
😄  minikube v1.2.0 on linux (amd64)
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
E0723 13:38:57.444511    3837 start.go:559] StartHost: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

💣  Unable to start VM
❌  Error:         [VBOX_VTX_DISABLED] create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
💡  Advice:        In some environments, this message is incorrect. Try 'minikube start --no-vtx-check'
⁉️   Related issues:
    ▪ https://github.com/kubernetes/minikube/issues/3900

😿  If the above advice does not help, please let us know: 
👉  https://github.com/kubernetes/minikube/issues/new

Check virtualisation :

$ lscpu | grep -i virt
Virtualisation:      AMD-V

BIOS has virtualisation enabled

running with --no-vtx-check flag works:

$ minikube start --no-vtx-check
😄  minikube v1.2.0 on linux (amd64)
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
🐳  Configuring environment for Kubernetes v1.15.0 on Docker 18.09.6

For more context, just trying to run minikube on my local machine.

This issue only crept up for me on minikube v1.2.0

breezyraj · 2019-08-18T08:04:48Z

Hi,

I am also facing the same error, below are the configuration
OS - ubuntu(Running as guest in Windows machine)
VMX enabled: lscpu | grep -i virt
Virtualization type: full
minikube version: v1.3.0

I tried below options but no luck
sudo minikube start --vm-driver=none
sudo minikube start --no-vtx-check

LOG:
sudo minikube start --no-vtx-check
😄 minikube v1.3.0 on Ubuntu 18.04
⚠️ Please don't run minikube as root or with 'sudo' privileges. It isn't necessary with virtualbox driver.
🔥 Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
E0818 13:17:11.848294 19057 start.go:723] StartHost: create: creating: 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:01.285078 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

💣 Unable to start VM
❌ Error: [VBOX_VERR_VMX_NO_VMX] create: creating: 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

Kinldy help me

aamir200 · 2019-09-07T18:18:32Z

I am facing same issue

kefimo · 2019-09-14T15:12:35Z

I am facing same issue:
Configuration:
VPS :
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
...
Hypervisor vendor: KVM
Virtualization type: full
...

minikube start --no-vtx-check
😄 minikube v1.3.1 on Ubuntu 18.04
⚠️ Please don't run minikube as root or with 'sudo' privileges. It isn't necessary with virtualbox driver.
💡 Tip: Use 'minikube start -p ' to create a new cluster, or 'minikube delete' to delete this one.
🔄 Starting existing virtualbox VM for "minikube" ...
E0914 15:09:08.092043 22698 start.go:723] StartHost: 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.374049 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))

💣 Unable to start VM
❌ Error: [VBOX_VERR_VMX_NO_VMX] 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.374049 Power up failed (vrc=VERR_VMX_NO_VMX, rc=NS_ERROR_FAILURE (0X80004005))
💡 Suggestion: Please check your BIOS, and ensure that you are running without HyperV or other nested virtualization that may interfere
⁉️ Related issues:
▪ #1994

😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose

rikirenz · 2019-09-25T10:28:32Z

Hey Guys I am facing the same issue:

► minikube start            
😄  minikube v0.34.1 on linux (amd64)
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) ...
💣  Unable to start VM: create: creating: Unable to start the VM: /usr/bin/VBoxManage startvm minikube --type headless failed:
VBoxManage: error: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:00.234112 Power up failed (vrc=VERR_VMX_MSR_ALL_VMX_DISABLED, rc=NS_ERROR_FAILURE (0X80004005))

😿  Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
👉  https://github.com/kubernetes/minikube/issues/new

nsit-karan · 2020-01-04T11:50:59Z

Facing same issue and none of the workarounds suggested seem to work.

afbjorklund · 2020-01-04T12:06:15Z

@nsit-karan : please open a new issue, about your nested vmware problem

amitranjan0007 · 2020-03-15T18:42:00Z

Is this issue reolved ? I am getting the same error

afbjorklund · 2020-03-15T19:05:24Z

@amitranjan02051988 : please open a new issue

gillespiejim78 · 2020-03-15T19:07:21Z

@amitranjan02051988 are you using Windows 10 Home? If so, feel free to add on to #6952

calmaa1 · 2020-06-20T15:39:16Z

Got the same error after updating my windows to enable WSL 2.

Turned out "Windows Hyhpervisor Platform" enabled has been causing the conflict.

Minikube started correctly after disabling it.

onichandame · 2020-07-03T14:38:21Z

still seeing this issue on Windows 10 Pro ver.2004. --no-vtx-check did the trick. Maybe this issue is relevant?

s78718 · 2020-07-29T09:02:07Z

i try to download virtualbox , and use cmd(Administrator)
keyin bcdedit /set hypervisorlaunchtype off and restart pc
and use cmd keyin minikube start and its work
Win10 home 2004

other
cmd ->cd C:\Program Files\Oracle\VirtualBox keyin VBoxManage.exe modifyvm "minikube" --nested-hw-virt on

ParagNetApp · 2020-10-20T09:14:35Z

Despite of enabling VT-D in the bios I get the message VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)

c:\work>minikube start --driver=virtualbox --disk-size=40000mb --no-vtx-check

minikube v1.12.2 on Microsoft Windows 10 Enterprise 10.0.18363 Build 18363
Using the virtualbox driver based on user configuration
minikube 1.14.0 is available! Download it: https://github.com/kubernetes/minikube/releases/tag/v1.14.0
To disable this notice, run: 'minikube config set WantUpdateNotification false'
Downloading VM boot image ...

minikube-v1.12.2.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
minikube-v1.12.2.iso: 173.73 MiB / 173.73 MiB [] 100.00% 3.44 MiB p/s 51s
Starting control plane node minikube in cluster minikube
Downloading Kubernetes v1.18.3 preload ...

preloaded-images-k8s-v5-v1.18.3-docker-overlay2-amd64.tar.lz4: 510.91 MiB
Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=40000MB) ...
Deleting "minikube" in virtualbox ...
! StartHost failed, but will try again: creating host: create: creating: Unable to start the VM: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe startvm minikube --type headless failed:
VBoxManage.exe: error: VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API_2 (VERR_NEM_MISSING_KERNEL_API_2).
VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole

Details: 00:00:02.877441 Power up failed (vrc=VERR_VMX_NO_VMX, rc=E_FAIL (0X80004005))

Failed to start virtualbox VM. "minikube start" may fix it: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\paragp.minikube\machines\minikube\config.json: The system cannot find the file specified.

X error provisioning host: Failed to start host: Error loading existing host. Please try running [minikube delete], then run [minikube start] again.: filestore "minikube": open C:\Users\paragp.minikube\machines\minikube\config.json: The system cannot find the file specified.
*

minikube is exiting due to an error. If the above message is not useful, open an issue:
- https://github.com/kubernetes/minikube/issues/new/choose

dharlequin · 2021-02-01T09:29:25Z

My minikube has been existing fine in VirtualBox on Windows 10 probably for a week.

Then right while I was working with minikub and kubectl, it just stopped responding, I was getting timeouts. And it could not properly start or stop. I tried deleting it, and now I can't start it back on VirtualBox. I get the same error as people here, that I have to enable virtialization:

`minikube start --vm-driver=virtualbox
😄 minikube v1.17.0 on Microsoft Windows 10 Pro 10.0.19041 Build 19041
✨ Using the virtualbox driver based on existing profile
👍 Starting control plane node minikube in cluster minikube
🔥 Creating virtualbox VM (CPUs=2, Memory=4000MB, 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=4000MB, 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

❌ 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:
▪ #3900
▪ https://github.com/kubernetes/minikube/issues/4730`

Tried rebooting and upgrading VirtualBox. Does not help.

YonathanGuez · 2021-03-28T20:07:26Z

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

Error: [VBOX_VTX_DISABLED] 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=none'. 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

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
*

minikube is exiting due to an error. If the above message is not useful, open an issue:

https://github.com/kubernetes/minikube/issues/new/choose

Hey , I had a same issue , i try something it s work for me :
i specified where i need to install minikube on windows 10 (in my virtualbox)

First i did the purge of old version of minikube :
minikube delete --all --purge
i installed minikube without vtx :
minikube start --driver=virtualbox --no-vtx-check
i checked my status:
minikube status

minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
timeToStop: Nonexistent

fryce · 2021-06-07T08:21:15Z

I am using minikube on a newly launched EC2 - Ubuntu 18.04, I met the same errors, here's what I did to fix:

sudo minikube start --no-vtx-check and got original errors.
sudo minikube start --vm-driver=none and got new errors:

😄 minikube v1.20.0 on Ubuntu 18.04
✨ Using the none driver based on user configuration

❌ Exiting due to GUEST_MISSING_CONNTRACK: Sorry, Kubernetes 1.20.2 requires conntrack to be installed in root's path
Then I type sudo apt-get install -y conntrack
Try again sudo minikube start --vm-driver=none and got succeed messages.

jandalpetr · 2021-09-20T08:16:13Z

Hi, @tstromberg, thanks
minikube start --no-vtx-check
This works to me on localy on Windows 10 Pro

λ minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured

IT-sukesh · 2022-06-22T07:08:10Z

! 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=2200MB, 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.

SAND171 · 2022-09-07T10:51:19Z

Do you mind trying this:

minikube start --no-vtx-check

It's hard to check from here if it's due to the new upstream checks in place, or if things might actually work. Also, I suspect that passing in that small amount of memory might yield further issues down the line.

thanks............worked for me

Cheroo35 · 2023-02-08T14:30:28Z

minikube start --no-vtx-check

this command worked for me

Lanata07 · 2023-12-08T18:01:06Z

Do you mind trying this:

minikube start --no-vtx-check

It's hard to check from here if it's due to the new upstream checks in place, or if things might actually work. Also, I suspect that passing in that small amount of memory might yield further issues down the line.

It works for me :)

Noorjahan153 · 2024-05-23T11:37:50Z

It's works for me .Thank you

cmhanmandlu · 2024-09-01T15:20:08Z

Do you mind trying this:

minikube start --no-vtx-check

It's hard to check from here if it's due to the new upstream checks in place, or if things might actually work. Also, I suspect that passing in that small amount of memory might yield further issues down the line.

it works for me, thanks

afbjorklund added cause/nested-vm-config When nested VM's appear to play a role co/virtualbox labels Mar 18, 2019

tstromberg added the needs-solution-message Issues where where offering a solution for an error would be helpful label Mar 22, 2019

tstromberg added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 4, 2019

tstromberg removed the needs-solution-message Issues where where offering a solution for an error would be helpful label May 2, 2019

tstromberg closed this as completed May 23, 2019

rajashekarkristappa mentioned this issue Jun 18, 2019

[VBOX_VTX_DISABLED] create: precreate: This computer doesn't have VT-X/AMD-v enabled #4517

Closed

varkalaramalingam mentioned this issue Jun 19, 2019

VBOX_VERR_VMX_NO_VMX: Point users to better documentation #4530

Closed

tstromberg mentioned this issue Aug 6, 2019

VBOX_VTX_DISABLED: This computer doesn't have VT-X/AMD-v enabled (v1.3.0) #4997

Closed

tstromberg mentioned this issue Sep 25, 2019

Add solution for VERR_VMX_MSR_ALL_VMX_DISABLED #5460

Merged

This was referenced Dec 29, 2019

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

Closed

Unable to start minikube on windows 10 home #6172

Closed

no workaround for minikube start up on win 10 home kubernetes/website#18364

Closed

liorms mentioned this issue Feb 5, 2020

crash while trying to start minikube on ubuntu18.04 on proxmox #6498

Closed

gillespiejim78 mentioned this issue Mar 8, 2020

virtualbox: --no-vtx-check: host timed out in 120.000000 seconds #6952

Closed

njohnjoel mentioned this issue Jun 10, 2020

Virtualization Enabled in BIOS, Hyper-V uninstalled | Windows10 #8442

Closed

ayushpawar21 mentioned this issue Jul 20, 2020

minikube start --vm-driver=virtualbox #6247

Closed

This was referenced Apr 22, 2022

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

Closed

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

Closed

soujatyabhat mentioned this issue Aug 13, 2022

Not Able start Minikube. It is showing bellow error. Please Help!!!! #14788

Closed

barnamdas mentioned this issue Mar 9, 2023

how to fix this when "minikube start" command is given #16011

Closed

Lakhvinder25 mentioned this issue Apr 15, 2023

Minikube failed to start in windows #16330

Closed

jessesebas mentioned this issue Nov 1, 2023

unable to start minikube . virtualization enabled and orcale vm virtual box install . still i get the following error #17539

Closed

hashandom mentioned this issue Jun 8, 2024

Unable To run minikube hashandom/Quality-Assurance-Projects#1

Open

dkabazzi mentioned this issue Jul 4, 2024

Minikube failing to interact with VirtualBox #19196

Closed

Brijeshku mentioned this issue Sep 11, 2024

Minikube failed with runing command minikube start --driver=virtualbox on window 11 #19609

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #3900

Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #3900

nekooei commented Mar 18, 2019

afbjorklund commented Mar 18, 2019

nekooei commented Mar 18, 2019

tstromberg commented Mar 19, 2019

nekooei commented Mar 19, 2019

MateuszZiolek commented Apr 1, 2019 •

edited

Loading

darrylsepeda commented May 12, 2019

gbraad commented May 12, 2019 via email

rakeshnambiar commented Jun 22, 2019

ankushgarg28794 commented Jul 3, 2019

WesleyCharlesBlake commented Jul 23, 2019

breezyraj commented Aug 18, 2019 •

edited

Loading

aamir200 commented Sep 7, 2019

kefimo commented Sep 14, 2019

rikirenz commented Sep 25, 2019

nsit-karan commented Jan 4, 2020

afbjorklund commented Jan 4, 2020

amitranjan0007 commented Mar 15, 2020

afbjorklund commented Mar 15, 2020

gillespiejim78 commented Mar 15, 2020

calmaa1 commented Jun 20, 2020 •

edited

Loading

onichandame commented Jul 3, 2020

s78718 commented Jul 29, 2020 •

edited

Loading

ParagNetApp commented Oct 20, 2020

dharlequin commented Feb 1, 2021

YonathanGuez commented Mar 28, 2021

fryce commented Jun 7, 2021

jandalpetr commented Sep 20, 2021

IT-sukesh commented Jun 22, 2022

SAND171 commented Sep 7, 2022

Cheroo35 commented Feb 8, 2023

Lanata07 commented Dec 8, 2023

Noorjahan153 commented May 23, 2024

cmhanmandlu commented Sep 1, 2024

Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #3900

Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory #3900

Comments

nekooei commented Mar 18, 2019

afbjorklund commented Mar 18, 2019

nekooei commented Mar 18, 2019

tstromberg commented Mar 19, 2019

nekooei commented Mar 19, 2019

MateuszZiolek commented Apr 1, 2019 • edited Loading

darrylsepeda commented May 12, 2019

gbraad commented May 12, 2019 via email

rakeshnambiar commented Jun 22, 2019

ankushgarg28794 commented Jul 3, 2019

WesleyCharlesBlake commented Jul 23, 2019

breezyraj commented Aug 18, 2019 • edited Loading

aamir200 commented Sep 7, 2019

kefimo commented Sep 14, 2019

rikirenz commented Sep 25, 2019

nsit-karan commented Jan 4, 2020

afbjorklund commented Jan 4, 2020

amitranjan0007 commented Mar 15, 2020

afbjorklund commented Mar 15, 2020

gillespiejim78 commented Mar 15, 2020

calmaa1 commented Jun 20, 2020 • edited Loading

onichandame commented Jul 3, 2020

s78718 commented Jul 29, 2020 • edited Loading

ParagNetApp commented Oct 20, 2020

dharlequin commented Feb 1, 2021

YonathanGuez commented Mar 28, 2021

fryce commented Jun 7, 2021

jandalpetr commented Sep 20, 2021

IT-sukesh commented Jun 22, 2022

SAND171 commented Sep 7, 2022

Cheroo35 commented Feb 8, 2023

Lanata07 commented Dec 8, 2023

Noorjahan153 commented May 23, 2024

cmhanmandlu commented Sep 1, 2024

MateuszZiolek commented Apr 1, 2019 •

edited

Loading

breezyraj commented Aug 18, 2019 •

edited

Loading

calmaa1 commented Jun 20, 2020 •

edited

Loading

s78718 commented Jul 29, 2020 •

edited

Loading