Jump to content
RESET Forums (homeservershow.com)

hyper v causes bsod on win 10 host


Recommended Posts

HI, I had my ml10v2 set up and running win 10 pro nicely.


I tried to enable hyper v in programs and settings and it accepted it and installed and rebooted.  On the reboot I got the dreaded "inacessible_boot_device".


logging into windows safe mode and disabling hype-v fixes it.


I am running the os (128gb ssd) on port 1 of the b120i, and the bios is set to enable sata ahci support.


I believe it is either a driver problem or a bios issue.


My questions are:


what do I need to change to get hyper-v to run on the ml10v2?


Am I in the right bios sata mode?


Could it be a driver issue in win 10 pro, which was a clean install?


Does anyone know what the correct substitute drivers are for win 10: ie when a win 10 driver is not available, is it better to use a server 2008 or 2012?



Link to comment
Share on other sites

  • 2 months later...

I installed 2012r2 datacenter on my ml10v2, installed hyper-v and have 3 VM's running (2012r2 standard, WHS2011, and Win7 enterprise client).  No issues running all 3 at same time (so far).

Link to comment
Share on other sites

  • 2 months later...

I have the exact same issue. The only way to fix it is to disable vt-d in the bios, which then ruins the whole point of VMs for me. Pete, are you running xeon chip with vt-d enabled?


just stumbled across this, it looks like vt-d is the root cause for my ml10v2 as well https://community.hpe.com/t5/ProLiant-Servers-ML-DL-SL/ML310e-Gen8-V2-with-Server-2016-Hyper-V/td-p/6912878

Edited by rexii454
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...