2.5 VC to VSphere4 VC problems Vmotioning now

[spf62]

We had a 2.5 VC with 3.5 update 4 ESX hosts. Everything was working fine (5 ESX hosts all using HA, DRS and VMotion)

We upgraded to VCenter4 and now I cannot VMotion from one of my ESX hosts. I get this error

host cpu is incompatible with the virtual machine's requirements at cpuid level 0x80000001 register 'ecx'

The other 4 ESX hosts VMotion without issue.

Please advise, thanks in advance for your help

[Troy_Clavell]

see this KB article

http://kb.vmware.com/kb/1011294

[spf62]

This article seems to mask the issue. I can't see having to power down every VM and change their configuration.

It seems like it should be more of a ESX fix than an individual vm fix.

[Troy_Clavell]

yes, it's a band-aid, but it's a functional fix. The issue doesn't happen with all VM's that I've noticed, just some. Maybe VMware will fix it in the .1 release, but for now following the KB article should resolve your issue.

[spf62]

For me it is happening for every VM that I try to migrate to and from that particular server. We have to many VM's for this band-aid to be plausable.

We had this issue when going from 2.x to 2.5 (different ESX host) and I can't find the KB article anywhere.

thanks for your help

[RParker]

The other 4 ESX hosts VMotion without issue.

We don't have a problem with VMotion, however they ARE noticeably slower, and ALL I did was upgrade to vCenter 4.0. That's really odd...

[spf62]

We are at VCenter4, but 3.5 update 4 hosts

[AndreTheGiant]

All hosts have the same processors? Or are you using EVC?

Maybe do you have upgrade the BIOS of one host?

Andre

[KNardi]

All procs are AMD, all hosts fall under the recommended hardware list.

Yes we are using EVC.

All the BIOS updates have been done

[AndreTheGiant]

Yes we are using EVC.

Have you change the baseline of EVC cluster on VC4?

Andre