Enhanced vMotion

[RanjnaAggarwal]

Generally it is said enhanced vmotion means vmotion and storage vmotion is done simultaneously but storage vmotion is available from standard and enhanced vmotion is even available in essentials plus how it is possible to do the enhanced vmotion even in the essentials plus?

Message was edited by: Brian Atkinson to remove the ALLCAPS from the subject line

[a_p_]

It looks like VMware just added the required feature to Essentials Plus (see. e.g. vMotion bug fixed in vCenter server 5.1.0a - frankdenneman.nl)

André

[RanjnaAggarwal]

i read this already from frankdenneman blog but my question is how without storage vmotion feature enhanced vmotion is possible?

[a_p_]

I don't currently have a test system with Essentials Plus licensing. However, from how I understand it, enhanced vMotion leverages storage vMotion, but requires to change Host and Datastore, whereas storage vMotion allows to change the datastore without the requirement to also change the host on which the VM is running.

André

[tomtom901]

Correct. That way you can use (enhanced) vMotion to move VM's between local datastores. The Storage vMotion feature itself is not available but it uses parts from that same technique. The reason it is introduced in the Essentials Plus acceleration kit is to allow SMB customers (for which the acceleration packs are aimed) to leverage vMotion feature without the absolute need for shared storage.

Hope this helps,

[admin]

in the enhance Vmotion you can use ESX local stroage too ..you don't have need of shared storage..

[Mnemonic]

As I understand you question. You are asking how Enhanced VMotion can be done, when Storage VMotion is not included in the license.

The answer is that VMware can do what ever they want in regards to licenses. The software you install is exactly the same, the only difference between most of the licenses is what you are allowed to do by the software, not by what the software is capable of, so if VMware decides that you are allowed to do a Enhanced VMotion on a Essentials Plus license they can do that, just like you would be able to do "ALL-THE-THINGS" if you dialed in a Trial license.

[King_Robert]

Enhanced vMotion Compatibility (EVC) simplifies vMotion compatibility issues across CPU generations. EVC automatically configures server CPUs with Intel FlexMigration or AMD-V Extended Migration technologies to be compatible with older servers.

After EVC is enabled for a cluster in the VirtualCenter inventory, all hosts in that cluster are configured to present identical CPU features and ensure CPU compatibility for vMotion. The features presented by each host are determined by selecting a predefined EVC baseline. VirtualCenter does not permit the addition of hosts that cannot be automatically configured to be compatible with the EVC baseline.

EVC capabilities of your server are based on two factors:

1. The version of vCenter Server that manages the host.
2. The underlying CPU architecture of the host processor.

About the tables in this article:

• Tables 1.1 and 1.2 list the available EVC baselines and their description.
• Tables 2.1 and 2.2 describe EVC baselines supported by different vCenter Server versions.

In general, if a processor can support EVC level XN, it can also support levels XN-1 to X0. For example, a processor that supports the Intel® "Sandy Bridge" Generation EVC Baseline has an EVC level of L4. Therefore, it can also support EVC levels L3, L2, L1, and L0. However, it cannot support EVC level L5, which corresponds to the Intel® "Ivy Bridge" Generation. Intel EVC Baselines are listed in Table 1.1.

For AMD processors, there are two different sequences of EVC levels: Levels A0 to A3, which support the first 3 generations of AMD Opteron™ processors, and levels B0 and above, which support AMD Opteron™ Generation 3 and later processors. Note that the AMD Opteron™ Generation 3 (no 3DNow!™) EVC baseline is common to both sequences. For example, an AMD processor that supports the AMD Opteron™ Generation 4 EVC baseline can support the AMD Opteron™ Generation 3 (no 3DNow!™) baseline, but not the AMD Opteron™ Generation 3 baseline. An AMD processor that supports the AMD Opteron™ Generation 3 baseline can support the AMD Opteron™ Generation 3 (no 3DNow!™) baseline, but not the AMD Opteron™ Generation 4 baseline. AMD EVC baselines are listed in Table 1.2.

Table 1.1: Description of Intel EVC Baselines

