VTx under Linux (Ubuntu Oneiric 11.10, Linux 3.0) => Fixed in SVN

[jaak]

After updating the kernel from 2.6.39-3 to 3.x the option VT broke in Virtualbox.

cpuinfo shows vmx but the option to enable VT in Virtualbox is gone.

After rebooting into kernel 2.9.39-3 and executing sudo /etc/init.d/vbixdrv setup VT came back.

(it doesn't matter what Guest OS is beiing used)

[Frank Mehnert]

Just tried Linux 3.0-rc3 vanilla and everything works fine here. Ubuntu Oneiric is not stable yet so I will close this ticket as worksforme.

[Evan]

I am also experiencing this bug, and I have found the root cause.

In the function called "suplibOsQueryVTxSupported" on line 257 of "HostDrivers/Support/linux/SUPLib-linux.cpp" it expects a version number of format #.#.# and will return an error if receives any other format. Uname on ubuntu 11.10 currently returns the string 3.0-1-generic (note the hyphen instead of a dot between the second and third numbers).

I can verify that stubbing this function to always return true fixes the problem (in a bad way, of course).

The only mystery to me is why 3.0-rc3 vanilla (whose uname version should be 3.0-rc3) did not cause the same problem for you, Frank.

Regardless, I don't think Ubuntu's uname version is unusual, so Virtualbox should be fixed to recognize the new format.

[Frank Mehnert]

3.0-rc3 vanialla returns 3.0.0-rc3 as uname.

[Frank Mehnert]

That problem will be fixed in the next maintenance release.

[Frank Mehnert]

Fix in VBox 4.0.10.

[cmichallek]

this bug is still present with debian wheezy kernel 3.0.0-1-amd64 and Virtualbox 4.0 OSE, Virtualbox 4.0.12 and Virtualbox 4.1.

Here is my CPU flags section, to be sure that vmx is there:

flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dts tpr_shadow vnmi flexpriority

greetings

Christian

[Frank Mehnert]

A VBox.log file is missing. Just create one with a VM which does not require VT-x.

[cmichallek]

Vbox.log from Windows 7 64 guest which wont boot

[cmichallek]

Vbox.log from Windows XP 32bit guest

[cmichallek]

Replying to frank:

A VBox.log file is missing. Just create one with a VM which does not require VT-x.

the 64bit guest produced a logfile too, so i added them both

[Frank Mehnert]

The log file shows that the VT-x extension is disabled, see VERR_VMX_MSR_LOCKED_OR_DISABLED. Reboot your PC, enter the BIOS setup and activate the VT-x extension in the BIOS. Some BIOSes deactivate it by default.

[cmichallek]

sorry for the late reply, VT-x was enabled, but trusted execution too. Which seems to disable the VT-x somehow.

greetings