Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory" #3474

richardgohcr · 2020-08-31T15:18:50Z

I am currently trying to set up minishift on my Dell XPS 15 laptop running Windows 10 home. I have also previously installed Docker desktop for windows with no problems. However, I am facing the error message "Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"

I have tried disabling and re-enabling virtualisation on my system BIOS, but to no avail. Anyone facing this issue on Windows 10 Home as well?

General information

Minishift version: v1.34.2
OS: Windows 10 Home 2004
Hypervisor: VirtualBox

PS C:\Users\Richard> minishift start -- Starting profile 'minishift' -- Check if deprecated options are used ... OK -- Checking if https://mirror.openshift.com is reachable ... OK -- Checking if requested OpenShift version 'v3.11.232' is valid ... OK -- Checking if requested OpenShift version 'v3.11.232' is supported ... OK -- Checking if requested hypervisor 'virtualbox' is supported on this platform ... OK -- Checking if VirtualBox is installed ... OK -- Checking the ISO URL ... OK -- Checking if provided oc flags are supported ... OK -- Starting the OpenShift cluster using 'virtualbox' hypervisor ... -- Minishift VM will be configured with ... Memory: 4 GB vCPUs : 2 Disk size: 20 GB -- Starting Minishift VM ..... FAIL E0831 23:15:47.758000 20152 start.go:494] Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory". Retrying. Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"

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

anjannath · 2020-09-25T04:36:00Z

On windows, enabling hyperv along with virtualbox may cause issues, are you sure that hyperv is also not enabled in the same time?

miroslav-beranic · 2020-10-19T20:37:55Z

I was looking for this for days. I only have VBox installed and Minishift fails to start, with same error as reported. On same workstation, in dual boot I have Fedora, where Minishift works as expected.

I have VT-X enabled in BIOS ( in can not be disabled 🍔 ) and I have VBox 6.1.

@richardgohcr Just noticed - Windows 10 Home ( as far as I understand, only Pro+ version of Windows 10 is able to use Virtualization ). Can be, I am wrong. But this is one thing I read when looking how to fix my problem.

bintegra · 2020-10-20T11:10:33Z

Hi all,

it turned out Minishift is complaining about missing Hyper-V, regardless configuration to use VBox.

 minishift.exe start  --show-libmachine-logs --logtostderr -v5 --vm-driver virtualbox
-- minishift version: v1.34.3+4b58f89
-- Starting profile 'minishift'
-- Check if deprecated options are used ... OK
-- Checking if https://github.com is reachable ... OK
-- Checking if requested OpenShift version 'v3.11.0' is valid ... OK
-- Checking if requested OpenShift version 'v3.11.0' is supported ... OK
-- Checking if requested hypervisor 'virtualbox' is supported on this platform ... OK
-- Checking if VirtualBox is installed ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting the OpenShift cluster using 'virtualbox' hypervisor ...
-- Minishift VM will be configured with ...
   Memory:    2 GB
   vCPUs :    2
   Disk size: 20 GB
-- Starting Minishift VM ....Found binary path at C:\Minishift\bin\minishift.exe
Launching plugin server for driver virtualbox
Plugin server listening at address 127.0.0.1:64675
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(minishift) Calling .GetMachineName
(minishift) Calling .DriverName
Reading certificate data from C:\Minishift\certs\ca.pem
Decoding PEM data...
Parsing certificate...
Reading certificate data from C:\Minishift\certs\cert.pem
Decoding PEM data...
Parsing certificate...
Running pre-create checks...
(minishift) Calling .PreCreateCheck
(minishift) DBG | COMMAND: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version
(minishift) DBG | STDOUT:
(minishift) DBG | {
(minishift) DBG | 6.1.14r140239
(minishift) DBG | }
(minishift) DBG | STDERR:
(minishift) DBG | {
(minishift) DBG | }
(minishift) DBG | Hyper-V is not installed.
. FAIL E1020 13:03:19.726727    3972 start.go:499] Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory". Retrying.
Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"

CallisteH · 2021-01-27T09:13:17Z

Same issue there.
I'm on Windows10 home, so I do not have Hyper-V installed, according to this doc

@p4qu1t0 Minishift seems to instanciate himself the VM on virtualbox so I do not have any VM in my list after running VBoxManage list vms

VirtualBox is installed and can run VM, but Minishift stills wants hyper-v

$ minishift start --show-libmachine-logs --logtostderr -v5 --vm-driver virtualbox
-- minishift version: v1.34.3+cb967be
-- Starting profile 'minishift'
-- Check if deprecated options are used ... OK
-- Checking if https://mirror.openshift.com is reachable ... OK
-- Checking if requested OpenShift version 'v3.11.286' is valid ... SKIP
-- Checking if requested OpenShift version 'v3.11.286' is supported ... OK
-- Checking if requested hypervisor 'virtualbox' is supported on this platform ... OK
-- Checking if VirtualBox is installed ... OK
-- Checking the ISO URL ... OK
-- Checking if provided oc flags are supported ... OK
-- Starting the OpenShift cluster using 'virtualbox' hypervisor ...
-- Minishift VM will be configured with ...
   Memory:    4 GB
   vCPUs :    2
   Disk size: 20 GB
