VMotion guests from 3.0.2 to 3.5 times out at 10%

[AndyTipton]

Upgrading all my 3.0.2 hosts to 3.5 and when I try to bulk migrate the VM's from the host about to be re-installed to a previously installed 3.5 host they all fail one by one saying Operation Timed Out and always at the 10% mark.

Anyone else seen this?

Andy

[merse]

This is normally a network configuration issue with the VMKernel ports used for VMotion - Check the addresses, VLAN tags and use VMKPING to verify connectivity.

Sometimes removing and recreating the VMotion ports is required to fix this.

merse

[VMKR9]

Does sound like a network issue, check yor vmkernel ports default gateways are the same on each host

[wgardiner]

I will 3rd whats been said twice... just incase you aren't convinced yet

10% vmotion stopping is nearly always networking...related, and i find usually DNS resolution is the cause.

[weinstein5]

I will add my voice to the chorus that it is typically a network issues - but do you get any errors - because it can also be a resource issue and en error message will point you in the right direction -

also can you vmotion one at a time?

[Dave_Mishchenko]

Your post has been moved to the ESX Server 3.x Configuration forum

Dave Mishchenko

VMware Communities User Moderator