Avatar of Marco Juski
Marco Juski
 asked on

Failure HyperV Cluster

I have a HyperV Cluster environment.
One of the servers is not listing the virtual machines.
But VMs are up and running.
I can view the VMs of host01, but not of host02.
Also by the Cluster Manager function I can not manage the VMs.

The error below occurs:
The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.

And:
A component on the server did not respond in a timely fashion. This caused the cluster resource 'Virtual Machine SRVCWBMON01 (2)' (resource type 'Virtual Machine', DLL 'vmclusres.dll') to exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.
Chamado.png
Windows Server 2012Hyper-V

Avatar of undefined
Last Comment
Marco Juski

8/22/2022 - Mon
Mahesh

remove VMs from cluster, remove server from cluster and add it again and then add virtual machine resources again
Marco Juski

ASKER
This problem does not occur only in the Cluster function.
Using HyperV's local host manager, it does not view the VMs that are connected to it.
But the VMs are up and running, that is, I just can not manage them, but they are up and running.

Even right on the host I can not see the VMs.
Mahesh

try installing hyper-v manager tools on other server, windows 10 and check if you are able to connect
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
SOLUTION
kevinhsieh

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Marco Juski

ASKER
Yes, but it did not work.
To understand the scenario, today we have two servers in the cluster. Server 02 has this problem.

On server 01 using hyperv manager, it opens its VMs, but it tries to connect to the VMs of server 02.

On server 02 using hyperv manager, it does not open its local VMs, but of that problem server, I can connect to the VMs of server 01 correctly.

I think it's not the HyperV manager tool, but a different one.
Mahesh

may be you can try clear / refresh WMI repository on affected hyper-v host
Marco Juski

ASKER
I have not yet restarted, but the concern is to reboot and not recognize the VMs.
At that point I can not manage them, but the VMs are up and running.
If I reboot, they may just not come back, that's the concern.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Marco Juski

ASKER
How do I clean the WMI repository?
ASKER CERTIFIED SOLUTION
Log in to continue reading
Log In
Sign up - Free for 7 days
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Marco Juski

ASKER
WMI repositor is consistent

But, I found on Server 02, the Hyper-V Virtual Machine Management service in Stopping status.

He is locked in this position and does nothing.
This is why VMs are still in the air but do not appear in the HyperV Manager.
FailoverClusterManager.png
ServiceStopping.png
Server02-connectVMsServer01.png
Server02-not-connect-local-VMs.png
kevinhsieh

You can try to kill the process on the host.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Marco Juski

ASKER
I did this, I restarted the service, but the problem persists.
Marco Juski

ASKER
I'll schedule it for the server tonight.
kevinhsieh

I would manually shut down the VMs on the bad host before rebooting the host, so so they get shut down cleanly.
Get an unlimited membership to EE for less than $4 a week.
Unlimited question asking, solutions, articles and more.
Philip Elder

There's a problem with Hyper-V communicating with storage from what I can see.
Get-NetAdapter | Sort Name
Get-NetLbfoTeam | Format-List
Get-VMSwitch  | Format-List

Open in new window

Let's start there.

Then, what is the Hyper-V to storage layout please?
Get-ClusterResource
Get-Cluster

Open in new window

Marco Juski

ASKER
I researched google, and I found several people saying that when the HyperV service starts giving problems, they only resolved by restarting the host.

Yes kevinhsieh, I will manually turn off each VM.

Philip Elder, the VMs are in the air and run and I can communicate with the storages without problems.

I have 16 VMs running from that host and everything is functional, just no communication to manage the VMs.
Marco Juski

ASKER
After the server restarted, the WMI service went up disabled and corrupted.
I did the recommended procedures for you.
I put the service in automatic mode and rebooted server.
HyperV has returned to normal.
Thanks for the recommendations.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23