-- Starting Minishift VM ....Found binary path at C:\Users\calli\minishift\minishift.exe
Launching plugin server for driver virtualbox
Plugin server listening at address 127.0.0.1:64693
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(minishift) Calling .GetMachineName
(minishift) Calling .DriverName
Reading certificate data from C:\Users\calli\.minishift\certs\ca.pem
Decoding PEM data...
Parsing certificate...
Reading certificate data from C:\Users\calli\.minishift\certs\cert.pem
Decoding PEM data...
Parsing certificate...
Running pre-create checks...
(minishift) Calling .PreCreateCheck
(minishift) DBG | COMMAND: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version
(minishift) DBG | STDOUT:
(minishift) DBG | {
(minishift) DBG | 6.1.18r142142
(minishift) DBG | }
(minishift) DBG | STDERR:
(minishift) DBG | {
(minishift) DBG | }
(minishift) DBG | Hyper-V is not installed.
. FAIL E0127 10:08:01.569914   10892 start.go:499] Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory". Retrying.
Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory"```

mrballcb · 2021-01-29T20:43:06Z

I struggled with this same error while trying to get minishift to create VM's in my freshly installed VirtualBox (and rebooted). I created a test linux VM,, and saw the nested VT-x setting was grayed out for me in VirtualBox. All of the instructions say to make sure that Hyper-V is turned off because it puts some kind of lock on on the VT-X such that VirtualBox can't share it. I did not have Hyper-V enabled on my Win10 Home machine, however I did have "Virtual Machine Platform" enabled.

After turning off both of them, minishift start began working. (It didn't succeed all the way, but I'm still researching.) EDIT: Yes it did succeed all the way - I mistook some of the debug output as failures, when it actually is "keep trying to connect to do something until it succeeds".

gbraad · 2021-02-18T07:44:22Z

Make sure virtualization is enabled from the BIOS and that the hypervisor has exclusive access to the VTX estension; don't mix hypervisors on the same machine.

gbraad · 2021-02-18T07:45:13Z

it turned out Minishift is complaining about missing Hyper-V, regardless configuration to use VBox.

make sure to remove any previous VMs, and use the driver option to force the selection on start

mihailmanoli · 2021-04-26T08:56:45Z

I did not have Hyper-V enabled on my Win10 Home machine, however I did have "Virtual Machine Platform" enabled.

This saved my day

adarshvyas99 · 2021-07-16T19:19:20Z

adarshvyas99 · 2021-07-16T19:20:32Z

I am getting the same

gbraad · 2021-07-18T05:02:25Z

This issue is all over the place with virtualbox, hyperv, and no extensions enabled. Please check your bios before you try minishift/CDK. After this, see if you have enabled or installed the hypervisor and it works outside the use of minishift. If you can start a demo VM, there is no need to try minishift. If your hypervisor works, try a delete and make sure the hypervisor is correct set as config. On start, collecta log. Check the issue tracker for the same platform and hypervisor... And I'd this does not yield any results. File a new issue.

…

On Sat, Jul 17, 2021, 03:20 Adarsh Vyas ***@***.***> wrote: I am getting the same — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#3474 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAOZTRAM2OVN7FCLMZ6L3TYCBAZANCNFSM4QQUHNAA> .

mahmud255 · 2022-11-24T11:06:57Z

I struggled with this same error while trying to get minishift to create VM's in my freshly installed VirtualBox (and rebooted). I created a test linux VM,, and saw the nested VT-x setting was grayed out for me in VirtualBox. All of the instructions say to make sure that Hyper-V is turned off because it puts some kind of lock on on the VT-X such that VirtualBox can't share it. I did not have Hyper-V enabled on my Win10 Home machine, however I did have "Virtual Machine Platform" enabled.

After turning off both of them, minishift start began working. (It didn't succeed all the way, but I'm still researching.) EDIT: Yes it did succeed all the way - I mistook some of the debug output as failures, when it actually is "keep trying to connect to do something until it succeeds".

Thanks a lot. It works for me :)

gbraad closed this as completed Feb 18, 2021

dboggs95 mentioned this issue Mar 14, 2022

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

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory" #3474

Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory" #3474

richardgohcr commented Aug 31, 2020

anjannath commented Sep 25, 2020

miroslav-beranic commented Oct 19, 2020 •

edited

Loading

bintegra commented Oct 20, 2020

CallisteH commented Jan 27, 2021 •

edited

Loading

mrballcb commented Jan 29, 2021 •

edited

Loading

gbraad commented Feb 18, 2021

gbraad commented Feb 18, 2021

mihailmanoli commented Apr 26, 2021

adarshvyas99 commented Jul 16, 2021

adarshvyas99 commented Jul 16, 2021

gbraad commented Jul 18, 2021 via email

mahmud255 commented Nov 24, 2022

Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory" #3474

Error starting the VM: Error creating the VM. Error with pre-create check: "This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory" #3474

Comments

richardgohcr commented Aug 31, 2020

General information

anjannath commented Sep 25, 2020

miroslav-beranic commented Oct 19, 2020 • edited Loading

bintegra commented Oct 20, 2020

CallisteH commented Jan 27, 2021 • edited Loading

mrballcb commented Jan 29, 2021 • edited Loading

gbraad commented Feb 18, 2021

gbraad commented Feb 18, 2021

mihailmanoli commented Apr 26, 2021

adarshvyas99 commented Jul 16, 2021

adarshvyas99 commented Jul 16, 2021

gbraad commented Jul 18, 2021 via email

mahmud255 commented Nov 24, 2022

miroslav-beranic commented Oct 19, 2020 •

edited

Loading

CallisteH commented Jan 27, 2021 •

edited

Loading

mrballcb commented Jan 29, 2021 •

edited

Loading