Vmotion on 3.5

[egodette]

I am having an issue with Vmotion since moving to 3.5.
When ever a VM is moved to a different host using Vmotion the processor power goes to 100%.

Anyone experience this? Got a fix?

 

[Arisap]

You are not the only one with seeing this behavior. I think it is more related to VC 2.5 than anything else since the VC controls vmotion. Regardless, it also meeses up resource share settings in Reaource pools if you use DRS. The CPU spike should only occur for a few seconds and should no really impact overall performance. If you ESX host is over-allocated, then you may very well notice the spike.

 

[egodette]

Here is the solution from Vmware

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=k

c&externalId=1003638&sliceId=2&docTypeID=DT_KB_1_1&dialogID=53253468&stateId=
0%200%2053251610