You configure a new virtual machine (VM) on a Windows Server 2008 R2 Hyper-V failover cluster. You install the operating system on the VM from a media image. You install Microsoft System Center Operat

Question

Options

• ADetach the media image from the VM configuration.
• BPlace the VMs VHD on a Cluster Shared Volume (CSV)
• CImplement Performance and Resource Optimization (PRO).
• DCopy the media image to the same disk as the VM, and mount the ISO file.

• A
  77% (17)
• B
  5% (1)
• C
  5% (1)
• D
  14% (3)

Explanation

Any HAVMs that share a non-CSV LUN are imported into VMM with Unsupported Cluster Configuration status. To resolve this issue, use Failover Cluster Manager to reconfigure the virtual machines to have their own LUNs. Then, in the VMM Administrator Console, use the Repair action with the Ignore option to refresh each virtual machine's status in VMM. In VMM2008R2, when you migrate a virtual machine into a cluster from a stand-alone host by using a SAN transfer, VMM checks all nodes in the cluster to ensure that each node can see the LUN and automatically creates a cluster disk resource for the LU N. Even though VMM automatically configures the cluster disk resource, it does not validate it. You must use the Validate a Configuration Wizard in Failover Cluster Management to validate the newly created cluster disk resource. To migrate a virtual machine out of a cluster to a stand-alone host, the virtual machine must be on a dedicated LUN that is not using CSV. Troubleshoot "Unsupported Cluster Configuration" Status for a Highly Available Virtual Machine To view the reason that a HAVM is in an Unsupported Cluster Configuration state, display the Hardware Configurationtab of theVirtual Machine Propertiesdialog box. Then, in the Advancedsettings, click Availability. If the virtual machine is in an Unsupported Cluster Configuration state, theDetailsarea displays the error that placed the virtual machine in that state. The following situations can cause Unsupported Cluster Configuration status: The virtual machine is on a non-CSV LUN that contains more than one virtual machine. If you have configured highly available virtual machines in Hyper-V to share the same LUN, and the LUN is not on a clustered file system (CSV) volume, you must update the virtual machine configurations in Failover Cluster Management and Hyper-V so that each resides on its own The virtual machine is using non-clustered storage. If the HAVM is stored on system drive C: or any disk that is not clustered, the virtual machine is placed in Unsupported Cluster Configuration state. To resolve this issue, ensure that all files and pass-through disks belonging to the virtual machine reside on clustered disks. A VMware HAVM is connected to a port group that does not exist on all nodes of the host cluster. On host clusters that VMM is managing, each port group must be configured on all ESXServer hosts in the cluster. If a virtual machine is configured with a port group that is not common to all hosts, the virtual machine has Unsupported Cluster Configuration status. You have detach the media image to be fully supported by VMM. If media is attached then migration may fail.

No community discussion yet for this question.