EVC Level	EVC Baseline	Description
L0	Intel® "Merom" Gen. (Intel® Xeon® Core™ 2)	Applies baseline feature set of Intel® "Merom" Generation (Intel® Xeon® Core™ 2) processors to all hosts in the cluster.
L1	Intel® "Penryn" Gen. (formerly Intel® Xeon® 45nm Core™ 2)	Applies baseline feature set of Intel® "Penryn" Generation (Intel® Xeon® 45nm Core™ 2) processors to all hosts in the cluster. Compared to the Intel® "Merom" Generation EVC mode, this EVC mode exposes additional CPU features including SSE4.1.
L2	Intel® "Nehalem" Gen. (formerly Intel® Xeon® Core™ i7)	Applies baseline feature set of Intel® "Nehalem" Generation (Intel® Xeon® Core™ i7) processors to all hosts in the cluster. Compared to the Intel® "Penryn" Generation EVC mode, this EVC mode exposes additional CPU features including SSE4.2 and POPCOUNT.
L3	Intel® "Westmere" Gen. (formerly Intel® Xeon® 32nm Core™ i7)	Applies baseline feature set of Intel® "Westmere" Generation (Intel® Xeon® 32nm Core™ i7) processors to all hosts in the cluster. Compared to the Intel® "Nehalem" Generation mode, this EVC mode exposes additional CPU features including AES and PCLMULQDQ.Note: Intel® i3/i5 Xeon® Clarkdale Series processors that do not support AESNI and PCLMULQDQ cannot be admitted to EVC modes higher than the Intel® "Nehalem" Generation mode.
L4	Intel® "Sandy Bridge" Generation	Applies baseline feature set of Intel® "Sandy Bridge" Generation processors to all hosts in the cluster. Compared to the Intel® "Westmere" Generation mode, this EVC mode exposes additional CPU features including AVX and XSAVE.Note: Intel® "Sandy Bridge" processors that do not support AESNI and PCLMULQDQ cannot be admitted to EVC modes higher than the Intel® "Nehalem" Generation mode.
L5	Intel® "Ivy Bridge" Generation	Applies baseline feature set of Intel® "Ivy Bridge" Generation processors to all hosts in the cluster. Compared to the Intel® "Ivy Bridge" Generation EVC mode, this EVC mode exposes additional CPU features including RDRAND, ENFSTRG, FSGSBASE, SMEP, and F16C.Note: Some Intel® "Ivy Bridge" processors do not provide the full "Ivy Bridge" feature set. Such processors cannot be admitted to EVC modes higher than the Intel® "Nehalem" Generation mode.

Note: In vCenter Server 5.1 and 5.5, the Intel® "Ivy Bridge" Generation option is only displayed in the Web Client.

Table 1.2: Description of AMD EVC Baselines

EVC Level	EVC Baseline	Description
A0	AMD Opteron™ Generation 1	Applies baseline feature set of AMD Opteron™ Generation 1 (Rev. E) processors to all hosts in the cluster.
A1	AMD Opteron™ Generation 2	Applies baseline feature set of AMD Opteron™ Generation 2 (Rev. F) processors to all hosts in the cluster. Compared to the AMD Opteron™ Generation 1 EVC mode, this EVC mode exposes additional CPU features including CPMXCHG16B and RDTSCP.
A3	AMD Opteron™ Generation 3	Applies baseline feature set of AMD Opteron™ Generation 3 (Greyhound) processors to all hosts in the cluster. Compared to the AMD Opteron™ Generation 2 EVC mode, this EVC mode exposes additional CPU features including SSE4A, MisAlignSSE, POPCOUNT and ABM (LZCNT).Note: Due to 3DNow!™ support being removed from AMD processors after mid 2010, use AMD Opteron™ Generation 3 (no 3DNow!™) when possible to avoid compatibility issues with future processor generations.
A2, B0	AMD Opteron™ Generation 3 (no 3DNow!™)	Applies baseline feature set of AMD Opteron™ Generation 3 (Greyhound) processors, with 3DNow!™ support removed, to all hosts in the cluster. This mode allows you to prepare clusters containing AMD hosts to accept AMD processors without 3DNow!™ support.
B1	AMD Opteron™ Generation 4	Applies baseline feature set of AMD Opteron™ Generation 4 (Bulldozer) processors to all hosts in the cluster. Compared to the AMD Opteron™ Generation 3 (no 3DNow!™) EVC mode, this EVC mode exposes additional CPU features including SSSE3, SSE4.1, AES, AVX, XSAVE, XOP, and FMA4.
B2	AMD Opteron™ "Piledriver" Generation	Applies baseline feature set of AMD Opteron™ "Piledriver" Generation processors to all hosts in the cluster. Compared to the AMD Opteron™ Generation 4 EVC mode, this EVC mode exposes additional CPU features including FMA, TBM, BMI1, and F16C.

