I recently ran into a situation with a customer where they needed to add another host to their cluster. Problem is, their original hosts had single core AMD Opteron processors (Opteron 285) and the host they wanted to purchase came with either a Dual-Core or Quad-Core Opteron. The customer was scared about the VMotion Compatibility between their older AMD hosts and the newer hosts they would be purchasing….so much that they wanted me to find them an old single-core system. I know EVC is nothing new, I’ve been enabling it when needed for almost 8 months now. You may run into a situation where your customer (or boss) is a little hesitant in enabling this advanced feature. But rest assured, VMware has KB 1003212 to answer all your questions.
Well, with a little bit of convincing and by showing the customer VMware KB Article 1003212 I was able to enable Enhanced VMotion Compatibility (EVC) on their vCenter cluster.
There are a few things you should know about EVC. First off, it is fully supported by VMware and the CPU Manufacturers. Just as long as your running ESX 3.5 U2+ (and vCenter 2.5 U2), you can enable EVC on your cluster. This means that all CPUs on your hosts within a given cluster must be in one of the charts listed in the KB Article. As you can see, support for the new Intel Nehalem processors has been added in ESX 3.5 U4.
Also remember, VMotion is currently not possible between Intel and AMD processors, so all nodes in your cluster must be from the same manufacturer. Exciting changes in technology are happening and hopefully we will see this limitation lifted (I thought I’d never be able to say that).
Finally, one last thing you must know about EVC — because it really does nothing more than what CPU masking has done in ESX 2+, all of the Virtual Machines in the cluster you wish to enable EVC on need to be powered off. I strongly suggest reading the KB article for more information.
Created on March 31, 2009 by Rick Scherer
This blog has 12,216 views and 2 responses.