I just saw an update to KB2855336 (the update rollup) was updated with additional text:
If you have a Windows Server 2012-based Hyper-V cluster that uses NIC Teaming with virtual LAN (VLAN), and you install this update rollup before July 12, 2013, you may receive an "0x000000D1" Stop error when you perform a live migration of a virtual machine. For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: KB2866029 "0x000000D1" Stop error when you perform a live migration of a virtual machine on a Windows Server 2012-based cluster.
Over on KB2866029 we can see:
Symptoms
Consider the following scenario:
- You have a Windows Server 2012-based Hyper-V cluster that uses NIC Teaming with virtual LAN (VLAN).
- You perform a live migration of a virtual machine.
- You perform a live migration of the virtual machine back to the original host.
In this scenario, the host computer crashes. Additionally, you receive the following Stop error message:
STOP: 0x000000D1 (parameter1, parameter2, parameter3, parameter4)
Notes
- This issue occurs after you install update rollup KB2855336
- This Stop error describes an IRQL_NOT_LESS_OR_EQUAL issue.
The fix is to install the reoffered update rollup KB2855336, available through Windows Update.
My advice:
- If your hosts are broken now because you installed the July update rollup then reinstall the new update rollup.
- If you have not deployed the July update rollup then deny it, give it a couple of weeks, and then plan an install if there are no more reported issues.
This is a mess.
Thank goodness I just read this, my cluster started bouncing at 3 am in the middle of the night 2 days ago and I have been working on it all morning – recreating my NIC Teams, Virtual Switches, checking drivers – only to see this is the problem! Thanks so much for your blog, I read it faithfully each day!