Createing CPU mask for Intel 7140M/7340

[ISD_Plc]

Can anyone give me some advice on how to set the cpu mask on a HP DL580G5 with a 7340 Quad core processor to enable vmotion with 3 other DL580 G4's with dual core 7140M cpu's. I get an vmotion error presently referencing EAX. I know these 2 cpu's are not vmotion compatible but I hope I can mask them.....

[ISD_Plc]

No-one got any hints?

[christianZ]

Have you checked the knowledge base for that - masking, vmotion, cpu

[ISD_Plc]

i did yes but its really not very well written at all. I can work out which bit to mask out for the EAX register.

[christianZ]

Post the vmotion error here (screen shot)

Check this:

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1993&slice...

[ISD_Plc]

Here you go one screen shot.

[pkk · Accepted solution]

We have 1xDL580 G5 with E7220 and 3xDL580 G4 with X7140M. There we use the following CPU mask:

Level 1

eax: -

---

-

---

-

---

-

---

-

---

0--0 -

---

-

---

ecx: -

---

-

---

-

---

-0-- -

---

--0- -

---

-

---

This allows for full vMotion between the 4 hosts (ESX 3.5 u2).

Good luck!

[ISD_Plc]

ok great did you add those masks globaly on the VC or on the DL580G5 only?

[pkk]

We added them on our templates in VC and manually on the few vm's that were already running at that time. I've read a description somewhere on how to add them globally, but can't remember now.

[christianZ]

...see attached link above.

[ISD_Plc]

yes I'm readung that now but it really isn't very clear at all....

my vpxd.cfg file from the vc is ..

<config>

<vcp2v>

<dontStartConsolidation>true</dontStartConsolidation>

</vcp2v>

<!-- <ws1x> -->

<!-- Enables 1.x Web Services compatibility -->

<!-- <enabled>true</enabled> -->

<!-- Enables 1.x Built in Perf data Refresh -->

<!-- <perfRefreshEnabled>false</perfRefreshEnabled> -->

<!-- Location of ws1x persistent data. Default is same directory as vpxd.cfg -->

<!-- <dataFile> C:\ws1x.xml </dataFile> -->

<!-- Location of the ws1x event mapping file. Default is the same directory as vpxd.cfg -->

<!-- <eventMap> C:\ws1xEventMap.xml </eventMap> -->

<!-- </ws1x> -->

<vpxd>

<das>

<serializeadds>true</serializeadds>

<slotMemMinMB>256</slotMemMinMB>

<slotCpuMinMHz>256</slotCpuMinMHz>

</das>

<filterOverheadLimitIssues>true</filterOverheadLimitIssues>

</vpxd>

<vmacore>

<threadPool>

<TaskMax>30</TaskMax>

</threadPool>

<http>

<readTimeoutMs>45000</readTimeoutMs>

<writeTimeoutMs>45000</writeTimeoutMs>

<blacklistPeriodMs>3000</blacklistPeriodMs>

</http>

<ssl>

<handshakeTimeoutMs>30000</handshakeTimeoutMs>

</ssl>

</vmacore>

</config>

so reading that doc I need to add the following after <vpxd>

<cpuFeatureMask>

<default-vendor>

<level-1>

<eax>--:::::smileyshocked:0:--:--</eax>

<ecx>--:::-0:--:0-:--:--</ecx>

</level-1>

</default-vendor>

</cpuFeatureMask>

really not too sure if the above is correct, I am surprised it is this complex.

[christianZ]

From the above doc:

Below is an example of the tag order, shown in the context of the vpxd.cfg file. The <config> and <vpxd> opening and closing tags are already in the vpxd.cfg file. The <guestOSDescriptor> opening tag can be placed directly after the <vpxd> opening tag, embed the appropriate tags to >suit your needs, followed by the closing </guestOSDescriptor> tag. <config> <vpxd>

<guestOSDescriptor>

<esx-2-x-x>

<all-versions>

<all-guests>

<cpuFeatureMask>

http://Elements and mask definition go in here. Common Mask Patterns can be copy-and-pasted from the below example patterns.

</cpuFeatureMask>

</all-guests>

</all-versions>

</esx-2-x-x>

</guestOSDescriptor>

so you should add /guestOSDescriptor but not sure about your masks

Nachricht geändert durch christianZ

use </esx-3-x-x> or </esx-3-5-x>

[ISD_Plc]

ok so assuming the mask from pkk_decens work and my hosts are all ESX 3.5 U3 then would you say this looks ok?

