EVC not working after 6.7U3 upgrade

[bentobox]

Good morning dear community,

We are currently facing a weird problem in our vsphere cluster. After upgrading to vsphere 6.7U3 vMotion is not possible for VMs of Virtual HW Version 8 and earlier. Even if I open the vMotion wizard and select the same host, as the particular VM is running on, I'm getting a CPU compatibility error:

The virtual machine requires hardware features that are unsupported or disabled on the target host: """""""""""""* General incompatibilities " If possible, use a cluster with Enhanced vMotion Compatibility (EVC) enabled; see KB article 1003212. CPUID details: incompatibility at level 0x1 register 'ecx'. Host bits: 0001:0110:1001:1000:0010:0010:0000:0011 Required: x111:x11x:10x1:1xx0:xx10:xx1x:x00x:xx11

EVC is enabled in the cluster. So all Hosts are running on Sandy Bridge. As soon as I upgrade the HW version, the issue is resolved. We are running several virtual appliances on HW version 8 and 7 which cannot be updated to a new HW version.

What do we need to do to resolve the problem?

Thanks for any help.

[berndweyand]

thats the way how cpu extensions are checked. with hw version 8 there is a strong checking, hw9 and greater the checks are more relaxed.

just powerdown your vm and restart them - then you should be able to vmotion

[bentobox]

@bewe:

I‘m aware of that change. But this case looks more like a bug to me currently. Shutting down the vm and booting again does not solve the problem. Also resetting the vm specific CPUID settings does not solve it...

any other idea?
thanks for any help.