Host CPU incompatible issue when migrating virtual machines between ESX hosts

 

I was trying to migrate a virtual machine from one ESX host to another and received following validation error, “Host CPU is incompatible with the virtual machine’s requirements at CPUID level 0x1 register ‘ecx’.”.

 

Host CPU Incompatibility

Host CPU Incompatibility

 

The solution to this issue is to enable Enhanced vMotion Capability (EVC) in your virtual cluster. Please follow following article on how to enable EVC.

 

Enabling EVC on a virtual cluster

Enabling Enhanced vMotion Capability (EVC) on a cluster when vCenter is running in a virtual machine

 

Below steps would enable Enhanced vMotion Capability (EVC) on a cluster when vCenter Server is installed on a virtual machine running in the cluster. Inorder to use EVC, you must have ESX 3.5 Update 2 or higher. Following steps will work only if the vCenter Server virtual machine is running on an ESX host that is presenting the same CPU features as the ESX host in the new EVC cluster.

 

In this scenario I have 2 ESX hosts and vCenter Server is running on one of the ESX host. Both ESX hosts are connected to a NAS and store all virtual machine data. vSphere client is used to connect to vCenter Server.  Continue reading

How to enable vMotion in VMWare ESXi Host

By default vMotion is not enabled on VMWare ESXi Host. Below shown steps will enable vMotion capability to your VMWare Virtual Host.

 

  1. Connect to your ESXi host using vSphere client.
  2. Go to Configuration page and select Networking.
  3. Click Properties for the virtual switch where a VMkernel port has been configured.
  4. Select Management Network from Ports.
  5. Select Edit and enable vMotion in General tab.
vmotion

Enable vMotion