Hyper-V host blue screens (BSOD) after being added to SCVMM

Description

When rebooting a Hyper-V host running on VMware Workstation after adding it to System Center Virtual Machine Manager (SCVMM), the host will not boot & blue screens (BSOD).

Cause

When a Hyper-V host is added to SCVMM, several hardware IDs are added to the Multi path I/O (MPIO) list. One of these hardware IDs are not compatible on VMware Workstation.

Information
To see a list of hardware IDs added by SCVMM run:

Get-MSDSMSupportedHW

It’s worth noting that when the MPIO role is installed, the only ID in the list is a generic entry for Vendor 8 Product 16.

Solution

Boot the Hyper-V host to the last known good configuration. Once it’s back up, add the Hyper-V host to SCVMM again. Before rebooting, remove the MPIO entry for MSFT2011SASBusType_0xA by running the following PowerShell command:

Remove-MSDSMSupportedHW -VendorId "MSFT2011" -ProductId "SASBusType_0xA"

Now reboot the Hyper-V host.

 

STOP: 0x0000007B

Warning: This post deal with editing the registry. If you don’t know what that is stop right here & ask someone else to help you. Using the registry editor incorrectly can cause serious problems that may require you to reinstall Windows. Use the registry editor at your own risk

The power supply in one of our computers died. It was an old Dell Optiplex GX270. I’ve had problems in the past with that model’s power supply so I didn’t even want to bother ordering a new one.

I had plenty of spare computers that I could just move the hard drive to. So I take the hard drive out of the GX270 & put it in a GX260 & turn it on. I get a BSOD  with a STOP: 0x0000007B (0xF894F528,0xC0000034,0x00000000,0x00000000). Apparently the hard drive controllers are different enought that Windows didn’t like it.

Doing a little tube searching I came across KB314802. It gives you a nice little reg file to import into the registry. I didn’t need to copy the files it mentions because they were already there. Using BartPE I was able to import the registry settings. Rebooted one more time & Windows came right up! Just had to install the chipset, audio, & video driver then all was good again.

This link has the notes on using BartPE to import the reg file.

http://windowsxp.mvps.org/peboot.htm