VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX) inside VM

[venki2804]

What Happened?

venky@venky-VMware-Virtual-Platform:~$ minikube start --no-vtx-check
😄 minikube v1.34.0 on Ubuntu 24.10
✨ Using the virtualbox driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🔄 Restarting existing virtualbox VM for "minikube" ...
🤦 StartHost failed, but will try again: driver 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.280482 VBoxHeadless: exiting
🔄 Restarting existing virtualbox VM for "minikube" ...
😿 Failed to start virtualbox VM. Running "minikube delete" may fix it: driver 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.266031 VBoxHeadless: exiting

❌ Exiting due to HOST_VTX_UNAVAILABLE: Failed to start host: driver 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.266031 VBoxHeadless: exiting
💡 Suggestion: Your host does not support virtualization. If you are running minikube within a VM, try '--driver=docker'. Otherwise, enable virtualization in your BIOS
🍿 Related issues:
▪ #1994
▪ #5326

venky@venky-VMware-Virtual-Platform:~$

Attach the log file

venky@venky-VMware-Virtual-Platform:$ screenfetch
./+o+- venky@venky-VMware-Virtual-Platform
yyyyy- -yyyyyy+ OS: Ubuntu 24.10 oracular
://+//////-yyyyyyo Kernel: x86_64 Linux 6.11.0-9-generic
.++ .:/++++++/-.+sss/ Uptime: 28m .:++o: /++++++++/:--:/- Packages: 1862 o:+o+:++...```.-/oo+++++/ Shell: bash 5.2.32
.:+o:+o/. +sssoo+/ Resolution: 1718x920 .++/+:+oo+o: /sssooo. DE: GNOME 47.0.1
/+++//+:`oo+o /::--:. WM: Mutter
+/+o+++`o++o ++////. WM Theme: Adwaita
.++.o+++oo+:` /dddhhh. GTK Theme: Yaru [GTK2/3]
.+.o+oo:. `oddhhhh+ Icon Theme: Yaru
+.++o+o``-````.:ohdhhhhh+ Font: Ubuntu Sans 11
`:o+++ `ohhhhhhhhyo++os: Disk: 19G / 30G (65%)
.o:`.syhhhhhhh/.oo++o` CPU: 11th Gen Intel Core i5-11400H @ 4x 2.688GHz
/osyyyyyyo++ooo+++/ GPU: VMware SVGA II Adapter
````` +oo+++o: RAM: 2501MiB / 3354MiB
`oo++.
venky@venky-VMware-Virtual-Platform:$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Address sizes: 45 bits physical, 48 bits virtual
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Vendor ID: GenuineIntel
Model name: 11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz
CPU family: 6
Model: 141
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 4
Stepping: 1
BogoMIPS: 5375.99
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm constan
t_tsc arch_perfmon rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2
x2apic movbe popcnt aes xsave avx f16c rdrand hypervisor lahf_lm abm 3dnowprefetch pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 avx2
smep bmi2 erms invpcid avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xge
tbv1 xsaves arat avx512vbmi umip avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid movdiri movdir64b fsr
m avx512_vp2intersect md_clear flush_l1d arch_capabilities
Virtualization features:
Hypervisor vendor: VMware
Virtualization type: full
Caches (sum of all):
L1d: 192 KiB (4 instances)
L1i: 128 KiB (4 instances)
L2: 5 MiB (4 instances)
L3: 48 MiB (4 instances)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-3
Vulnerabilities:
Gather data sampling: Unknown: Dependent on hypervisor status
Itlb multihit: Not affected
L1tf: Mitigation; PTE Inversion
Mds: Mitigation; Clear CPU buffers; SMT Host state unknown
Meltdown: Mitigation; PTI
Mmio stale data: Not affected
Reg file data sampling: Not affected
Retbleed: Mitigation; IBRS
Spec rstack overflow: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Spectre v2: Mitigation; IBRS; IBPB conditional; STIBP disabled; RSB filling; PBRSB-eIBRS Not affected; BHI SW loop, KVM SW loop
Srbds: Not affected
Tsx async abort: Not affected
venky@venky-VMware-Virtual-Platform:

Operating System

Ubuntu

Driver

VirtualBox

[venki2804]

Can someone help me on this issue please?
I tried - minikube start --no-vtx-check
But still the issue persist

[kundan2707]

/kind support

[kundan2707]

/assign

[kundan2707]

Try Following:
Open CMD as administrator
Turning hyper-v OFF with and a reboot:
To TURN it back ON (or auto start) and reboot.