Unable to Manage VMs in Hyper-V

Recently I came across a situation where a set of VMs running on cluster shared storage were all in an un-manageable state. They were not listing as being present on the host and exhibited the error shown in symptoms:

Symptoms

Virtual Machines show in a running or paused state but have the following error when attempting to access console, settings, or take any other management actions:

Screen Shot 2015-12-26 at 12.45.36 PM

Additionally try listing the VMs in Powershell

Get-VM

If the VM does not show in the list it is definitely in this state.

Problem

Check to see if any other VMs exhibit this issue and if they are on cluster shared storage. If you are using it make an exclusion for the Cluster Volume or disable AV as this is usually the culprit.

Remediation

Install Sysinternals process explorer here: https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

Next we will locate the GUID of the VM in question

Screen Shot 2015-12-26 at 12.10.36 AM

Once you have located the GUID open process explorer as administrator and locate right click the VWP.exe processes and check the commandline entry under the “image” tab. This will display the GUID of the VMs. Select the VWP.exe that matches your trouble VM and kill the process.

DO NOT kill any other processes or you will potentially bring down other VMs

Screen Shot 2015-12-26 at 12.10.23 AM

Once you have done this you will need to restart the Hyper-V management stack by restarting the VMMS process. I have found some of these will not work properly with the restart-service cmdlet, so you will need to stop and then start the service. This does not effect the running VMs, it only effects your ability to manage them while this service is stopped.

Get-Service vmms
Stop-Service vmms
Start-Service vmms
Get-Service vmms

Now you should be up and running!

Leave a Reply

Your email address will not be published. Required fields are marked *

5 + seven =