Couple of weeks ago we had a HW failure on one of the HP BL680c G5 blades where it just died, lights are on but no one home kind a thing. HP came in and with a new mobo, as they always do, replaced but still no joy, the savvey engineer then discovered that it is not one but two out of the four cpus are faulty. Ordered and replaced them and the host came back to life. Fine but for the life of me I could not get the 6 hosts cluster to recognise it as a VT enabled host although made sure the VT and the 'No-Execute Memory Protection' both are enabled in the BIOS. As a result this lone host would not vmotion to or from without the warning message about the CPU bit.

The only way to get the cluster EVC enabled again and be able to vmotion normally was to create a new cluster with EVC enabled and migrate all the hosts and VMs to it. When I did that the host that had a problem joined ok and was vmotioning as normal. I had manually recreate all the rules I had on the old cluster which was deleted and the new one renamed.

Now had anyone been in the same boat and what did they do if different.

Thank you