Before we deep dive into the raw per-VM EVC stuff, let ’ s cover cursorily what EVC is. EVC stands for Enhanced vMotion Compatibility which is a vCenter Server cluster-centric feature allowing virtual machines to vMotion or migrate across ESXi hosts equipped with unalike processors in the same bunch. VMware EVC Mode works by masking unsupported central processing unit features frankincense presenting a homogeneous processor battlefront to all the virtual machines in a cluster. This means that a VM can vMotion to any ESXi host in a cluster regardless of the server ’ s micro-architecture examples of which include Intel ’ s Sandy Bridge and Haswell. One caveat to remember is that all the processor ( randomness ) must be from a single seller i.e. either Intel or AMD. You merely can not mix and match .
What is per-VM EVC?
As the diagnose indicates, per -VM EVC can be enabled on an individual virtual car. The great thing about per VM EVC is that it not entirely works on VMs inside the cluster but besides VMs outside of the bunch. Unlike cluster level EVC, this feature enables vMotion across clusters, standalone hosts, across vCenters & hybrid clouds such as VMware cloud on AWS ( from on-premise vCenter ). It ’ s a reasonably cool modern feature ! The EVC modality now becomes an attribute of the virtual machine. A office cycle does not affect the compatibility of the virtual machine with different processors either. Most importantly, when you configure EVC at the virtual machine horizontal surface, the per-VM EVC mode overrides cluster-based EVC. If you do not configure per-VM EVC, when you baron on the virtual machine, it inherits the EVC mode of its parent EVC cluster or host .
Typical per-VM EVC Troubleshooting Problems
If you ’ re having trouble enabling per-VM EVC, here are the most common issues you should check.
- The environment must have vSphere 6.7 in place
- VM hardware version must be hardware version 14
- The user must power off the VM before configuring per-VM EVC
- If the user is enabling per-VM EVC on an individual VM that is inside an EVC enabled cluster, EVC mode on the VM should be equal or lower than that of EVC mode configured on the cluster
- If the user wants to enable this feature from UI, only vSphere H5 client supports it and not the flex based client
- Per-VM EVC works with vSphere DRS
- If you clone a VM with per-VM EVC configured, it will retain per-VM EVC configuration on the destination VM
- If the underlying host does not support EVC mode configured on VM, VM cannot power on
If you ’ re still having trouble after checking you ’ re in accordance with all these conditions, send me a message below and I ’ ll avail you out .
Enabling Per-VM EVC
Before you attempt the steps below just be certain the VM is powered off, running hardware translation 14 and use the HTML 5 node .
- In the vSphere Client, navigate to the virtual machine
- Under the Configure tab, select VMware EVC
- Click edit and select whether to enable or disable EVC
- If you want to enable EVC, choose a baseline CPU feature set from the VMware EVC Mode drop-down menu and click OK
If you ’ re going to be using any kind of overcast solution like AWS and moving virtual machines from different environments, Per-VM EVC is an absolute must in regulate to make migrations from your on-premise location to the cloud seamless .
You will likely need to upgrade if you ’ ra not running vSphere 6.7. This is something that you ’ ll want to take into consideration when you decide this type of tool is something you ’ ll plan on using. For most of us, our upgrades are well afoot by immediately !
hope this post helped and felicitous migrations !
[ the_ad id= ” 4738″ ] [ thrive_leads id= ’ 18673′ ]
Was this helpful ?
It wasn ’ thymine accurate
It wasn ’ triiodothyronine clear
It wasn ’ thymine relevant
Provide feedback about this article
share this post