vSphere Client freezes when trying to control VM

[ScotladUK]

I have a Dell Precision T5500 running ESXi 5.0.  It has two Intel Xeon E5507 CPU's and 8 GB Ram. 

Whilst running just one VM which is setup to have 4 cores and 2GB of Ram I find that if I click off the vSphere Console Window of the VM and do something else on my local PC then try to click back onto the vSphere Console Window of the VM it is unresponsive for 30secs - 1min.  When I am actively using the vSphere Console Window everything is fine and there is no freezes.  I have even found a similar behaviour when I am using a Remote Desktop Connection to some of my VM's. 

I am not an expert in vSphere but I know enough to get it installed and configured.  As far as I am aware it is a straightforward install with no special configuration or setup.  This issue is not overly a problem but it is more of an annoyance and I would like to learn how to investigate and resolve it if at all possible.

Looking forward to hearing your thoughts and suggestions.

[zXi_Gamer]

Do check on the vmware.log of the VM directory when you are facing such issue to note any error messages or info

Also, try to increase the video memory size of the VM in the advanced settings. link

If issue still persists,

If you are having only one VM in your system, try to disable the balloon driver in the VM and see if the freezing is still happening. Also do revert the balloon driver once  you have confirmed that the issue still persists after that also.

Disabling balloon driver here

[ScotladUK]

Ok I have tried both suggestions and neither of them seem to have made any difference.  I am still seeing the same delay when trying to gain control of the vSphere client window.

[zXi_Gamer]

Do check and post the vmware.log of the VM when you are trying to open the remote console.

[ScotladUK]

So after running with the balloon disabled it did seem better and more responsive however there were still times when trying to grab the control that it paused for a 30-60 secs still.  I have uploaded 5 of the logs that cover the time period when I was using the VM, sorry I didnt get a chance to narrow it down some more but if it is too much to go through the logs I will narrow down the time period and provide a more precise log.  Just wondering what else you might be able to find in the logs so hope you dont mind.

[zXi_Gamer]

Just wondering what else you might be able to find in the logs so hope you dont mind.

Nope,.. please I dont mind at all. In fact, I find it interesting to fix the same.

From your logs, it looks like the tools have been very naughty.

1. Please do a quick tools upgrade. If already upgraded, reinstall the tools.

Also, I also see that you have provided a USB disk from a client side. Is this correct? The reason I am asking is that when you open a mks connection, there are some delays happening while accessing the usb disks simultaneously the mks being established.

Also, I am finding that you are facing this issue after you  have taken a snapshot of the VM.? Am I right on this one?