VERR_VMX_NO_VMX and BSOD on win 10

[fean9r]

Dear all,

first of all thanks for your time and help.

My issue is the following:
I have different 64 bit linux virtual machines and I launch them from Windows using VirtualBox-5.1.8-111374-Win.
Everything was working fine until I made an update of windows 10. After that I'm not longer able to open a virtual machine, and
when I try, I get either a VirtualBox - Error popup with the following details:

VT-x is not available (VERR_VMX_NO_VMX).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

or an horrible crash with Blue Screen Of Death and stop code SYSTEM_SERVICE_EXCEPTION.

I tried to update VirtualBox to the 5.1.12 r112440 win but it doesn't solve the problem.
Making many researches, I found guides explaining similar issues and advising to enable the VT-x in the BIOS and to turn off the Hyper-V in Windows features. I checked them but they where already correctly configured. Then I noticed that I'm no loger able to create new 64 bit machine but only 32 bit ones.

I suppose an incompatibility between VirtualBox and the last updates of Windows 10 or a windows bug.

Can you help me to solve this mess?

Thank very much!

[scottgus1]

enable the VT-x in the BIOS and to turn off the Hyper-V in Windows features. I checked them but they where already correctly configured. Then I noticed that I'm no loger able to create new 64 bit machine but only 32 bit ones

You are on the right track. See I have a 64bit host, but can't install 64bit guests I believe that turning on VT-x in the BIOS requires a complete power off to take effect.

[fean9r]

Unfortunately I rebooted and halted my pc many times but the problem persists.

[scottgus1]

The "no-vmx" log does show:

Code: Select all

00:00:02.989736 VMSetError: VT-x is not available

The linked tutorial also mentions other things besides Hyper-V and BIOS that could take over VT-x and prevent Virtualbox from using it.

[fean9r]

The linked tutorial also mentions other things besides Hyper-V and BIOS that could take over VT-x and prevent Virtualbox from using it.

Thanks for your idea!

Looking in msinfo32 I found that there is something called Device Guard running and it seems to be a Win 10 feature related to virtualization.
May it be the thing that prevents VirtualBox to use the VT-x ??

[scottgus1]

Googling shows it could be.

[fean9r]

I think this is the problem..

Virtualization applications do not work together with Hyper-V, Device Guard, and Credential Guard
reference:
support.microsoft.com/en-in/kb/3204980

[BillG]

That could be the problem if you are running Windows Enterprise in a domain environment. Otherwise you will not have credential guard.

There was a discussion about this recently in the Technet forum.

https://social.technet.microsoft.com/Fo ... rverhyperv

[fean9r]

Following the guide, I managed to remove credential guard, device guard and the secure boot.

The problem persists, but now instead of a BSOD on my 64 bit machines I get this one:
VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot.
Then the machines fails to load.

In the VirtualBox log I have :

Code: Select all

 00:00:01.836402 WARNING! 64-bit guest type selected but the host CPU does NOT support HW virtualization. 

I repete, in my BIOS I have enabled the HW virtualization.

Thanks for your help again!

[scottgus1]

Post that complete log, zipped, please. I would like to see what the CPU type is.

You can look, too. Look for a line that has something like this in it:

Code: Select all

CPUM: Matched host CPU INTEL 0x6/0x3f/0x2 Intel_Core7_Haswell with CPU DB entry 'Intel Core i7-5600U' (INTEL 0x6/0x3d/0x4 Intel_Core7_Broadwell)

Likely your processor will be different than mine. but the "CPUM: Matched host " part should be the same.

Also, in an Explorer window, right click "This PC", then Properties. Under System, Processor, it should say what CPU you have. Please post that info.

[fean9r]

This is my line:

Code: Select all

CPUM: Matched host CPU INTEL 0x6/0x45/0x1 Intel_Core7_Haswell with CPU DB entry 'Intel Core i7-5600U' (INTEL 0x6/0x3d/0x4 Intel_Core7_Broadwell)

from msinfo:
Processor Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, 2701 Mhz, 2 Core(s), 4 Logical Processor(s)

[scottgus1]

I think there's a glitch here. Your Msinfo32 says a i7-4600U and the Vbox log says i7-5600U. (Both of which are VT-x capable according to Intel.)

My msinfo32 says:

Code: Select all

Processor	Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s)

and my Vbox.log also says "i7-5600U"

Something's wrong in the log.

I am running VB 5.1.6, Windows 10 Pro Anniversary Edition, but my guests are running fine. Don't know what else to do myself.

[Perryg]

If "execute protection" is enabled in the bios, disable it and see if that helps.

[Martin]

This is my line:

Code: Select all

CPUM: Matched host CPU INTEL 0x6/0x45/0x1 Intel_Core7_Haswell with CPU DB entry 'Intel Core i7-5600U' (INTEL 0x6/0x3d/0x4 Intel_Core7_Broadwell)

from msinfo:
Processor Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz, 2701 Mhz, 2 Core(s), 4 Logical Processor(s)

The "Matched host CPU with DB entry" line is just a rough match, the correct CPU type can be found near the end of the CPUID dump section in the log:
00:00:03.361640 Full Name: "Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz"

[scottgus1]

Sure enough, Martin, thanks for the correction! I wonder why that "almost" line is in the log...

fean9r, your log is showing your cpu correctly at the place Martin points out, as well as does mine. Sorry for the red herring.

As to why you're not able to get VT-x to come through, it's a really good question if the tutorial didn't help...