VM Connect takes long time

Hello,

I have a new cluster using 2012 R2 and have the problem that if I want to connect to a VM from the Hyper-V Manager (or Failover Cluster) the connection takes about 10 seconds or sometime even longer (20 seconds).

Does someone have any idea why this could be happening? Currently the servers are running in an isolated environment without internet connection, there are 2 DCs (2012 R2) with DNS which have been newly deployed just for this environment.

Any idea how to make the connection to the VMs faster? Could the lack of internet cause this problem?

Regards

Paul

February 19th, 2015 8:51am

Hi Paul,

Does this server has the heavy workload or does it connected quicicker if you disable AV soft? Does you RDP to this node at normally speed? Did you see any warning or error event after your connect successfully? Please confirm your cluster node connect to your DC has the normal network delay.

More information:
Troubleshooting Hyper-V
https://technet.microsoft.com/en-us/library/cc742454.aspx?f=255&MSPPError=-2147217396
Best Regards,

Free Windows Admin Tool Kit Click here and download it now
February 20th, 2015 6:02am

Hello Alex,

thanks for the reply.

Currently there is no AV active as of now. The RDP speed is normal. I will check the eventlog for errors as soon as I get the time to.

What do you mean with "Please confirm your cluster node connect to your DC has the normal network delay."?

Regards

February 20th, 2015 6:09am

When does the issue occur?  By default, Windows Server is configured to treat interactive jobs, e.g. VMconnect, at a lower priority than service jobs, e.g. VMs.  So one of two things can be happening.

First is if you have not accessed the system for a while, it is likely that the code needed to run VMconnect is not in memory and takes disk accesses to bring it in.  That takes longer than if you had just run VMconnect on another VM earlier.  The code may not have been 'garbage collected' out of the system.  Another possibility in this space is that if your system is running close its limit in regards to memory.  That can cause paging to occur for the parent partition.

Secondly is that if there is a fair amount of service activity, the interactive activity will be 'behind' the service activity.  A combination of the two can make it appear slower yet.

Free Windows Admin Tool Kit Click here and download it now
February 20th, 2015 3:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics