Running a Virtual Machine when Windows Hyper-V is enabled should NOT Crash Windows
|Reported by:||Will||Owned by:|
|Guest type:||all||Host type:||Windows|
VirtualBox can not run on Windows 10 when Hyper-V mode is ACTIVE (ON). However the existing behaviour is pathological and must be corrected.
Running a VM when Hyper-V is ON causes the BSOD!
- Windows boots with Hyper-V enabled
- Start-up VirtualBox Manager GUI
- START an existing VM
- VM begins to load
- The dread Windows BSOD (Blue Screen of Death) appears
- Windows dies -- generates crash log, etc.
- Windows reboots
- NOTE: Hyper-V is still active and must be deactivated manually.
- Check for Hyper-V mode is: OFF, at start-up for all VirtualBox tools; especially:
- VirtualBox Manager GUI and
- VM shell itself
- Issue a WARNING pop-up or error message for command line Reporting that Hyper-V mode is active and VirtualBox cannot run while there is another hypervisor active. Or some such.
- Exit the VirtualMachine (shell) once the Hyper-V Active
status is reported.
- Thus Avoiding the BSOD
Optional / suggestion:
- It would be useful for the warning to tell users how to disable/enable Hyper-V as part of the warning message(s).
- Another helpful feature is for the VirtualBox management GUI to turn Hyper-V off or on from a menu.
Related / supplementary notes:
There seem to be several issues that mention Hyper-V troubles. Some are real bugs and some look like misunderstandings.
In my opinion no software should cause a system crash-dump when it can be prevented by checking some system configuration attributes.