Using System Center Virtual Machine Manager 2008 R2 to delete a VM on a shared LUN causes the other VMs to fail
You are using Hyper-V and a Failover Cluster and your Virtual Machines (VMs) share the same Clustered LUN to hold the VHD for the VMs. You are also using System Center Virtual Machine Manager 2008 R2 (SCVMM) to manage your environment.
If you delete a VM that resides on a LUN which is shared with another VM, the other VM may fail.
When SCVMM deletes the selected VM, it also frees up the Clustered LUN and returns it to the "Available Storage" Group. The remaining VMs on this LUN lose their dependency.
In a cluster Trace you will see the following entries during the delete of a VM:
00000952 30.59181404  0B90.0F1C::06/22-15:39:56.848#04:WsmanAPIWrapper.cs(1415): WSMAN: URL: [http://hypervhost1.contoso.com:80] Verb: [INVOKE], method: [GetGroupType], resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/mscluster/MSCluster_ResourceGroup?Name=Available Storage]
00000953 30.59195137  0B90.0F1C::06/22-15:39:56.848#04:WsmanAPIWrapper.cs(544): HostSessionCache: elements for [S-1-5-18-hypervhost1.contoso.com]: 
00000954 30.60273933  0B90.0F1C::06/22-15:39:56.859#04:WsmanAPIWrapper.cs(1415): WSMAN: URL: [http://hypervhost1.contoso.com:80] Verb: [INVOKE], method: [MoveToNewGroup], resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/mscluster/MSCluster_Resource?Name=Classic Shared 50Gb]
This is by design. System Center Virtual Machine Manager was not designed to allow management of this shared configuration. Sharing a LUN across multiple Virtual Machines is an unsupported configuration and may lead to undesirable effects.
This problem does not occur if you are using Clustered Shared Volumes (CSV).
This issue only affects System Center Virtual Machine Manager 2008 R2.
Article ID: 2423004 - Last Review: 09/30/2010 14:14:00 - Revision: 1.0
Microsoft System Center Virtual Machine Manager 2008, Microsoft System Center Virtual Machine Manager 2008 R2 Workgroup Edition