Note: In vCenter Server 5.1 and 5.5, the AMD Opteron™ "Piledriver" Generation option is only displayed in the Web Client.

It is often the case that an older release of vSphere supports a new processor but not the corresponding new EVC baseline that exposes the maximum guest-visible features of that processor. A newer vSphere release usually supports both the processor and the new EVC baseline. This is because the older release can only support those features of the new processor that are in common with older processors. Therefore, support of an EVC baseline is not identical to the support of the corresponding processor. Tables 2.1 and 2.2 indicate the earliest vSphere release that supports each EVC baseline.

As an example, consider the Intel® “Sandy Bridge” Generation EVC baseline and the Intel® Xeon e5-2400 (a processor based on the Intel® “Sandy Bridge” architecture). The processor is supported by both vSphere 4.1 Update 2 (and later) and vSphere 5.0 (and later). But because vSphere 4.1 update 2 lacks support for advanced “Sandy Bridge” features such as AVX, the Intel® “Sandy Bridge” Generation EVC baseline is only supported starting with the vSphere 5.0 release. However, vSphere 4.1 Update 2 does support lower level EVC baselines on the Intel® Xeon e5-2400, such as Intel® “Westmere” Generation and Intel® “Merom” Generation.

Not all members of a given processor generation can support the same maximum EVC baseline. Either because of BIOS configuration or branding decisions made by OEM or CPU vendors, some members of that generation may lack a feature required to participate at the maximum EVC baseline. For example, some Intel® Xeon i3/i5 Clarkdale processors (based on the Intel “Westmere” processor architecture) do not have AESNI capability, which is required for the Intel “Westmere” Generation EVC baseline. Therefore, these processors cannot support that EVC baseline and must use lower levels of EVC baselines. Another example is where AESNI has been disabled by BIOS in an Intel® Xeon 5600 processor (also based on the Intel “Westmere” processor architecture); as a result, this processor also cannot support the Intel® “Westmere” EVC baseline and must use lower levels of EVC baselines.

The VMware Compatibility Guide always correctly lists the maximum EVC baseline for a processor assuming that no BIOS disablement of features has been enforced. Since disabling of features by BIOS is OEM and customer specific, the guide cannot address these cases.

Table 2.1: AMD EVC Baselines supported in vCenter Server releases

	EVC Cluster Baseline
vCenter Server Release	AMD Opteron™ Gen. 1	AMD Opteron™ Gen. 2	AMD Opteron™ Gen. 3	AMD Opteron™ Gen. 3 (no 3DNow!™)	AMD Opteron™ Gen. 4	AMD Opteron "Piledriver" Gen.
VirtualCenter 2.5 U2 and later updates	Yes	No	No	No	No	No
vCenter Server 4.0	Yes	Yes	Yes	No	No	No
vCenter Server 4.0 U1 and later updates	Yes	Yes	Yes	No	No	No
vCenter Server 4.1	Yes	Yes	Yes	Yes	No	No
vCenter Server 5.0	Yes	Yes	Yes	Yes	Yes	No
vCenter Server 5.1	Yes	Yes	Yes	Yes	Yes	Yes

Table 2.2: Intel EVC Baselines supported in vCenter Server releases

	EVC Cluster Baseline
