VMware Cloud Community
KrisHamilton
Contributor
Contributor
Jump to solution

Changing Processors in Server after ESX installation

Here is the situation:

We purchased a Dell Poweredge 2950 (III) and installed ESX 3.0.2 on it. Once installed we found that our processors were incompatible and unable to VMotion. We then purchased 2 new processors from Dell and installed them into the server. These processors are the same as the processors that are in our Dell Poweredge 1950 (II). Now we still are unable to VMotion some machines from one host to another. We have determined that if the Nx bit is set to Expose the Nx bit, it will fail, but if the setting is set to Keep current Advanced setting values for the Nx Flag, they will VMotion across. Do we need to reinstall ESX on the 2950 that we downgraded the processors on? It seems that since the processors are the same that the VMotion woudl work whether or not the Nx bit was hi or exposed. See below for the processor details:

Dell 2950 original processors --> Intel Xeon Quad Core E5440 (2 installed)

Dell 2950 "downgraded processors --> Intel Xeon Quad Core X5355 (2 installed)

Dell 1950 installed processors --> Intel Xeon Quad Core X5355 (2 installed)

Any suggestions are greatly appreciated.

Tags (1)
Reply
0 Kudos
1 Solution

Accepted Solutions
dwight
Enthusiast
Enthusiast
Jump to solution

Did you check the bios on the 2950 and make sure the noexec support in the bios is set the same on the 2950 as on the 1950?




RHCE, VCP

Blog: http://computing.dwighthubbard.info

RHCE, VCP Blog: http://computing.dwighthubbard.info

View solution in original post

Reply
0 Kudos
3 Replies
dwight
Enthusiast
Enthusiast
Jump to solution

Did you check the bios on the 2950 and make sure the noexec support in the bios is set the same on the 2950 as on the 1950?




RHCE, VCP

Blog: http://computing.dwighthubbard.info

RHCE, VCP Blog: http://computing.dwighthubbard.info
Reply
0 Kudos
KrisHamilton
Contributor
Contributor
Jump to solution

Thanks that was it. The 2950 had the Execute Disable setting set to disabled. Once we enabled it, all is well. Thanks again!

Reply
0 Kudos
Sean321
Contributor
Contributor
Jump to solution

Thank you both for bringing this up and the fix. I had the same issue since my upgrade to 3.5 on one specific 2950. Changed that bios setting "execute disable" and VMotion problem solved.

Sean

Reply
0 Kudos