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

[longwuyuan]

The exact command to reproduce the issue:
minikube start

The full output of the command that failed:

C:\Users\user0>minikube start
* minikube v1.3.0 on Microsoft Windows 10 Pro 10.0.18362 Build 18362
* Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
E0806 20:39:15.548811    6172 start.go:723] StartHost: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
*
X 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
* Suggestion: 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/choose

C:\Users\me>minikube start --no-vtx-check
* minikube v1.3.0 on Microsoft Windows 10 Pro 10.0.18362 Build 18362
* Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
E0806 20:40:11.921481    9692 start.go:723] StartHost: create: creating: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe storageattach minikube --storagectl SATA --port 0 --device 0 --type dvddrive --medium C:\Users\me\.minikube\machines\minikube\boot2docker.iso failed:
VBoxManage.exe: error: Could not get the storage format of the medium 'C:\Users\me\.minikube\machines\minikube\boot2docker.iso' (VERR_NOT_SUPPORTED)
VBoxManage.exe: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 191 of file VBoxManageDisk.cpp
VBoxManage.exe: error: Invalid UUID or filename "C:\Users\me\.minikube\machines\minikube\boot2docker.iso"
*
X Unable to start VM: create: creating: C:\Program Files\Oracle\VirtualBox\VBoxManage.exe storageattach minikube --storagectl SATA --port 0 --device 0 --type dvddrive --medium C:\Users\me\.minikube\machines\minikube\boot2docker.iso failed:
VBoxManage.exe: error: Could not get the storage format of the medium 'C:\Users\me\.minikube\machines\minikube\boot2docker.iso' (VERR_NOT_SUPPORTED)
VBoxManage.exe: error: Details: code VBOX_E_IPRT_ERROR (0x80bb0005), component MediumWrap, interface IMedium, callee IUnknown
VBoxManage.exe: error: Context: "OpenMedium(Bstr(pszFilenameOrUuid).raw(), enmDevType, enmAccessMode, fForceNewUuidOnOpen, pMedium.asOutParam())" at line 191 of file VBoxManageDisk.cpp
VBoxManage.exe: error: Invalid UUID or filename "C:\Users\user0\.minikube\machines\minikube\boot2docker.iso"

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

C:\Users\user0>

The output of the minikube logs command:

X command runner: getting ssh client for bootstrapper: Error dialing tcp via ssh client: dial tcp 127.0.0.1:22: connectex: No connection could be made because the target machine actively refused it.
*

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

The operating system version:
Windows10 Pro fully updated

[longwuyuan]

@blueelvis I could provide additional info as needed

[longwuyuan]

and it works fine with Minikube Release v1.2.0 for Windows

[tstromberg]

First issue is #3900 - I wonder if us moving back to the upstream machine drivers introduced a regression. Are you on an AMD processor?

Second issue appears related to #4992 - I wonder if we have an issue upgrading VirtualBox disks? I'm curious if minikube delete solves it.

[longwuyuan]

(1) am not on AMD processor
(2) I have to check #4992 but the same laptop with everything same worked with version 1.2 of minikube for windows

What info can i add here ?

[tstromberg]

Do you mind sharing the result of:

dir C:\Users\me\.minikube\machines\minikube\boot2docker.iso

[afbjorklund]

I'm not sure it was the libmachine change*, seems more like the new downloader has issues ?

* confirmed above, not using an AMD processor and it would only explain the first issue anyway

[longwuyuan]

I deleted 1.3 and installed 1.2.0 now ;

C:\Users\me>dir C:\Users\me\.minikube\machines\minikube\boot2docker.iso
 Volume in drive C has no label.
 Volume Serial Number is 7A7C-14AF

 Directory of C:\Users\me\.minikube\machines\minikube

06-08-2019  22:02       135,616,512 boot2docker.iso
               1 File(s)    135,616,512 bytes
               0 Dir(s)  163,366,060,032 bytes free

C:\Users\me>

[afbjorklund]

Can you repeat with 1.3.0 ? That old one looks to have the right file length:

135616512 minikube-v1.2.0.iso

137441280 minikube-v1.3.0.iso

The strange thing is that the library should verify the SHA256 of the download.

[afbjorklund]

Apparently some versions of VirtualBox wants the size padded to 512 bytes... (preferrably 2048)

The 1.2.0 ISO is an even multiple (264876.0), but the 1.3.0 ISO has half a sector (69563.5)

