Currently we have 4 HP DL380 G5 servers with Intel E5405 processors and 1 Dell 2950 with E5410 processor in a cluster. We are wanting to add another server to this cluster and I was wanting to know if the newer HP DL380 G6 servers with the Nehalem processors, specifically the X5520, could be added to the cluster and still have full vmotion capabilities. From what I have read this can be done with the Enhanced Vmotion Compatibility but I was wondering if anyone has done this successfully.
![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
ESX 3.5 Server Cluster
- Thread starter mct
- Start date
sabregen
Fully [H]
- Joined
- Jun 6, 2005
- Messages
- 19,501
You will not retain full vmotion capabilities between the two different CPU architectures. VMotion looks at the CPU architecture between the current host and the target, and does a supported feature comparison. If the stepping is too far off, or if either side does not have a feature support match (or if you are going from Intel to AMD), then the VMotion validation will fail.
My recommendation woulr be to load ESX on the new server, add it into the datacenter, but use it to run VMs that are more compute intensive for now, until you can get a second one. Once you have second one, then you can create a separate cluster for the new architecture, and slowly phase out the older machines, or just use them as two different logical environments, if you prefer. Nahalem based systems for compute intensive servers and application loads, and Core 2 based Xeons for more memory intensive loads, or something like that.
This may give you a graceful way to maintain server and application availability while phasing out older hardware. As you get new hosts that are Nahalem based, you can afford to move more running VMs over to that cluster, and start shutting down the older hosts. This will keep you from having licensing issues (having to buy more, that is). Then you could load ESXi on the older hardware, and add them back into the vCenter managed view as standalone, free host machines, for Dev or something.
My recommendation woulr be to load ESX on the new server, add it into the datacenter, but use it to run VMs that are more compute intensive for now, until you can get a second one. Once you have second one, then you can create a separate cluster for the new architecture, and slowly phase out the older machines, or just use them as two different logical environments, if you prefer. Nahalem based systems for compute intensive servers and application loads, and Core 2 based Xeons for more memory intensive loads, or something like that.
This may give you a graceful way to maintain server and application availability while phasing out older hardware. As you get new hosts that are Nahalem based, you can afford to move more running VMs over to that cluster, and start shutting down the older hosts. This will keep you from having licensing issues (having to buy more, that is). Then you could load ESXi on the older hardware, and add them back into the vCenter managed view as standalone, free host machines, for Dev or something.
sabregen
Fully [H]
- Joined
- Jun 6, 2005
- Messages
- 19,501
I placed a call to VMware Tech Support today and I was told that EVC would work with the Harpertown processors that we currently have and the Nehalem processors. The guy seemed pretty confident that there wouldn't be any issues.
I know you work for VMware lopoetve so what is VMware's stance on this?
I know you work for VMware lopoetve so what is VMware's stance on this?
sabregen
Fully [H]
- Joined
- Jun 6, 2005
- Messages
- 19,501
obviously, you're asking for lopo's response, so my information may be completely moot. I will say though, that his recommendations on these forums, with regard to VMware stuff is pretty much gospel. If he says it won't work, I wouldn't bet against him.
I welcome all the information I can get. I am just wanting to verify this because the processors we are using are the Penryn (Harpertown) which are the previous Xeon family of processors from my understanding. I am not sure if I just badly worded my original post and he misunderstood what we are actually using. The processors that we are currently using support Intel VT FlexMigration which is suppose to work with EVC.
Man can this stuff be confusing.
If it works it works - I'm in storage, so my strong point isn't the CPU mappings
http://kb.vmware.com/selfservice/mi...KB_1_1&dialogID=45334025&stateId=0 0 44874618
From looking at the new mappings, it may very well work - you won't get some of the Nehalem features though.
News to me! Learn something every day If it works it works - I'm in storage, so my strong point isn't the CPU mappings
http://kb.vmware.com/selfservice/mi...KB_1_1&dialogID=45334025&stateId=0 0 44874618
From looking at the new mappings, it may very well work - you won't get some of the Nehalem features though.
Thanks for the input. That is the same link I was given. I believe we will give it a shot and see if it works.
It is always nice to learn something new, I just hate forgetting the stuff I already knew.