Well not a day after my blog post Extra Info on Clustering & Hyper-V with Dynamic Memory When You Start With Windows Server 2008 R2 SP1on important hotfixes for Hyper-V clustering with Windows Server 2008 R2 SP1 Microsoft releases a new hot fix for issue below. I’ll add it to the post to keep up to date.
Stop error 0x0000007a occurs on a virtual machine that is running on a Windows Server 2008 R2-based failover cluster with a cluster shared volume, and the state of the CSV is switched to redirected access
The KB article with instructions on how to get the hot fix is here: http://support.microsoft.com/kb/2494016/en-us?sd=rss&spid=14134
The scenario is detailed as follows:
Consider the following scenario:
- You enable the cluster shared volume (CSV) feature on a Windows Server 2008 R2-based failover cluster.
- You create a virtual machine on the CSV on a cluster node.
- You start the virtual machine on the cluster node.
- You move the CSV owner to another cluster node, and you change the state of CSV to redirected access.
- The connection that is used for redirected access is switched to another connection when one of the following scenarios occurs:
- The cable for local area network (LAN) is disconnected.
- The related network adapter is disabled.
- The connection is switched by using Failover Cluster Manager.
In this scenario, you receive a Stop error message that resembles the following in the virtual machine:
STOP 0x0000007a ( parameter1 , parameter2 , parameter3 , parameter4 )
KERNEL_DATA_INPAGE_ERROR
Note
- The parameters in this Stop error message vary, depending on the configuration of the computer.
- Not all "0x0000007a" Stop error messages are caused by this issue.
- You may also receive other Stop error messages when this issue occurs. For example, you may receive a "0x0000004F" Stop error message.
Were there any other factors in addition to the redirect IO that caused this issue or was it a common issue?
No other factors involved as far as I know. This is a very uncommon scenario, not all conditions will be met that often. So no this was not a common issue (for stats on that you’d need to asks Microsoft) and I’ve never seen it in in the wild. All those condition being met in production would require moving the CSV owner to another cluster node and changing the state of CSV to redirected access a failure & failover of the CSV network.
Thank you very much for your response. It might not be the issue were experiencing, will have to do more testing.