Hyper-V Failover Cluster VM migration

I have a Failover Cluster configured to host Hyper-V VMs currently running two VMs : test1 and test2.

The cluster is composed of two nodes : VS01 and VS02 both running Windows server 2012 R2 Datacenter on version 6.3.9600.

Test1 was originally created on VS01 and test2 was created on VS02 before importing them to the cluster with Microsoft's Failover Cluster Manager.

My problem is that if I quick or live migrate test1 to VS02 (the machine it was not created on), I get the following errors :

Cluster resource 'Virtual Machine test1' of type 'Virtual Machine' in clustered role 'test1' failed. The error code was '0xc0370029' ('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.').
and
The virtual machine 'test1' is using processor-specific features not supported on physical computer 'MEDIVS02'. 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 E8880BB1-0CAB-49FD-BF1A-A3FD1AECB30E)

But if I migrate test2 from VS02 to VS01, there is no problem whatsoever.

I checked Hyper-V on both machines, and they are both on version 6.3.9600.16384.
VS01 has a Intel Xeon E5-2650 and VS02 has a Intel Xeon x5660.
LVL 1
savoiejpAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Enable CPU compatibility mode in the VM's settings.

There are two different CPU architectures there.

It is advisable that all nodes in a cluster be identical.
0
Casey WeaverNetwork EngineerCommented:
As above, you need compatibility mode. Here's why: https://technet.microsoft.com/en-us/library/dn859550.aspx

You can see from Intel Ark that your processors extensions are very different. VS02 to VS01 works because VS01 has all those old extensions and more. But going from VS01 to VS02 the VM wonders where the extensions it was working with went.

Newer E5: http://ark.intel.com/products/75269/Intel-Xeon-Processor-E5-2650-v2-20M-Cache-2_60-GHz
Older X5: http://ark.intel.com/products/37109/Intel-Xeon-Processor-X5560-8M-Cache-2_80-GHz-6_40-GTs-Intel-QPI
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hyper-V

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.