windows 10 pro no start when hyper-v is enabled

[Daimroc]

I have installed VirtualBox 5.0.0 and I have enabled hyper-v on windows 10. If I reboot windows does not boot, it stop in the screen with the 5 spheres rounding (load screen).

If I disabled VT in the bios, then I can start windows, disabled hyper-v, reboot, enabled VT in BIOS and now I can boot. But in this case I have not hyper-v, which I need to use some emulator for developing.

There is some way to disabled VirtualBox to avoid that try to take control of VT in the boot to allow to hyper-V to use it? It seems that in the boot, VirtualBox and Hyper-V try to get control of the VT and then there is a conflict.

It's very tedious to have to disabled hyper-v and change the bios configuration when I want to use hpyer-v for emulators and change it again if I want to use virtualBox.



Thank you so much.

[Perryg]

There is some way to disabled VirtualBox to avoid that try to take control of VT in the boot to allow to hyper-V to use it? It seems that in the boot, VirtualBox and Hyper-V try to get control of the VT and then there is a conflict.

True statement but backwards. VirtualBox can share the control of VMX, it is hyper-v that takes total control and will not share it or play nice. I believe you should ask a MS hyper-v forum why they don't play nice.

[BillG]

The reason they don't work together is that If you have Hyper-V enabled, Hyper-V loads even before the OS, so the hardware virtualization is locked before the OS loads. The host OS sits on top of the hypervisor and does not have direct access to the hardware: it can only access the hardware through the hypervisor like a vm does. (And as you know, VirtualBox cannot use hardware virtualization if it is running in a vm).