VMwarewolfVMotion stops working in vSphere
A couple of ahem… hiccups have popped up for some users of VMotion after upgrading to vSphere.
The Knowledge base team has been ultra-fast in responding to these, and two new KBs have appeared:
VMotion stops working after upgrading to vSphere 4.0 (1011294)
and
If you notice any issues with VMotion with vSphere, be sure to check those two articles out.
Related posts:Announcing the Release of vSphere 4
VMware VI and vSphere SDK: Managing the VMware Infrastructure and vSphere
32-bit ODBC DSN for vSphere
VMotion Is Disabled After ESX Server Upgrade
VMotion in 3.5 DRS enabled Cluster causes Guest CPU to rise Dramatically
VMotion, VMware, vSphere May 26th. 2009, 11:07am
May 26th, 2009 at 12:02 pm
Now that is a brilliant piece of Quality Assurance. vSphere 4 wasn’t rushed. Seriously. Trust me.
May 27th, 2009 at 7:58 am
Even though I am “pro VMware” admin I’d say that KB1011294 issue is not minor hiccup. Requirement to power off an VM after migration from ESX 3 to ESX 4 to get VMotion working is quite big problem for me and my clients.
June 5th, 2009 at 12:43 pm
[...] to VMware vSphere, and now having issues with VMotion? Thanks to VMwarewolf, this pair of VMware KB articles (here and here) might help resolve the [...]
September 25th, 2009 at 8:36 am
So – I have verified all these things and STILL vMotion isn’t working for me. These are fresh installs – not upgrades. The flag is always there – machine has to be powered off to perform this function….
Dell poweredge 2950’s that had 3.5 update 2 on them. vMotion worked before installing 4.0 on the servers….any ideas?
September 29th, 2009 at 4:58 am
I joust found a similar article here. This guy manually edited the .vmx file to resolve the issue:
http://www.jjclements.co.uk/index.php/2009/09/15/vmware-vmotion-cpu-problem-after-vsphere-upgrade