Page 1 of 1

Can not start vm getting a VT-x error

Posted: 27. Jun 2017, 13:47
by cmccabe
I am running ubuntu 14.04, 64-bit and trying to create a VM but getting an VT-x disabled error. However I can not seem to update my bios and the results of 3 different commands all seem to show VT-x virtulization enabled.

Code: Select all

cat /proc/cpuinfo | grep "vmx"
find vmx colored red 

Code: Select all

egrep -q 'vmx|svm' /proc/cpuinfo && echo yes ||
echo no
yes

Code: Select all

lscpu
>Architecture: x86_64
>CPU op-mode(s): 32-bit, 64-bit
>Byte Order: Little Endian
>CPU(s): 16
>On-line CPU(s) list: 0-15
>Thread(s) per core: 2
>Core(s) per socket: 8
>Socket(s): 1
>NUMA node(s): 1
>Vendor ID: GenuineIntel
>CPU family: 6
>Model: 63
>Stepping: 2
>CPU MHz: 1226.906
>BogoMIPS: 4788.70
>Virtualization: VT-x --- seems to be on ---- maybe?
>L1d cache: 32K
>L1i cache: 32K
>L2 cache: 256K
>L3 cache: 20480K
>NUMA node0 CPU(s): 0-15
error message in virtual box:

Code: Select all

VT-x is disabled in bios

Failed to open a session for the virtual machine TS52.

VT-x is disabled in the BIOS. (VERR_VMX_MSR_VMXON_DISABLED).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
I have allocated 10240MB to the VM out of the total 128GB available on my system, running 4 processors, with vt-x/amd-v acceleration nested paging . Thank you :).

Re: Can not start vm getting a VT-x error

Posted: 27. Jun 2017, 14:15
by socratis
cmccabe wrote:VT-x is disabled in bios
cmccabe wrote:However I can not seem to update my bios
Then there's not that much that you can do. Having a bunch of programs tell you what *capabilities* your CPU has, does not mean that these capabilities are *available*. Huge difference. Find a way to get into your BIOS to enable virtualization.

And please do not "prune" the diagnostics. Post them as is, unless you know better...

Re: Can not start vm getting a VT-x error

Posted: 28. Jun 2017, 10:35
by michaln
As Socratis hinted, a given CPU is either VT-x capable or not. But that's not the end of the story. On a VT-x capable CPU, VT-x can be either disabled or enabled by firmware, and if it's disabled, no software can enable it.

The continuation of the story is that on a CPU which has VT-x enabled, VT-x can be already in use and not available to VirtualBox. That's not your problem though.

Is that needlessly complicated? You be the judge. But that's how Intel designed it.