Cannot start any VM (Win 10; 64-Bit; VBOX_E_IPRT_ERROR, VERR_VMX_UNABLE_TO_START_VM)

[basti-tee]

Hi community,

I have the problem that I cannot startup any virtual machine in my VBox installation. I run Win 10.0.10586 and the latest VirtualBox 5.0.22 r108108. The error in the UI can be seen in the attached screenshot. It seems to break during or even prior to loading the ISO images on initial startup/installation. I used various Xubuntu/Lubuntu install ISOs and minimal ISOs.

The logs indicate something related to

1) VBOX_E_IPRT_ERROR.

Code: Select all

00:00:04.498042 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={7303a66d-433b-25a4-f9a8-fcadf87e0c2a} aComponent={DisplayWrap} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:00:04.498210 ERROR [COM]: aRC=E_INVALIDARG (0x80070057) aIID={7303a66d-433b-25a4-f9a8-fcadf87e0c2a} aComponent={DisplayWrap} aText={Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)}, preserve=false aResultDetail=0

2) VERR_VMX_UNABLE_TO_START_VM

Code: Select all

00:00:03.489034 HM: VERR_VMX_UNABLE_TO_START_VM:
00:00:03.489056 HM: CPU[0] Instruction error    0x7
00:00:03.489062 HM: CPU[0] Exit reason          0x0
00:00:03.489065 HM: CPU[0] PinCtls          0x7f
00:00:03.489070 HM: CPU[0] ProcCtls         0xb5a0edfe
00:00:03.489073 HM: CPU[0] ProcCtls2        0xeb
00:00:03.489077 HM: CPU[0] EntryCtls        0x11ff
00:00:03.489080 HM: CPU[0] ExitCtls         0x436fff
00:00:03.489084 HM: CPU[0] HCPhysMsrBitmap  0x00000000da252000
00:00:03.489088 HM: CPU[0] HCPhysGuestMsr   0x00000000da251000
00:00:03.489092 HM: CPU[0] HCPhysHostMsr    0x00000000da24e000
00:00:03.489095 HM: CPU[0] cMsrs            1
00:00:03.489099 HM: VERR_VMX_UNABLE_TO_START_VM: VM-entry allowed    0xffff
00:00:03.489102 HM: VERR_VMX_UNABLE_TO_START_VM: VM-entry disallowed 0x11ff

I searched the forum, but couldn't find anything helpful, even though that other users had the same error. What I can already take out of the equation:

- Broken ISO download (I tried different ones and checked the checksums - 100% correct)
- Re-installing Virtual Box (No effect)
- Re-starting the machine (no effect)
- Reducing guest memory (1-4 GB of 8 GB total , no effect)
- Tested influence of anti-vir guard (only running windows defender, no change after temporary disabling)
- Deinstalled anything remotely related to virtualization (teamviewer, daemon tools, etc)
- Deinstalled Windows updates that came after 12/15: 3149135, 3140768, 3135173, 3124263, 3116900 , 3140743 , 3124262, 3124200 , 3116908 , 3120677 (lead to Windows 10.0 1511 10586.0 )
- Disabling and enabling VT-X support in BIOS (no effect)
- Trying out different VBox version (tried 4.3 to current to development/test builds -> always the same)
- Fiddeling around with virtualization settings in VB (no effect, back to default settings)
- Checked for error from HardeningLog supR3HardenedMonitor_LdrLoadDll: error opening 'C:\WINDOWS\system32\wintab32.dll - seems to be an error that won't stop VB from operating - nothing changed

Twice during my tests I even received a windows bluescreen together with an auto-reboot of my machine (see blueshot.jpg attachment).

My VBox system settings:

- Base Memory: 768 MB
- Chipset: PIIX3
- Extended Features: [X] I/O APIC [ ] Enable EFI [X] HW Clock
- Processor: 1 CPU, 100 % Execution Cap
- Extended Features: [ ] Enable PAE/NX
- Acceleration: Paravirt. Interface: Default, [X] VT-X / AMD-V [X] Nested Paging

Any help would be appreciated.
Thanks in advance & best regards.

PS: I had to zip the logs due to filesize limitations.

[mpack]

It looks like VirtualBox was unable to initialize VT-x, which it requires in order to run Ubuntu (64bit).

What I can't tell you is why it can't access VT-x. You have a Win10 host but Hyper-v seems to be disabled (but check anyway). Failing that it's either another VM platform, or it's your AV software which is interfering: that said I'm not seeing third party AV present in the hardening log, and I'm pretty sure VBox has no problem with Windows Defender.

[basti-tee]

Hello mpack,

thanks very much for the reply and the insights. So you're saying another VM'ish applications might block the VT-X initialization?
By the way: I also tried to run the VM with Windows Defender disabled. Did not change anything.

But I'll have a look whether any applicaton might be responsible for such a thing. Is there something like a "black-sheep" list somewhere?


EDIT: I tested with Hyper-V as PV interface. No effect. Same error. And I also added my System-settings in the original post.

[mpack]

No, there's no "black sheep list" anywhere. The potential interactions are quiet complex, but I already covered the main headings: Hyper-v and non-Microsoft AV ("non-Microsoft" because the devs have obviously thoroughly tested the most obvious AV).

