virtual box settings issues

[mczakk]

Hi, i have two machines, a toshiba laptop and a self built pc.
both are running the same version of ubuntu 64 bit, and the same virtual box version, 5.0.12 r104815.

however, the acceleration tab on the 'system' page of the settings on the laptop is greyed out.

attached are screenshots from both machines, how can i change the laptop settings from hyper v to VTx accceleration?

thanks

virtual box on laptop

laptop.png (88.03 KiB) Viewed 5589 times

virtual box on pc

pc.png (91.73 KiB) Viewed 5589 times

[Perryg]

1) 64-bit guests ( or acceleration ) need hardware-virtualzation enabled in the hosts bios.

[mczakk]

Hardware visualisation is enabled in the host bios.
Both guest o/s are 32 bit windows 10

[Perryg]

For the one that acceleration is disabled on, post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[mczakk]

log attached

[mpack]

00:00:11.015166 HM: HMR3Init: Falling back to raw-mode: VT-x is not available

This says no VT-x is present, meaning you would be unable to install Win8 and later guests, or any 64bit guest. However your log identifies your CPU as an Intel i7-2635QM, which ark.intel says does support VT-x.

So, either you are running nested hypervisors, or you are other software (debugger, AV scanner) on the host which grabs VT-x, or VT-x is disabled in the host BIOS.

[Perryg]

VirtualBox uses this for a matching MSR scheme

Code: Select all

00:00:11.019831 CPUM: Matched host CPU INTEL 0x6/0x2a/0x7 Intel_Core7_SandyBridge with CPU DB entry 'Intel Core i7-2635QM' (INTEL 0x6/0x2a/0x7 Intel_Core7_SandyBridge)

But the actual processor is:

Code: Select all

00:00:11.203176 Full Name:                       "         Intel(R) Pentium(R) CPU B960 @ 2.20GHz"

http://ark.intel.com/products/59836/Int ... e-2_20-GHz

Which does not support VT-x.

[mpack]

Ah, that explains it.

[Perryg]

I wish I had a dollar for every time I read the first indicator. It bit me several times and now I don't do it so much.

[mczakk]

00:00:11.015166 HM: HMR3Init: Falling back to raw-mode: VT-x is not available

This says no VT-x is present, meaning you would be unable to install Win8 and later guests, or any 64bit guest. However your log identifies your CPU as an Intel i7-2635QM, which ark.intel says does support VT-x.

So, either you are running nested hypervisors, or you are other software (debugger, AV scanner) on the host which grabs VT-x, or VT-x is disabled in the host BIOS.

Ah, that explains it.

so even though my bios says vt-x is the hardware accelleration (see attactched photo of laptop bios), it will never be able to run windows 10?

[mpack]

It will never be able to run Win 8.0 or later, or any 64bit OS - as VirtualBox VMs, because VirtualBox requires VT-x for those guests.

[Perryg]

According to Intel the processor you have does not support VT-x. You would need to contact the PC manufacture to find out why this does not post as it should in BIOS.
I see that it mentions VT-x in your screen shot but not that it is actually using it [enabled]. Various manufactures use tactics like this to make you think you have something that you do not.

[mpack]

I wish I had a dollar for every time I read the first indicator. It bit me several times and now I don't do it so much.

For some reason I thought that the two CPU indicators had now been merged into one in recent logs, so I didn't look for the second one.

[mpack]

Various manufactures use tactics like this to make you think you have something that you do not.

The wording is odd too, "VT-x only". Why "only"?

[Perryg]

The wording is odd too, "VT-x only". Why "only"?

Not to mention that the right screen says when available. Anyway it does not matter. If the processor does not support it then that is the end of the discussion.