VirtualBox 6.0 and Hyper-V

[Larswa]

What do you mean by "the forum does not support vms running under vagrant" ?

It means exactly what Bill said. We don't support Vagrant here, only the official VirtualBox install. That doesn't mean it won't work, it means take your support questions to the Vagrant forum.

Thanks. Understood.

[klaus]

FYI, in the mean time I received additional information about VERR_NEM_MISSING_KERNEL_API: it's a known issue and we'll see that we fix it until the next release.

[evil_gr]

I wonder if there are API availability differences between the Windows 10 editions, i.e. Home/Pro (and maybe the S mode also has an effect)

I am using Windows 10 Enteprise LTSC 2019 edition - maybe that does the trick. Also, I have active WLS subsystem, and this is the reason I need VirtualBox working along with enabled Hyper-V instead of switching it off.

[kwinz]

Seeing as how the Hypervisor Platform API is so broken. And also if it works the performance is not good.

Would it not be better (at least on Intel) to enable

Code: Select all

Set-VMProcessor -VMName <VMName> -ExposeVirtualizationExtensions $true

for the main Windows 10 OS client of Hyper-V?
So that VirtualBox can run its own virtualization on top?
I don't know what to put for the VMName though. Is this feasible?

[kwinz]

Related: https://github.com/microsoft/WSL/issues/5030

[the big foot]

i have a problem with that as well my host windows 10 and i wanna run windows 7 as a vm.
i have tried everything regarding hyper-v and i am sure its disabled.
from the windows feature hyper- v and container and windows sand box and virtual machine plat form all r disabled and i used the CMD to disable hyper.
mine still doesn't work and it gives the turtle icon instead of the V. please any help will be appreciated.

[BillG]

Have you used the bcdedit command to prevent the hypervisor from loading, and rebooted at least once (preferably twice)?

bcdedit /set hypervisorlaunchtype Off

If you are getting the turtle, the hypervisor is still loading and VirtualBox cannot use hardware virtualization.

[the big foot]

yes and even i ADD the option that when i start my computer it asks me if i need a Hyper-V TO WORK OR WITHOUT.


ANY HELP WILL BE REALLY APPRECIATED I REALLY WANT VIRTUAL BOX TO WORK.
THANK U SO MUCH!!

[klaus]

Next week there will be a new release, and while it doesn't have much actual change in this code area, it will give better diagnostics to figure out what exactly is going wrong. Our developer couldn't reproduce any trouble with recent Windows 10 releases and the Insider Preview as of some weeks ago.

[kwinz]

Have you used the bcdedit command to prevent the hypervisor from loading, and rebooted at least once (preferably twice)?

bcdedit /set hypervisorlaunchtype Off

If you are getting the turtle, the hypervisor is still loading and VirtualBox cannot use hardware virtualization.

