[vbox-dev] VirtualBox on Win 10 with Hyper-V/CredentialsGuard enabled

Mikhail Kovalev mikhail.kovalev at gmail.com
Tue Mar 21 10:17:29 UTC 2017


in the current state VirtualBox doesn't work on Win10 in case if Hyper-V is
enabled. I do understand that VT-x is not available for VirtualBox in that
case, but at least the 32-bit VMs could work without VT-x.
In the bug ticket #15780, Frank wrote

"VirtualBox <https://www.virtualbox.org/wiki/VirtualBox> is trying to
change the CR4 value but the host crashes try to do so. The reason is most
likely that Hyper-V is active. Please try to disable Hyper-V".

So this is a Hyper-V bug and nothing can be done on the VirtualBox side to
fix this? Or is there a chance that this problem will get fixed in the
upcoming releases of VirtualBox?

If I additionally enable the CredentialsGuard with Virtualization Based
Protection for Code Integrity (without activating Code Integrity Policies)
on Win 10, then VirtualBox crashes even earlier with "Failed to load
VMMR0.r0". I guess this is a different issue and it's unrelated to the
BSOD. I would create a bug ticket for that, but it probably doesn't make
much sense currently because of the BSOD problem.

Thnx & best regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20170321/bf2a26a1/attachment.html>

More information about the vbox-dev mailing list