Yep that error is unexpected. I have to ask: are you sure that the cluster is set up for 45nm Core 2, and not just Core 2?
And this is a migration from outside the EVC cluster to a destination inside the cluster?
Assuming that the EVC mode is in fact 45nm Core 2, then the destination host should definitely be advertising SSE 4.1 support. If you don't mind I'd like to have a look at:
The contents of /etc/vmware/config on the destination host (particularly any line that begins with "cpuidMask").
/proc/vmware/cpuinfo from the destination host
The config of the VM (particularly any line that begins with "hostCPUID", "guestCPUID", or "userCPUID").
Also... the destination host is not in maintenance mode, correct?
Just noticed something that caught my eye. I decided to delete the new cluster and create a new one. After I create the cluster and go into the EVC section and click Enable EVC a baseline is already showing as set and it does not give me a drop down to change it. At this point I have not added any hosts so it shouldnt have anything to "detect"
The baseline it is setting it to is "Merom" which I know is not what we want. So guess as this point is the baseline is not set right but the fact that I cannot choose a baseline doesnt make sense. In this new cluster there are no hosts yet.
*And this is a migration from outside the EVC cluster to a destination inside the cluster? * Correct
What version of vCenter are you using?
2.5.0 build 147633
Just came across a doc that is puzzling. If you scroll down
to Table 3.1: EVC Baselines on Intel CPUs it it showing that on ESX 3.5 U2 and
up that the only EVC baseline supported is Intel® Xeon® Core™2.
I'm not sure about the accuracy of that part of the table, but I'm puzzled about a more fundamental issue now:
In VC 2.5, you don't have the option to choose from multiple EVC modes. You will always get Merom (Xeon Core 2) for Intel, or Rev. E (Opteron Generation 1) for AMD.
You won't be able to choose any other modes, like Xeon 45nm Core 2, unless you use VC 4.0.
I believe the KB article is incorrect. ESX 3.5u2 or later is required to use EVC, but it should be able to use any mode if it is being managed by VC 4.0 or later.
Thanks for the clarification. I didnt realize there were so many running VC 4 with 3.5 hosts which is what tripped me up.
We upgraded to VC 4.0 today and proceeded and it worked as expected.