We have existing Hyper-V cluster with Windows 2008 R2 and have recently begun creating a new Hyper-V cluster with Windows Server 2012. We recently added a Dell PowerEdge R710 that previously co-existed in a cluster running 2008 R2 Hyper-V. We are now unable to live migrate to/from this new node with the error below. Using CPU-Z, we find that 'AES' is the only cpu instruction that differs between the systems; existing and new.
Without turning on CPU Compatibility for the VM, is there a way to work around this or possibly disable AES on the CPUs that are capable in the cluster. We are not using secure migrations.
The virtual machine 'Bartender10' is using processor-specific features not supported on physical computer 'HYPERVC4N5'. To allow for migration of this virtual machine to physical computers with different processors, modify the virtual machine settings to limit the processor features used by the virtual machine. (Virtual machine ID 80A6ED64-A8D5-4FF9-959F-61E7F57AB137)