Is it possible to enforce EVC/vMotion compatibility on a single VM in a (non-EVC) vSphere 6 cluster?
I have an old Nehalem based host which I would like to use as a backup host in case I need to restart my main Haswell based machine without shutting down my AD.
But on the other hand, I wouldn't want to move every VM in an EVC cluster because of the lack of CPU features.
– At the moment, the cluster only consists of those two hosts.
– Adding a 2nd DC could work but this would result in more "maintenance work" and I would also need to spend another Windows license for this.
So my main goal would be a way to ensure vMotion capability between Haswell and Nehalem for specific VMs.
As ewwhite pointed out, there is no solution except enabling EVC for the cluster. Therefore I have removed the initial "accepted answer", although it works for me, and accepted his answer.