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

sofianehammami · 2022-02-22T20:02:13Z

General information

Minishift version: 1.34.3
OS: Windows 10 Home edition 64 bytes version
Hypervisor: VirtualBox

Steps to reproduce

Go to directory where unzipped minishift
execute the command minishift.exe start --vm-driver virtualbox

Expected

Minishift VM is created in Virtual Box

Actual

Creation script fails

Logs

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"

Please note that I'm using Dell Inspire 7000 series with Intel I7 and Virtualization is enabled in BIOS . I don't have any BIOS option like VT-X/AMD-v

gbraad · 2022-02-23T17:21:25Z

The vm driver determined it is not working. This means you might have missed another option that is required in the bios. The vendors are unfortunately not very consistent about this. Try to use HyperV manager directly to see if it allows a VM to start. And check any vendor specific page that details this. In the worst case, update the bios and make sure vtx, vtd, or something like tla/sla is enabled.

…

-- Gerard Braad | http://gbraad.nl STEM is the source, but BUILD is how you develop! [ Better Understanding Involves Learning and Doing ]

sofianehammami · 2022-02-26T09:17:37Z

I have the same issue with an Acer Aspire vero which i baught lately. I dont want to buy an expensive laptop just for virtualization issues . VT-X option is visible in his BIOS and is enabled. But again with Intel tool the option is not checked.

gbraad · 2022-02-26T09:23:00Z

Virtualization is essential to the use of Minishift. Enabling virtualization on a machine is outside the scope of the tool and documentation as this is different per manufacturer/BIOS or even disabled by corporate policies. Consult with your manufacturer.

…

On Sat, Feb 26, 2022 at 5:17 PM sofianehammami ***@***.***> wrote: I have the same issue with an Acer Aspire vero which i baught lately. I dont want to buy an expensive laptop just for virtualization issues . — Reply to this email directly, view it on GitHub <#3553 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAOZRIJRCBFE4JJTDYH4TU5CLDZANCNFSM5PCMJMBQ> . You are receiving this because you commented.Message ID: ***@***.***>

-- Gerard Braad | http://gbraad.nl STEM is the source, but BUILD is how you develop! [ Better Understanding Involves Learning and Doing ]

dboggs95 · 2022-03-14T20:52:55Z

I found another issue with a similar problem. Disabling the Virtual Machine Platform fixes the issue. I don't understand why MS would enable something I keep getting told I can't use in the Home edition of Windows, especially when it prevents us from using Virtualization at all.

#3474 (comment)

new-py-learner · 2022-08-19T02:02:57Z

I have the same error.but my cpu virtual technology is enabled.

new-py-learner · 2022-08-19T02:03:55Z

returntrip · 2022-09-09T15:40:27Z

This might be of interest for some of you: #3556 (comment)

amolmote · 2022-09-21T05:45:34Z

I have refered issue #2852 and did accordingly, used administrative way and set-up the path as MINISHIFT_HOME, still facing the similar kind of issue which others faced already. Do anyone have the exact way to resolve this issue. Everything going well but at the end it throws an timeout error.

C:\Windows\system32>minishift start --vm-driver=virtualbox
-- 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
-- Downloading OpenShift binary 'oc' version 'v3.11.0'
53.59 MiB / 53.59 MiB [===================================================================================] 100.00% 0s-- Downloading OpenShift v3.11.0 checksums ... 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

