Avatar of Sri M
Sri M
Flag for United Arab Emirates asked on

HyperV Host not responding

I am running a Hyper V cluster with two hyper v hosts and one of the host says Host not responding. We cannot see the GUI when we connected to a monitor, nor we can do a remote desktop connect to the server it simply hangs at creating session while doing RDP. Issue is there are few critical vm's running under it which we cannot take them down or risk loosing them due to some issue in future. Is there a way to get the host GUI back without disturbing the VM's? so I can safely migrate the vm's to another host and perform maintenance once I get access to GUI. As of now I feel its too risky to attempt host migration without knowing the root cause.

I have powershell access to that host and I tried restarting terminal services to attempt successful RDP connection however with no luck too.

Looking forward for experts help to get this resolved

Thanks
PowershellVirtualizationHyper-V* Clustering

Avatar of undefined
Last Comment
Sri M

8/22/2022 - Mon
Radhakrishnan

If you are able to connect services.msc remotely then check all the hyper-v related services are started?
Also check event logs for any errors?
Lee W, MVP

Why not just run the Hyper-V console off the other cluster node and migrate the VMs over?
Philip Elder

On a management system whose user runs as Standard User or on a DC:

Click Start --> type PowerShell --> either Right click and Run As Administrator or CTRL+SHFT+ENTER on it --> Domain Admin Credentials
Enter-PSSession -ComputerName HyperVServerName
Get-VM | FL
Get-ClusterResource | FL

Open in new window

That should give you an idea of what's happening.

You can also
Suspend-ClusterNode -Drain Immediate

Open in new window

to initiate a Live Migration of VMs off the node ... if it responds.
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Sri M

ASKER
Hello Philip Elder / Lee / Radhakrishnan,

Thank you all for very quick response

I can access the vm via another node console however I do not want to attempt failover as I am not sure if it will go without a problem. I want the Host access and if there is some way to restore host access by restarting certain services. Once I get access and make sure the host is fine I wanted to attempt failover and then bring the host down and perform maintenance on it.

I ran cluster validation and it worked fine and no false alarms but Host is not accessible at all via RDP, direct monitor connection  to the host physical server or by any means. In System Center under VMM it show Host unresponsive but all vm's running on that host works fine.

Looking forward for further inputs to restore Gui access to the host node

Thank you in advance

Regards
Brian Murphy

This might seem over simplified but did you check the AV/Firewall software management to assure the proper exclusions?

A customer of mine, recently, had a similiar scenario but in their case ESET was causing the server to "hard lock" every time the cluster service was started on any of the cluster nodes.

Adding the exclusions resolved the problem on all nodes.
(Example: https://support.eset.com/kb3078/?locale=en_US&viewlocale=en_US)
Sri M

ASKER
Hello Brian,

Thank you

Yes its not AV/Firewall on the host manchine. All I have is power shell access to the hyper v node, even migrations are failing when I tried evacuating the vm's to another cluster node

Regards
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Steve

try opening eventviewer on the working node and view the failed node's events. this should help work out whats actually wrong. Your symptoms suggest a problem with creating a new user session. Could be something as simple as disk space if you're lucky,

Selecting Computers
With appropriate administrative authority, you can select any computer in your network to view that computer's Event logs.

To select computers in Event Viewer:

Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.
In the top of the console tree, right-click Event Viewer (local), and then click Connect to another computer.
Either browse to the computer name or type the computer name in the dialog box to view the Event log on that computer.
Click OK.
(taken from https://support.microsoft.com/en-gb/help/302542/how-to-diagnose-system-problems-with-event-viewer-in-microsoft-windows)
ASKER CERTIFIED SOLUTION
Sri M

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.