Another thing to try would be to create an empty cluster, enable EVC for Intel there, evacuate or power off all VMs on the host, and then try moving the host into the cluster... see what error message that generates.

This error message means the host has the wrong CPU family/model:  "The host's CPU hardware does not support Enhanced VMotion Compatibility, which is enabled for this cluster."

This error message means that the host has a CPU family/model that is generally acceptable for EVC, but not acceptable for the mode active on the cluster (shouldn't happen in update 2, since there is only one mode per vendor in that release): "The host's CPU hardware does not support the specific Enhanced VMotion Compatibility mode that is currently enabled for this cluster."

This error message means that the host's CPU family/model should be OK, but the specific CPU features advertised by the host are lacking: ""The host's CPU hardware should support the Enhanced VMotion Compatibility mode that is enabled for this cluster, but some of the necessary CPU features are missing.  Check the host's BIOS configuration to ensure that no necessary features are disabled (such as XD and VT for Intel, or NX for AMD)."

christiandouma, the CPUID utility should work with ILO as well. Can you please post details of what you observer during the crash (perhaps screenshots)?

Great!. If the CPUID utility crashes your server, it would be helpful if you can post a screeenshot of how exactly it crashes. Thanks.