Hi folks,
When i vmotion a couple of VMs (Win 2003 x64 running IIS) from one host in our solution the VM CPU utilisation goes upto 100% and there are a lot of ASP.NET crash reports in the event log. This seems to kick off a lot of DW20.exe processes that then continue to eat CPU. THe cpu utilisation then causes the numerous websites to go offline (after running a bit slow for a while). Sometimes the application pools within IIS show up as unspecified error and they need manually starting. I think this is as a result of all of the asp errors. Ive left the server for a few minutes after vmotion has completed but the CPU utilisation does not drop off. The only way to cure the problem is to reboot the VM.
We are running 3 exsi 3.5 hosts with enterprise licences. Vmotion is setup on a different vlan. I am able to vmotion the same server between hosts 1 and 3 and 1/3 to host 2. When i then vmotion from host 2 i get the above errors.
I have 3 hosts running esxi. The version numbers are below:
1 - 3i, 3.5.0, 153875
2 - 3i, 3.5.0, 132629
3 - 3i, 3.5.0, 153875
Yesterday i recently updated the vmtools across all of the VMs.
When i try and migrate a host from host2 i get the following error message:
from host02: no guest os heartbeats are being received. Either the guest os is not responding or vmtools not configured properly
Anyone come across anything similar. This is a bit of a show stopper for us as we have had to turn DRS off on our new hosting solution.
