Unfortunately the answer is yes. As the articles in the previous post point out, the procs pretty much have to be the same. But, I do have a piece of a post that fixes this but TRY AT YOUR OWN RISK. This fix will completely eliminate CPU compatibility check. All I can say is that it works very well for me and I haven't had bad things happen. My servers' CPU are all Intel and very close but different enough because if you buy a server 6 months after your other ones, you're already too far apart for VMotion.
Here you go:
You can disable all CPU compatibility checks by editing the vpxd.cfg file on the host that is running the VC server. This file is located in the
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter
folder. If vpxd.cfg doesn't exist, create it. (If your system is configured to hide common extensions, make sure you don't accidentally create a vpxd.cfg.txt file instead of vpxd.cfg.) However I'm pretty sure that it should have been created already by the beta 2 VC installer, and have various stuff in it.
This is another XML-structured file. The outermost element is <config>. We're going to add something just inside that level. I.e. this doesn't go inside the <vpxd> element or any other inner elements.
<migrate>
<test>
<CpuCompatible>false</CpuCompatible>
</test>
</migrate>
After modifying vpxd.cfg, you need to restart the VC service for the changes to take effect.