We recently added a brand new host to our VCenter Datacenter as part of an plan to expand our current VMware Environment. Since the addition, I have found that VMotion appears to be incompatible between the new host and the older hosts. The older hosts work just fine. I will illustrate our environment below:
3 Hosts Total
2 older HP Proliant DL360 G5 Servers using Intel Xeon E5420 processors
1 new HP Proliant DL360 G7 Server using Intel Xeon X5660 Processors
I was under the impression prior to this incident that as long as the processors in the host were 64-bit and either "all Intel" or "all amd" that there wouldn't be a problem. Apparently I was wrong and this may have been overlooked.
I came across this posting from another user with a similar problem:
To which a user posted a useful reply:
Upon investigating this link, I believe what I have according to the chart for my older Generation Servers would be located in Group C in the second chart and Group E for the new Generation Server (Correct me if I'm wrong).
If this is the case, they do not illustrate what needs to be done to get Group C Servers compatible with Group E, rather they illustrate how to get C to work with D, D to work with E.
1.) Can I follow the steps using the chart to mask said features of Group E (SSE4.2, and AES) to allow VMotion compatibility between hosts
2.) Where within VMware would I go to find these features to mask?
Any help or direction in reply to this post would be greatly appreciated. Let me know if more information is required to post an accurate solution.