Windows 2012R2 Cluster – Migration/Move fails

After having a Windows 2012R2 Cluster up and running and after having some Virtual Machines up and running as well the next step usually is to test the failover, i.e. migration to a different node. The cluster is running on two physical Dell servers. As a secondary node a PowerEdge T610 with two Intel Xeon E5620 processors was used. Although almost 4 years old and with some extra RAM the server should be able to run most of the important VM in case node one fails. The first node is running on a new PowerEdge R720 with two Intel Xeon E5-2609 processors.

All VM’s were installed with affinity to node 1. Every attempt to move any VM to the second node failed. The logs pointed with error messages like “The virtual machine ‘SRV-ADC-03’ is using processor-specific features not supported on physical computer ‘SRV-HYP-02’. 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.”  or “Cannot restore this virtual machine to the saved state because of hypervisor incompatibility. Delete the saved state data and then try to start the virtual machine.”.

Microsoft explicit mentions this when using totally different processors like Intel and AMD. It appears to be applicable for different processor generations too. Of course the instruction set particular with regards to visualisation will improve/change with every generation. The solution is to enable the option below for the respective VM. Once this is done the migration/move works flawless.

Migrate option for different processors

Leave a Reply

Your email address will not be published. Required fields are marked *