Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1453
  • Last Modified:

AMD Opteron 6172 and 6272 Hyper-V Cluster

We are trying to setup Clustered Shared Volumes on two Dell PowerEdge R715 servers.  Dell told us that these two processors are compatible and would work together in a cluster.  However, when we try to migrate a VM over to the newest host, the AMD 6272, it shoots an error that the cpu’s are not compatible.  We have "Allow migration to a virtual machine host with a different processor version" checked.  Here’s how the error reads:

The virtual machine (servername) is not compatible with the virtualization host (servername).  The virtual machine may not start or operate correctly on the host.  This may be due to inconsistent processor compatibility information.

Has anyone seen this with AMD processors from a different revision?
AMD-6172.JPG
AMD-6272.JPG
0
Brandon Norris
Asked:
Brandon Norris
1 Solution
 
JelcinCommented:
Hi,

did you read the Microsoft document attached? Are your servers 2008R2?
Could you please try to change the migratioin direction from Newer to older server?
Also there is a difference between live migration and fail over clustering. Where live migration is more cpu dependent than the fail over feature. The fail over feature should work also between machines with different cpu vendors.
VM-processor-compatibility-mode.doc
0
 
Brandon NorrisNetwork/Server AdminAuthor Commented:
I decided to give the points to Jelcin instead of deleting this thread as he did put time into responding.  The problem lied within Hyper-V and the processors themselves. I applied two patches, one from MS and one from AMD and fixed my issue.
0
 
Robert_ClarkeCommented:
I know this is an old topic but i am experiencing a very similar issue.

xxhawkxx05 do you have the links or name of the 2 patches you applied to get your cluster working properly?

I have a 2 node cluster with AMD 6134 CPU, and have now added a 3rd node with AMD 6234.
I get the same error when trying to live migrate to the 3rd node.

Have tried everything else that Microsoft suggest, such as processor compatibility for the VM's.
Think these patches will help me out.
0

Featured Post

NEW Veeam Backup for Microsoft Office 365 1.5

With Office 365, it’s your data and your responsibility to protect it. NEW Veeam Backup for Microsoft Office 365 eliminates the risk of losing access to your Office 365 data.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now