you're reading...

Hyper-V virtual machine failed in failover cluster, showing pending status and cannot boot

We had a SAN failure this weekend on our 2008R2 Hyper-V Failover Cluster, this dropped all VM’s within the cluster and left us with a few VM’s unable to boot. In failover cluster manager, selecting the VM displayed the status as failed, and selecting the cluster node that hosted the VM shows its status as pending as the below screenshots show:

Cluster Manager Failed VM
VM failed status in cluster manager (viewable when the VM is selected)

Cluster Manager Node List - Pending Status
VM pending status in cluster manager (viewable when the cluster node is selected)

Cluster Manager VM Critical Events
Critical events for the VM in cluster manager

To resolve this, the Hyper-V node which was currently the owner of the failed VM’s had to be rebooted, this required live migrating several virtual servers before it could be done. Once rebooted, the VM’s were available to be booted on any node within the cluster. It appears that the node was preventing the VM from booting, perhaps it maintained a lock on the config/VHD files?


No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: