Help I can’t vmotion with vsphere!

5 06 2009

Are you having trouble using vmotion after you upgraded to vSphere? There seems to be an issue where some improper cpu-id masks are applied as part of the hardware upgrade procedure. When you go to migrate a machine, you will get a cpu mismatch error. VMWare has addressed the problem with this KB article….

You basically shutdown the vm, go to edit settings, go to options, then down to CPU-ID and click advanced. Then click Reset All to Defaults. Click ok, then boot the vm back up. That should let you vmotion the vm around again. You will have to do this for all you vms that are having an issue.




Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: