VMware Cloud Community
dalemarshall
Contributor
Contributor
Jump to solution

EVC baseline for Intel Xeon 32nm Core i7

Hi all,

I have a two node cluster, the processors in each node are Inter Xeon CPU x5660.

I believe that in order to get EVC compatibility working with these processors I need to apply update 1 or later. I've actually applied update 2 and I still don't get the option to apply the Intel Xeon 32nm Core i7 baseline.

Is there some part of the process I'm missing to make this option available?

Many Thanks,

Reply
0 Kudos
1 Solution

Accepted Solutions
AmadSeni
Contributor
Contributor
Jump to solution

Had to downgrade BIOS - appears that versions 2.1.9 and 2.1.15 are buggy..

the only one that has worked without any issues is: 2.1.3

get it from here: ftp://ftp.us.dell.com/bios/R710-020013C.exe

now vmotion, etc works perfectly.

View solution in original post

Reply
0 Kudos
12 Replies
AntonVZhbankov
Immortal
Immortal
Jump to solution

If all your hosts are with the same CPUs you don't even need EVC.


---

MCSA, MCTS Hyper-V, VCP 3/4, VMware vExpert

http://blog.vadmin.ru

EMCCAe, HPE ASE, MCITP: SA+VA, VCP 3/4/5, VMware vExpert XO (14 stars)
VMUG Russia Leader
http://t.me/beerpanda
Reply
0 Kudos
f10
Expert
Expert
Jump to solution

Hi,

Are options like Intel VT and No execute memory enabled in the server bios, also check http://kb.vmware.com/kb/1003212 for more info.

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

f10

VCP3,VCP4,HP UX CSA

Regards, Arun Pandey VCP 3,4,5 | VCAP-DCA | NCDA | HPUX-CSA | http://highoncloud.blogspot.in/ If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Reply
0 Kudos
dalemarshall
Contributor
Contributor
Jump to solution

Well thats what I thought, but if I try migrating the machine I get the "Host CPU is incompatible with the virtual machines requirements CPUID level 0x1 register 'ecx'" error.

The processors are both definitely the same, VT is also enabled on both servers. These are Dell servers and there doesn't appear to be a no memory execute option but there is an "Execute disabled" option which is set to enabled.

Reply
0 Kudos
AmadSeni
Contributor
Contributor
Jump to solution

did you manage to sort this out? i'm having exact same issue. just got 2 x Dell PowerEdge R710 with X5660 CPU on both and getting same error when trying to vmotion. all options on bios are correct though.

bios is latest version on all hosts, settings in bios also identical.

Reply
0 Kudos
dalemarshall
Contributor
Contributor
Jump to solution

We've applied update 2 and vMotion still doesn't work.

Update 2 has added Intel Xeon 32nm Core i7 baselines to EVC now, however just one of the hosts still says it's incompatible, depite the other host being the exact same spec being fine.

Still working on a resolution. I'll let you know if I find anything interesting.

Reply
0 Kudos
AmadSeni
Contributor
Contributor
Jump to solution

Problem solved; what model of server do you have?

Reply
0 Kudos
dalemarshall
Contributor
Contributor
Jump to solution

Exactly the same as yours - 2 x Dell PowerEdge R710 with X5660 CPU on both

How did you resolve it?

Reply
0 Kudos
AmadSeni
Contributor
Contributor
Jump to solution

Had to downgrade BIOS - appears that versions 2.1.9 and 2.1.15 are buggy..

the only one that has worked without any issues is: 2.1.3

get it from here: ftp://ftp.us.dell.com/bios/R710-020013C.exe

now vmotion, etc works perfectly.

Reply
0 Kudos
dalemarshall
Contributor
Contributor
Jump to solution

Spot on that, worked perfectly. Thanks!

Reply
0 Kudos
poyler
Contributor
Contributor
Jump to solution

BIOS downgrade worked great, wish I hadn't called tech support before trying this.

Reply
0 Kudos
wcwong
Contributor
Contributor
Jump to solution

Our Dell SE found that the issue was around the new AES-NI instruction in the Westmere CPUs. 2.1.9 and 2.1.15 wasn't always doing the right thing.

The latest BIOS (2.2.10) that was released yesterday is supposed to resolve this problem.

Reply
0 Kudos
AmadSeni
Contributor
Contributor
Jump to solution

Ok thx, will test this for a while before applying onto the servers we have already deployed..

Reply
0 Kudos