Using System Center Virtual Machine Manager 2008 R2 to delete a VM on a shared LUN causes the other VMs to fail

Symptoms

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.

Cause

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 [2960] 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 [2960] 0B90.0F1C::06/22-15:39:56.848#04:WsmanAPIWrapper.cs(544): HostSessionCache: elements for [S-1-5-18-hypervhost1.contoso.com]: [100]
00000954 30.60273933 [2960] 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]

Resolution

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.

More Information

This problem does not occur if you are using Clustered Shared Volumes (CSV).

This issue only affects System Center Virtual Machine Manager 2008 R2.

Properties

Article ID: 2423004 - Last Review: Sep 30, 2010 - Revision: 1

Feedback