Downloading ISO 'https://github.com/minishift/minishift-centos-iso/releases/download/v1.17.0/minishift-centos7.iso'
375.00 MiB / 375.00 MiB [=================================================================================] 100.00% 0s
-- Starting Minishift VM .................................................... OK
-- Checking for IP address ... OK
-- Checking for nameservers ... OK
-- Checking if external host is reachable from the Minishift VM ...
Pinging 8.8.8.8 ... OK
-- Checking HTTP connectivity from the VM ...
Retrieving http://minishift.io/index.html ... OK
-- Checking if persistent storage volume is mounted ... OK
-- Checking available disk space ... 1% used OK
-- Writing current configuration for static assignment of IP address ... OK
Importing 'openshift/origin-control-plane:v3.11.0' . CACHE MISS
Importing 'openshift/origin-docker-registry:v3.11.0' . CACHE MISS
Importing 'openshift/origin-haproxy-router:v3.11.0' . CACHE MISS
-- OpenShift cluster will be configured with ...
Version: v3.11.0
-- Pulling the OpenShift Container Image .................................................. OK
-- Copying oc binary from the OpenShift container image to VM ... OK
-- Starting OpenShift cluster ................................................................................Error during 'cluster up' execution: Error starting the cluster. ssh command error:
command : /var/lib/minishift/bin/oc cluster up --routing-suffix 192.168.99.104.nip.io --base-dir /var/lib/minishift/base --image 'openshift/origin-${component}:v3.11.0' --public-hostname 192.168.99.104
err : Process exited with status 1
output : Getting a Docker client ...
Checking if image openshift/origin-control-plane:v3.11.0 is available ...
E0921 05:33:08.519183 2832 helper.go:173] Reading docker config from /home/docker/.docker/config.json failed: open /home/docker/.docker/config.json: no such file or directory, will attempt to pull image docker.io/openshift/origin-cli:v3.11.0 anonymously
Pulling image openshift/origin-cli:v3.11.0
Image pull complete
E0921 05:33:13.853192 2832 helper.go:173] Reading docker config from /home/docker/.docker/config.json failed: open /home/docker/.docker/config.json: no such file or directory, will attempt to pull image docker.io/openshift/origin-node:v3.11.0 anonymously
Pulling image openshift/origin-node:v3.11.0
Pulled 5/6 layers, 84% complete
Pulled 6/6 layers, 100% complete
Extracting
Image pull complete
Checking type of volume mount ...
Determining server IP ...
Using public hostname IP 192.168.99.104 as the host IP
Checking if OpenShift is already running ...
Checking for supported Docker version (=>1.22) ...
Checking if insecured registry is configured properly in Docker ...
Checking if required ports are available ...
Checking if OpenShift client is configured properly ...
Checking if image openshift/origin-control-plane:v3.11.0 is available ...
Starting OpenShift using openshift/origin-control-plane:v3.11.0 ...
I0921 05:34:34.496010 2832 config.go:40] Running "create-master-config"
I0921 05:35:01.169893 2832 config.go:46] Running "create-node-config"
I0921 05:35:10.473088 2832 flags.go:30] Running "create-kubelet-flags"
I0921 05:35:12.460077 2832 run_kubelet.go:49] Running "start-kubelet"
I0921 05:35:13.386987 2832 run_self_hosted.go:181] Waiting for the kube-apiserver to be ready ...
E0921 05:40:21.396706 2832 run_self_hosted.go:571] API server error: Get https://192.168.99.104:8443/healthz?timeout=32s: dial tcp 192.168.99.104:8443: connect: connection refused ()
Error: timed out waiting for the condition

TheDeadOne · 2023-03-19T10:08:26Z

I found another issue with a similar problem. Disabling the Virtual Machine Platform fixes the issue. I don't understand why MS would enable something I keep getting told I can't use in the Home edition of Windows, especially when it prevents us from using Virtualization at all.

#3474 (comment)

Disabling Virtaul Machine Platform leads to WSL inoperability :(

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

sofianehammami commented Feb 22, 2022 •

edited

gbraad commented Feb 23, 2022 via email

sofianehammami commented Feb 26, 2022 •

edited

gbraad commented Feb 26, 2022 via email

dboggs95 commented Mar 14, 2022 •

edited

new-py-learner commented Aug 19, 2022

new-py-learner commented Aug 19, 2022

returntrip commented Sep 9, 2022

amolmote commented Sep 21, 2022 •

edited

TheDeadOne commented Mar 19, 2023

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

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

Comments

sofianehammami commented Feb 22, 2022 • edited

General information

Steps to reproduce

Expected

Actual

Logs

gbraad commented Feb 23, 2022 via email

sofianehammami commented Feb 26, 2022 • edited

gbraad commented Feb 26, 2022 via email

dboggs95 commented Mar 14, 2022 • edited

new-py-learner commented Aug 19, 2022

new-py-learner commented Aug 19, 2022

returntrip commented Sep 9, 2022

amolmote commented Sep 21, 2022 • edited

TheDeadOne commented Mar 19, 2023

sofianehammami commented Feb 22, 2022 •

edited

sofianehammami commented Feb 26, 2022 •

edited

dboggs95 commented Mar 14, 2022 •

edited

amolmote commented Sep 21, 2022 •

edited