vCenter Server Release	Intel® "Merom" Generation	Intel® "Penryn" Generation	Intel® "Nehalem" Generation	Intel® "Westmere" Generation	Intel® "Sandy Bridge" Generation	Intel® "Ivy Bridge" Generation
VirtualCenter 2.5 U2 and later updates	Yes	No	No	No	No	No
vCenter Server 4.0	Yes	Yes	Yes	No	No	No
vCenter Server 4.0 U1 and later updates	Yes	Yes	Yes	Yes	No	No
vCenter Server 4.1	Yes	Yes	Yes	Yes	No	No
vCenter Server 5.0	Yes	Yes	Yes	Yes	Yes	No
vCenter Server 5.1	Yes	Yes	Yes	Yes	Yes	Yes

Notes:

• For more information on supported servers and processor models, see the VMware Compatibility Guide for your ESX version.
• Verify that the BIOS settings for host processors enable Hardware Virtualization (if available) and Execute Protection. Default BIOS settings might not always enable these features. Hardware Virtualization is Intel VT on Intel processors and AMD-V on (supported) AMD processors. Execute Protection is Intel eXecute Disable (XD) on Intel processors and AMD No eXecute (NX) on AMD processors. For machines with AMD processors, under Processor Options, set No-Execute Page-Protection to Enabled. Until these CPU features are enabled, ESX hosts with EVC supported CPU types listed below will be unsupported.
  
  Note: XD is also listed as Execute Memory Protection under the processor option within the server BIOS.
  
  
• In EVC clusters where the ESX host CPU model is Intel 3500 or 5500 series (Nehalem), ESX 3.5 Update 4 or later and VirtualCenter Server 2.5 Update 4 or later must be installed. For additional information, see vMotion fails with an RDTSCP error in EVC clusters where the ESX host CPU Model is Intel 3500 series.... In EVC clusters where the ESX Host CPU model is Intel 3400 series, ESX 3.5 Update 5 or later and VirtualCenter Server 2.5 Update 5 or later must be installed. In EVC clusters where the ESX Host CPU model is Intel 7500 series, ESX 4.0 Update 1 or later and VirtualCenter Server 4.0 Update 1 or later must be installed.
• For Intel® "Westmere" EVC Mode, some server OEMs might require you to enable the AES instructions in the BIOS.
• E7 Series Processors require ESXi/ESX 4.1 Update 1 later. For more information, see Only one way migrations appear to function in an EVC cluster (2001373).
• Hosts with Intel Penryn-E processors that are running virtual machines at the ESXi 5.0 compatibility level (hardware version 😎 or higher cannot be added to Penryn EVC clusters. The ESXi 5.0 virtual machine compatibility level and higher compatibility levels expose the XSAVE feature to virtual machines running on Penryn-E hosts. The XSAVE feature is masked out in the Penryn EVC mode, causing a virtual machine feature incompatibility with these virtual machines.

[RanjnaAggarwal]

fllips, shared storage is even not needed in storage vmotion

[RanjnaAggarwal]

King_robert, my question is not about the EVC it is about the Enhanced vMotion.

[steveb05]

It is unfortunate that "Enhanced vMotion" means both "CPU Comparability vMotion" and "Cross-host Storage vMotion" which are two completely separate features.

[bekatro]

Hi RanjnaAggarwal,

you are absolutely correct. On paper, vMotion can be done with VMware licensing Essentials Plus bundle, Standard and higher, while Storage vMotion can be done with Standard licensing and higher.

But using the Enhanced vMotion or Cross Host Storage vMotion (done care about the name, as long you don't mix it up with EVC Cluster mode), Storage vMotion can be done with Essentials Plus using a small trick. Logging in to the WebClient, pick your running VM, select Migrate and Change Host and Datastore. As long as you change the host as well, you can Storage vMotion between local and shared storage as you like, even with Essentials Plus licensing, since the operation is triggered internaly as vMotion operation. If do the Enhanced vMotion and select the host on which the VM is currently running, you will get a licensing error.

So, as a matter of fact you can you use the Storage vMotion feature with Essentials Plus licensing as long as you have a second host and do a move of both, host and storage at the same time.

Regards Tim