X370 Killer SLI: Bios 5.1 fail boot Hyper-V

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I have the following setup:

I have a Windows Hyper V 2016 working on X370 (Bios 3.5) with AMD Ryzen 1700.  I also enabled SVM in CPU configuration.  I can use the start hyper-v guest machine as usual.

Next, I upgrade the BIOS to version 5.10 on the same system.  This time, the machine can boot but it will somehow stop at a Windows blue screen (BSOD) with error: Inaccessible Boot Device

I then disable SVM in bios and the windows hyper-v can boot.  But I won't be able to use the hypervisor feature - cannot start virtual machine.

I have updated the Windows to latest available update.  This problem doesn't happen in BIOS 3.5 but fail at BIOS 5.1.

I can confirm it is hardware issue.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
ccy Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 30 Jan 2018 Status: Offline Points: 7	Post Options Post Reply Quote ccy Report Post Thanks(0) Quote Reply Topic: X370 Killer SLI: Bios 5.1 fail boot Hyper-V Posted: 14 Jan 2019 at 11:31am
	I have the following setup: I have a Windows Hyper V 2016 working on X370 (Bios 3.5) with AMD Ryzen 1700. I also enabled SVM in CPU configuration. I can use the start hyper-v guest machine as usual. Next, I upgrade the BIOS to version 5.10 on the same system. This time, the machine can boot but it will somehow stop at a Windows blue screen (BSOD) with error: Inaccessible Boot Device I then disable SVM in bios and the windows hyper-v can boot. But I won't be able to use the hypervisor feature - cannot start virtual machine. I have updated the Windows to latest available update. This problem doesn't happen in BIOS 3.5 but fail at BIOS 5.1. I can confirm it is hardware issue.

xhue Members Profile Send Private Message Find Members Posts Add to Buddy List Groupie Joined: 17 Aug 2018 Status: Offline Points: 634	Post Options Post Reply Quote xhue Report Post Thanks(0) Quote Reply Posted: 15 Jan 2019 at 4:33am
	I'm pretty sure new BIOS will most likely break the host hypervisor, especially if we're talking 'bare-metal' hypervisors or just ASRock. ASRock couldn't manage to solve the VM stuff on their flagship mobos for nearly 2 years, so it wouldn't surprise me if they broke it in the new BIOS. It never hurts to open a ticket with them. New BIOS should generally come with a fresh hypervisor install, unless we're talking mission-critical enterprise systems (KVM, VMware, etc.) where this is usually not required. Even more so, in your case we're talking about new AGESA from AMD. Proper VM designs will decouple the guest VMs and their storage from the host OS, so update, damage or migration of the later should be less of an issue. After you update to 5.50 I suggest you clear CMOS, and clear it good. Then try setting the IOMMU, SR-IOV, SVM, etc. and re-deploy Win 2016 from scratch. If this fails, get an ASUS, as did I.