?
Solved

Recently added new host, VMotion incompatibility problem

Posted on 2010-09-21
6
Medium Priority
?
1,971 Views
Last Modified: 2013-12-09
Hi All,

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:

http://www.experts-exchange.com/Software/VMWare/Q_25058699.html?sfQueryTermInfo=1+10+30+cpu+host+incompat+machin+requir+virtual+vmotion

To which a user posted a useful reply:

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1991&sliceId=1&docTypeID=DT_KB_1_1&dialogID=61173743&stateId=0

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.  

My question:

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.
0
Comment
Question by:RyanMyers83
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
6 Comments
 
LVL 19

Expert Comment

by:vmwarun - Arun
ID: 33727428
EVC (Enhanced VMotion Compatibility) is the option that needs to be enabled at the Cluster level.

This would make sure that the CPUs in both the old and new hosts share the same CPU extensions and mask those extensions on the new host's CPU which the old hosts do not have.

The HA / DRS cluster has to be recreated with EVC enabled as EVC cannot be enabled on existing clusters.
0
 
LVL 19

Accepted Solution

by:
vmwarun - Arun earned 500 total points
ID: 33727450
These 2 KB articles should be helpful

http://tinyurl.com/24vwnoa - Enabling EVC on a cluster when vCenter is running in a virtual machine

http://tinyurl.com/26mffmc - EVC and CPU Compatibility FAQ
0
 

Author Comment

by:RyanMyers83
ID: 33727461
Thanks arunraju...I was just looking up how to do that..  I will keep you posted.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 42

Assisted Solution

by:paulsolov
paulsolov earned 500 total points
ID: 33727462
Shutdown your VMs, Go into the cluster and edit settings. Go into EVC and change to Core2 45nm compatibility.  That should take care of it
0
 
LVL 42

Expert Comment

by:paulsolov
ID: 33740625
Let us know if you run into any issues, I have performed this with your exact hardware and it should work for you as well.  Keep in mind to install HP version of ESXi, it will give you HP agents for reporting.
0
 

Author Comment

by:RyanMyers83
ID: 33743722
Wow - I had no idea HP even had a version of ESXi.  I will look into this.  Thanks for the tip!
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …
Suggested Courses

765 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question