EDIT: obviously that was off

Both are fine multiples of 2048

[longwuyuan]

• Originally, the minikube version 1.3.0 executable was a chocolatey install.
• This time I downloaded the binary from releases
• I cleaned up as below

• minikube delete
• minikube delete -p newminikube
• rmdir .minikube

• Then retried with manually downloaded minikube ver 1.3.0 executable

C:\Users\me\Downloads>minikube-1.3.0-windows-amd64.exe start
* minikube v1.3.0 on Microsoft Windows 10 Pro 10.0.18362 Build 18362
* Downloading VM boot image ...
    minikube-v1.3.0.iso.sha256: 65 B / 65 B [=====================] 100.00% 0s
    minikube-v1.3.0.iso: 131.07 MiB / 131.07 MiB [=============] 100.00% 3m28s
* Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
* Preparing Kubernetes v1.15.2 on Docker 18.09.8 ...
E0807 06:03:44.568785    7404 start.go:558] Error caching images:  Caching images for kubeadm: caching images: caching image C:\Users\me\.minikube\cache\images\k8s.gcr.io\k8s-dns-kube-dns-amd64_1.14.13: read tcp 10.8.4.11:8832->172.217.9.208:443: wsarecv: An existing connection was forcibly closed by the remote host.
* Unable to load cached images: loading cached images: loading image C:\Users\me\.minikube\cache\images\gcr.io\k8s-minikube\storage-provisioner_v1.8.1: CreateFile C:\Users\me\.minikube\cache\images\gcr.io\k8s-minikube\storage-provisioner_v1.8.1: The system cannot find the file specified.
* Downloading kubelet v1.15.2
* Downloading kubeadm v1.15.2
* Pulling images ...
* Launching Kubernetes ...
* Waiting for: apiserver proxy etcd scheduler controller dns
* Done! kubectl is now configured to use "minikube"


C:\Users\me\Downloads>dir C:\Users\me\.minikube\machines\minikube\boot2docker.iso
 Volume in drive C has no label.
 Volume Serial Number is 7A7C-14AF

 Directory of C:\Users\me\.minikube\machines\minikube

07-08-2019  06:00       137,441,280 boot2docker.iso
               1 File(s)    137,441,280 bytes
               0 Dir(s)  162,847,199,232 bytes free

C:\Users\me\Downloads>

The size of the ISO is different

[tstromberg]

OK. VERR_NOT_SUPPORTED was likely #4992

I'm still not sure why the VBOX_VTX_DISABLED issue occurred. I noticed it doesn't show up in your last comment.

[tstromberg]

Do you mind checking if minikube v1.3.1 has the same issue?

[longwuyuan]

I feel we can close this as I could not reproduce the problem after I switched from a chocolatey installed minikube to manually downloaded minikube executable from releases pages of github repo. Also suggesting close because access to a Window10 is gone for now.

[chrissound]

Also ran into this issue on v1.2.0 with a ryzen 3600 cpu.

Even though:

sudo systool -m kvm_amd -v | grep nested

    nested              = "1"

Seems to work fine with the kvm2 driver

[berndbausch]

I am getting VBOX_VTX_DISABLED as well. Cygwin on Windows 10 on an oldish core i3 laptop. Virtualization support is in fact enabled in the BIOS, and the VirtualBox GUI has no problems creating 64-bit VMs.

However, one recent configuration change may be relevant. I configured Windows 10 to allow running both WSL2 and VirtualBox instances. minikube used to work before that change.

Output of minikube start:

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

    > minikube-v1.12.0.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
    > minikube-v1.12.0.iso: 173.57 MiB / 173.57 MiB [] 100.00% 8.06 MiB p/s 22s
* Starting control plane node minikube in cluster minikube
* Downloading Kubernetes v1.18.3 preload ...
    > preloaded-images-k8s-v4-v1.18.3-docker-overlay2-amd64.tar.lz4: 526.27 MiB
* 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. "minikube start" may fix it: creating host: create: precreate: This computer doesn't h
ave VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
*
* [VBOX_VTX_DISABLED] error provisioning host Failed to start host: creating host: create: precreate: This computer doe
sn'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 '--driv
er=docker'. Otherwise, consult your systems BIOS manual for how to enable virtualization.
* Related issues:
  - https://github.com/kubernetes/minikube/issues/3900
  - https://github.com/kubernetes/minikube/issues/4730