Sounds like you have a CPU mismatch between the source and target or a VM hardware issue.
The article provides more detail in the issue, cause and resolution.
Is there any risk of Upgrading Virtual Hardware?
If I'm honest the virtual hardware isn't where I would start troubleshooting.
I would look at the hosts that make up your cluster and check that the processor types all match. If they do not then you will need to look at the steps required to enable EVC.
Further detail for EVC can be found here;
Host 1 : Xeon E5-2640 v2
Host 2 : Xeon E5-2640 v2
These two are code name 'Ivy-Bridge'
Host 3 : Xeon E5-2640 v3
This processor is code name 'Haswell'
From the screenshot it looks like the latest EVC mode you have available is 'Sandy Bridge', is this an ESXi 5 cluster?
The good news is that I think we've found the issue. The bad news is that because some of your VMs have been exposed to features above the available EVC mode you will not be able to fix it without VM downtime.
VMware vSphere 5.1 < EVC guide
From the EVC guide;
"If virtual machines are running on hosts that have feature sets greater than the EVC mode you intend to enable, ensure that the cluster has no powered-on virtual machines.
■ Power off all the virtual machines on the hosts with feature sets greater than the EVC mode
■ Migrate the cluster’s virtual machines to another host using vMotion.
Because these virtual machines are running with more features than the EVC mode you intend to set, power off the virtual machines to migrate them back into the cluster after enabling EVC"
Thanks for your explanation. So helpful
I will prepare the downtime for my vms