But I *want* Hyper-V to run. So I can use Credential Guard, WSL 2.0, etc.
I just also want Hyper-V to expose/emulate VT-x ("ExposeVirtualizationExtensions" https://wibier.me/expose-virtualization ... l-machine/).
For some reason it can not be(?) enabled and instead Virtualbox is now bending over backwards to adopt Microsoft's virtualization backend.

Or am I missing something?

[klaus]

But I *want* Hyper-V to run. So I can use Credential Guard, WSL 2.0, etc.
I just also want Hyper-V to expose/emulate VT-x ("ExposeVirtualizationExtensions" https://wibier.me/expose-virtualization ... l-machine/).
For some reason it can not be(?) enabled and instead Virtualbox is now bending over backwards to adopt Microsoft's virtualization backend.

Or am I missing something?

Yes, you're missing the fact that if Hyper-V is enabled then VirtualBox cannot use VT-x. All it can do is rely on Hyper-V. That's how Microsoft decided it has to be. You're running VirtualBox in the Hyper-V root domain (at least that's how I understand it) which never gets the virtualization extensions.

If you want to let VirtualBox use the emulated VT-x you need to create a separate Hyper-V VM and run VirtualBox there. May or may not work, we're not testing this case currently.

[kferhat]

Hello everyone,

I have the same problem and I do all the ticks without any result :

Code: Select all

00:00:03.886329 MM: cbHyperHeap=0x100000 (1048576)
00:00:03.888007 CPUM: No hardware-virtualization capability detected
00:00:03.889377 CPUM: fXStateHostMask=0x7; initial: 0x7; host XCR0=0x1f
00:00:03.891621 CPUM: Matched host CPU INTEL 0x6/0x4e/0x3 Intel_Core7_Skylake with CPU DB entry 'Intel Core i7-6700K' (INTEL 0x6/0x5e/0x3 Intel_Core7_Skylake)
00:00:03.891678 CPUM: MXCSR_MASK=0xffff (host: 0xffff)
00:00:03.891700 CPUM: Microcode revision 0x000000C6
00:00:03.891719 CPUM: MSR/CPUID reconciliation insert: 0x0000010b IA32_FLUSH_CMD
00:00:03.891727 CPUM: MSR/CPUID reconciliation insert: 0x0000010a IA32_ARCH_CAPABILITIES
00:00:03.891735 CPUM: MSR fudge: 0x00000122 IA32_TSX_CTRL
00:00:03.891758 CPUM: SetGuestCpuIdFeature: Enabled SYSENTER/EXIT
00:00:03.891763 CPUM: SetGuestCpuIdFeature: Enabled SYSCALL/RET
00:00:03.891768 CPUM: SetGuestCpuIdFeature: Enabled PAE
00:00:03.891772 CPUM: SetGuestCpuIdFeature: Enabled LONG MODE
00:00:03.891776 CPUM: SetGuestCpuIdFeature: Enabled LAHF/SAHF
00:00:03.891780 CPUM: SetGuestCpuIdFeature: Enabled NX
00:00:03.894663 VMSetError: F:\tinderbox\win-6.0\src\VBox\VMM\VMMR3\NEMR3Native-win.cpp(1463) int __cdecl nemR3NativeInitAfterCPUM(struct VM *); rc=VERR_NEM_VM_CREATE_FAILED
00:00:03.894724 VMSetError: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87)
00:00:03.894769 NEM: Destroying partition 0000000001be5050 with its 0 VCpus...
00:00:03.898300 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)}, preserve=false aResultDetail=-6805
00:00:03.898672 Console: Machine state changed to 'PoweredOff'
00:00:03.938203 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, rc=E_FAIL (0X80004005))
00:00:04.439141 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:04.439226 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={ab4164db-c13e-4dab-842d-61ee3f0c1e87} aComponent={DisplayWrap} aText={The console is not powered up}, preserve=false aResultDetail=0
00:00:04.439912 GUI: Aborting startup due to power up progress issue detected...

I'm on windows 10 1909 build 18363.720

Please Help me on this, I'm on it 3 days ...

[bird]

Hi kferhat and others with trouble starting VMs when Hyper-V is enabled.

To help reproduce / fix, I would very much like to know which windows features you have enabled in the "Turn Windows features on or off" list. Some screenshots with the enabled branches fully expanded would be nice.

At a minimum, could you report back whether the "Windows Hypervisor Platform" feature is enabled or not.

Cheers,
bird.

[kferhat]

Hello Bird,

Thank you so much for the replay.

So I try everything : Enabling and disabling all the features.

I disabled also "Windows Hypervisor Platform" and get the same error.

Now this is the state is in the attachment.

[BillG]

Enabling only the Windows Hypervisor Platform and no other Hyper-V features will allow VirtualBox guests to run OK, but I think this is only because enabling only the Windows Hypervisor Platform does not change the hypervisorlaunchtype setting in bcdedit, so the hypervisor does not load, even after a reboot. As soon as the hypervisor loads, we are back to the turtle icon and VERY slow vm.

Windows 10 Pro build 18363.778 VirtualBox 6.1.6 .



Task manager shows VirtualBox Virtual Machine using 25-29% CPU

Win7Later.PNG

Much to my surprise, my 32-bit XP and Win2000 vms will run with this setup. Windows 7 x64 still at trying to start.

W2k.PNG