VM runs ultra-slow after VMOTION from ESX 3.0.2 host to 3.5 host

[PMoreton]

I just VMOTION'd a live W2K3 (running sharepoint etc) machine from ESX 3.0.2 to ESX 3.5, and once on the 3.5 host, performance dropped to almost nothing. It took several minutes to log on, Task manager show both vCPU's at 100%, and task manager itself is using 30% of one CPU. It's as though I booted W2K3 on an old 4.77Mhz IBM PC, it runs, but only just....

I rebooted, and it was the same, so VMOTION'd back to the ESX 3.0.2 server and all is OK again (phew!)

Other W2K3 VM's ar running fine on the ESX 3.5 host....

Any ideas?

Thanks, Peter Moreton

[admin]

Have you seen this KB article? Sound like the behaviour you are experiencing.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100363...

[PMoreton]

Hi Alex,

Thanks, this might describe our problem, since DRS is enabled in our cluster. We might upgrade VirtualCenter to 2.5 update 1 tonight, as the article indictaes that update 1 will fix the issue.

Thanks, Peter

[kjb007]

I have seen other users have the same problem with Update 1 as well. You may want to try the workaround, and verify it is still in place after the upgrade to Update 1, if it helps you.

-KjB