Hyper-V Cluster resource (VM) is stucked in starting state

Question

After an unexpected shutdown of all nodes in our Hyper-V cluster, there is a VM which is stucked in starting state.

I have tried to stop it but I have this error :

"the group cannot accept the request because it is moving to another node"

I have also tried to remove from Windows Failover cluster manager but nothing happens.

Your help is really needed.

BR

Answer 1

Hi,

Thank you for your posting!

Based on your descriptions, I would like to first check your environment:

"An unexpected shutdown of all nodes in our Hyper-V cluster, there is a VM which is stuck in starting state."
Is the node in the sentence equal to VM, or does it mean that there are multiple VMs on one node?

If your issue is concerned with the latter, you may encounter unexpected failover in your cluster, and you can try these steps:

1. Try to turn off your VM from Hyper-V Manager if you could see your VM on Hyper-V Manager.

2) Try to kill the worker process corresponding to the VM in Task Manager. To find the VM's working process, you can go to the location where you store the VM configuration file for your VM and pick up the VM ID, the ID is at the end of the location:

%systemdrive%\programdata\Microsoft\Windows\Hyper-V\Virtual Machines**<VM_GUID>**

2) Restart the VMMS service on both the nodes (the primary server and the one that your VM is moving to) and check. Still not resolved then proceed further. You can run command Get-ClusterResource to check your VM status.

3) You can run command to try to stop, turn off or remove your VM:
-Get-ClusterResource "Virtual Machine" | Set-ClusterParameter OfflineAction value

-Use Remove-ClusterResource command forcibly to remove your VM. How to use:
https://learn.microsoft.com/en-us/powershell/module/failoverclusters/remove-clusterresource?view=windowsserver2019-ps

Thank you for your support!

Best regards
Joan

---

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hello jiayaozhu-MSFT,

There are multiple VM in one node. In the cluster I have 4 nodes.

1) In the Hyper-V manager I am not able to shutdown the VM. The option is no more available for the VM.

2) How can I identify the process name corresponding to that VM in the Task Manager ? I have the ID of the VM but I am not able to see a process link to the VM. Can you give me more details how to find this process ?

3) Here I don't know which node it is moving to. There is no Preferred Owners configured for this VM.
Please find below the status of the VM when I run Get-ClusterResource:
Name State
SCVMM VMName OnlinePending
SCVMM VMName Vonfiguration Online(Locked)

4) When I run this command: Get-ClusterResource "Virtual Machine" | Set-ClusterParameter OfflineAction 0

I have this error: "An error occurred while opening the resource <<VMName>>".

Also When I run this command: Remove-ClusterGroup -Name "VMName" -Force -RemoveResources

Nothing happens !!

BR,

CamaraTiti

Answer 3

Hi,

Thank you for your reply!

First try to kill the working process. Run the Task Manager and go to the Details tab. All virtual machines are running in their own instance of vmwp.exe. To determine which process is responsible for your VM, you need the GUID of the hung-up VM you obtained earlier. Locate the process vmwp.exe that has the GUID of your VM in the User name column. Kill this process (End Task).

Thank you for your support!

Best regards
Joan

--------------------------------------------------------------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 4

Hello jiayaozhu-MSFT,

When I ended the task of the process related to the VM, I can see that the VM has changed his state in the Failover Cluster Manager to "SAVED".

And After a period of time, I saw that the VM has moved to another node with the same state (Starting).

BR

Answer 5

Hi,

I am glad to hear that you have some progression. Now you can try to restart your VMMS service on the node that your VM moved to.

In addition, just check if all of your nodes have failed in your cluster. I will keep researching this issue for you.

Thank you for your patience!

Best regards
Joan

------------------------------------------------------------------------------------------------------------------------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.