One thing I just noticed: your host build number is 10.0.10586.306. That in itself may be a black sheep. Here is a recent similar discussion concerning that build: viewtopic.php?f=6&t=67840&start=330#p363880.

Can you identify when you installed this Win10 build? Is it a fast track preview build?

[basti-tee]

Hmm, my system preferences indicate a different windows version: Windows 10 Home 1511 10586.420. Might be my update version whereas 306 is the initial build version /wo updates. It's not a preview build. I upgraded through the regular Microsoft program.

I can try to deinstall the cumulative updates. I am sure I already ran VBox on this machine at some point.

[mpack]

10586.306 is the build number reported in the hardening log. Unfortunately I'm currently at work where my PC runs Win7, so I can't check what my own Win10 host (at home) says. I'll try to remember to check this evening or tomorrow morning (it's 19:35 here now).

[basti-tee]

Thanks man! I am a patient person - no stress

Meanwhile I deinstalled the following Windows updates that came after 12/15:
3149135, 3140768, 3135173, 3124263, 3116900 , 3140743 , 3124262, 3124200 , 3116908 , 3120677

That gives me Windows 1511 10586.0

I also deinstalled anything remotely related to AV or Virtualization. Which was basically daemon tools, teamviewer and some smaller apps.

Result: Nothing changed.

[mpack]

Ok, it's a red herring. At home my own VBoxHardening.log says 10586.306 even though WinVer says 10586.420. Tomorrow if I have the energy I'll try a more detailed comparison. Here's mine if you want to have a go. I have no problem starting this VM or any other.

[basti-tee]

Meanwhile I tried using the VMWare Player with more or less the same error. I will have a closer look to the corresponding logs for other indications, but it seems to be closely related to the blocked VX-T that mpack proposed.

[basti-tee]

Okay, I give up

I removed more or less all of my apps and my windows was very close to mint condition. The only thing I didn't tried, was to re-install/reset Windows completely. I don't know. Can this be hardware related? I used some Intel diagnosis apps where all of em displayed my VT-X as available. I read all the logs from that post here, but I see no real indication besides the one's mentioned. And after all I am not VBox-Engineer enough to interpret all of it.

[Perryg]

Does the host have secure boot enabled in its bios? If so try disabling it and see if that helps.

[scottgus1]

I looked at the logs too. Mpack is a lot more skilled at interpreting those things than I am, but I didn't see anything that told me VT-x is unavailable. I hunted for references to VT-x, didn't see anything saying it wasn't usable, and did see a line saying "Using VT-x implementation 2.0". A working 64-bit Windows 7 guest I have at home has the same three references to VT-x in its log as the posted log. I'm missing the obvious somehow.

Someone correct me if I'm wrong, but if Virtualbox can't get to VT-x it would only show 32-bit OS's as guest types when trying to make a new guest. (This is what many forum posters report when they try a new guest and it turns out they did not turn on VT-x in the BIOS.) Could you please try to make a new guest and see if the available "recipes" are only 32-bit?

I have had an antivirus program get in the way of Virtualbox. (BitDefender, BTW)
You have Windows 10 Home, so hyper-v should not be present.

[Perryg]

Yes VBox sees VT-x as available but can not actually use it. VBox does not even see that something else is using it so it has to be an issue with something on the host and from experience I don't see it as being something else is using it. It has to be either the bios setting of secure boot or maybe even the processor in some fashion. I have not seen a processor like the one the OP has before. "Intel(R) Processor 5Y10 CPU @ 0.80GHz"

[scottgus1]

Perry or Mpack, could you please educate me on what you see in the log that says VT-x is available but can't be used? I'd like to know how to interpret the logs better.

[Perryg]

00:00:02.640913 ********************* End of CFGM dump **********************
00:00:02.640926 VM: fHMEnabled=true (configured) fRecompileUser=false fRecompileSupervisor=false
00:00:02.640928 VM: fRawRing1Enabled=false CSAM=true PATM=true
00:00:02.641074 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support
00:00:02.641128 MM: cbHyperHeap=0x100000 (1048576)
00:00:02.644171 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x7
00:00:02.645312 CPUM: Matched host CPU INTEL 0x6/0x3d/0x4 Intel_Core7_Broadwell with CPU DB entry 'Intel Core i7-5600U' (INTEL 0x6/0x3d/0x4 Intel_Core7_Broadwell)

00:00:03.489099 HM: VERR_VMX_UNABLE_TO_START_VM: VM-entry allowed 0xffff
00:00:03.489102 HM: VERR_VMX_UNABLE_TO_START_VM: VM-entry disallowed 0x11ff
00:00:03.489113 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:03.489113 !!
00:00:03.489114 !! Guru Meditation -4005 (VERR_VMX_UNABLE_TO_START_VM)

In the first section it sees VT-x and it does not say it is being used by something else, which it would say if hyper-v or anything else was using it. The wording would be something like not available in bios or disabled or something like that.

The second part is the failure and I have not seen the exact error before but it looks like the service is being refused and not missing or used by something else.