<config>

<vcp2v>

<dontStartConsolidation>true</dontStartConsolidation>

</vcp2v>

<!-- <ws1x> -->

<!-- Enables 1.x Web Services compatibility -->

<!-- <enabled>true</enabled> -->

<!-- Enables 1.x Built in Perf data Refresh -->

<!-- <perfRefreshEnabled>false</perfRefreshEnabled> -->

<!-- Location of ws1x persistent data. Default is same directory as vpxd.cfg -->

<!-- <dataFile> C:\ws1x.xml </dataFile> -->

<!-- Location of the ws1x event mapping file. Default is the same directory as vpxd.cfg -->

<!-- <eventMap> C:\ws1xEventMap.xml </eventMap> -->

<!-- </ws1x> -->

<vpxd>

<guestOSDescriptor>

<esx-3-x-x>

<all-versions>

<all-guests>

<cpuFeatureMask>

<default-vendor>

<level-1>

<eax>--:::::smileyshocked:0:--:--</eax>

<ecx>--:::-0:--:0-:--:--</ecx>

</level-1>

</default-vendor>

</cpuFeatureMask>

<das>

<serializeadds>true</serializeadds>

<slotMemMinMB>256</slotMemMinMB>

<slotCpuMinMHz>256</slotCpuMinMHz>

</das>

<filterOverheadLimitIssues>true</filterOverheadLimitIssues>

</vpxd>

<vmacore>

<threadPool>

<TaskMax>30</TaskMax>

</threadPool>

<http>

<readTimeoutMs>45000</readTimeoutMs>

<writeTimeoutMs>45000</writeTimeoutMs>

<blacklistPeriodMs>3000</blacklistPeriodMs>

</http>

<ssl>

<handshakeTimeoutMs>30000</handshakeTimeoutMs>

</ssl>

</vmacore>

</config>

[christianZ]

Yor forgot to close

</all-guests>

</all-versions>

</esx-3-x-x>

[christianZ]

and

</guestOsDescriptor>

[ISD_Plc]

ah! well spotted.... so here we go I think this is complete and I hope I haven't missed anything else!!

<config>

<vcp2v>

<dontStartConsolidation>true</dontStartConsolidation>

</vcp2v>

<!-- <ws1x> -->

<!-- Enables 1.x Web Services compatibility -->

<!-- <enabled>true</enabled> -->

<!-- Enables 1.x Built in Perf data Refresh -->

<!-- <perfRefreshEnabled>false</perfRefreshEnabled> -->

<!-- Location of ws1x persistent data. Default is same directory as vpxd.cfg -->

<!-- <dataFile> C:\ws1x.xml </dataFile> -->

<!-- Location of the ws1x event mapping file. Default is the same directory as vpxd.cfg -->

<!-- <eventMap> C:\ws1xEventMap.xml </eventMap> -->

<!-- </ws1x> -->

<vpxd>

<guestOSDescriptor>

<esx-3-x-x>

<all-versions>

<all-guests>

<cpuFeatureMask>

<default-vendor>

<level-1>

<eax>--:::::smileyshocked:0:--:--</eax>

<ecx>--:::-0:--:0-:--:--</ecx>

</level-1>

</default-vendor>

</cpuFeatureMask>

</all-guests>

</all-versions>

</esx-3-x-x>

</guestOsDescriptor>

<das>

<serializeadds>true</serializeadds>

<slotMemMinMB>256</slotMemMinMB>

<slotCpuMinMHz>256</slotCpuMinMHz>

</das>

<filterOverheadLimitIssues>true</filterOverheadLimitIssues>

</vpxd>

<vmacore>

<threadPool>

<TaskMax>30</TaskMax>

</threadPool>

<http>

<readTimeoutMs>45000</readTimeoutMs>

<writeTimeoutMs>45000</writeTimeoutMs>

<blacklistPeriodMs>3000</blacklistPeriodMs>

</http>

<ssl>

<handshakeTimeoutMs>30000</handshakeTimeoutMs>

</ssl>

</vmacore>

</config>

[christianZ]

Looks OK now.

[ISD_Plc]

right well I spose I best test it then! ......

[pkk]

Good, let us know the result! Maybe I'll finally get the push I need to do this globally as well! :smileyblush:

[ISD_Plc]

well it doesn't work migration fails with the same error as before. screenshot attached. As the error is the same does that mean,

A) The mask hasn't loaded?

B) It's the wrong mask?

Message was edited by: ISD Plc