<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Compatibility problem Intel Xeon Gold 6252 in Test Forum Discussions</title>
    <link>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840850#M10</link>
    <description>&lt;P&gt;Thank you very much. I tried both ways, but no one works on ESXi 7.0 U1.((((&lt;/P&gt;&lt;P&gt;This works with ESXi 7.0 U2, but we have same situation like ESXi 6.7 U2 U3 - 4 sokets 12 coers per soket&lt;/P&gt;</description>
    <pubDate>Fri, 09 Apr 2021 08:41:49 GMT</pubDate>
    <dc:creator>vmezen</dc:creator>
    <dc:date>2021-04-09T08:41:49Z</dc:date>
    <item>
      <title>Compatibility problem Intel Xeon Gold 6252</title>
      <link>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840621#M6</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;&lt;P&gt;Not so long time ago we got new server with 2 sokets Intel Xeon Gold 6252 (2.1Ghz, 48 cores, 96 threads) on S2600WF.&lt;/P&gt;&lt;P&gt;When we setup ESXi 6.7U2 U3, it&amp;nbsp;&lt;SPAN&gt;recognize our server like 4 sokets by 12 cores per soket, and it dosen`t matter is the hypertridding on or off.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;When we setup ESXi 7, it even doesn`t recognize processors on installing stage. We have Purple Screen of Death with error "HW feature incompatibility detected: cannot start" (attached below). It seem like ESXi doesn't support&amp;nbsp;Xeon Gold 6252, but compatibility guide says that it is supporting Xeon Gold 6200 family.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;And also we have no problems with Xeon Gold 6138 on same S2600WF, bought earlier.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;We have ESXi 6.7 license.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Firmware on S2600WF set on latest.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please help if you can!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Sorry if wrong place to ask. If it is not difficult tell me where to ask.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 09:28:35 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840621#M6</guid>
      <dc:creator>vmezen</dc:creator>
      <dc:date>2021-04-08T09:28:35Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility problem Intel Xeon Gold 6252</title>
      <link>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840657#M7</link>
      <description>&lt;P&gt;For the ESX 7.0 PSOD, it is looks similar (similar only not exactly the same) to this thread.&lt;BR /&gt;&lt;A href="https://communities.vmware.com/t5/ESXi-Discussions/Upgrade-ESXI-7-0-1-Fatal-CPU-mismatch/td-p/2813635" target="_blank"&gt;https://communities.vmware.com/t5/ESXi-Discussions/Upgrade-ESXI-7-0-1-Fatal-CPU-mismatch/td-p/2813635&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Try specifying the boot parameter as indicated in that thread&lt;BR /&gt;cpuUniformityHardCheckPanic=FALSE&lt;/P&gt;&lt;P&gt;I don't have an answer why ESXi 6.7 does not see the number of cores/threads correctly for the Xeon Gold 6252.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Apr 2021 10:56:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840657#M7</guid>
      <dc:creator>bluefirestorm</dc:creator>
      <dc:date>2021-04-08T10:56:26Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility problem Intel Xeon Gold 6252</title>
      <link>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840837#M8</link>
      <description>&lt;P&gt;You meen to modify boot.cfg like this:&lt;/P&gt;&lt;P&gt;bootstate=0&lt;BR /&gt;title=Loading ESXi installer&lt;BR /&gt;timeout=5&lt;BR /&gt;prefix=&lt;BR /&gt;kernel=/b.b00&lt;BR /&gt;kernelopt=cdromBoot runweasel&lt;BR /&gt;&lt;U&gt;&lt;STRONG&gt;cpuUniformityHardCheckPanic=FALSE&lt;/STRONG&gt;&lt;/U&gt;&lt;BR /&gt;modules=/jumpstrt.gz --- /useropts.gz --- /features.gz --- /k.b00 --- /uc_intel.b00 --- /uc_amd.b00 --- /uc_hygon.b00 --- /procfs.b00 --- /vmx.v00 --- /vim.v00 --- /tpm.v00 --- /sb.v00 --- /s.v00 --- /bnxtnet.v00 --- /bnxtroce.v00 --- /brcmfcoe.v00 --- /brcmnvme.v00 --- /elxiscsi.v00 --- /elxnet.v00 --- /i40en.v00 --- /i40iwn.v00 --- /iavmd.v00 --- /icen.v00 --- /igbn.v00 --- /iser.v00 --- /ixgben.v00 --- /lpfc.v00 --- /lpnic.v00 --- /lsi_mr3.v00 --- /lsi_msgp.v00 --- /lsi_msgp.v01 --- /lsi_msgp.v02 --- /mtip32xx.v00 --- /ne1000.v00 --- /nenic.v00 --- /nfnic.v00 --- /nhpsa.v00 --- /nmlx4_co.v00 --- /nmlx4_en.v00 --- /nmlx4_rd.v00 --- /nmlx5_co.v00 --- /nmlx5_rd.v00 --- /ntg3.v00 --- /nvme_pci.v00 --- /nvmerdma.v00 --- /nvmxnet3.v00 --- /nvmxnet3.v01 --- /pvscsi.v00 --- /qcnic.v00 --- /qedentv.v00 --- /qedrntv.v00 --- /qfle3.v00 --- /qfle3f.v00 --- /qfle3i.v00 --- /qflge.v00 --- /rste.v00 --- /sfvmk.v00 --- /smartpqi.v00 --- /vmkata.v00 --- /vmkfcoe.v00 --- /vmkusb.v00 --- /vmw_ahci.v00 --- /crx.v00 --- /elx_esx_.v00 --- /btldr.v00 --- /esx_dvfi.v00 --- /esx_ui.v00 --- /esxupdt.v00 --- /tpmesxup.v00 --- /weaselin.v00 --- /loadesx.v00 --- /lsuv2_hp.v00 --- /lsuv2_in.v00 --- /lsuv2_ls.v00 --- /lsuv2_nv.v00 --- /lsuv2_oe.v00 --- /lsuv2_oe.v01 --- /lsuv2_oe.v02 --- /lsuv2_sm.v00 --- /native_m.v00 --- /qlnative.v00 --- /vdfs.v00 --- /vmware_e.v00 --- /vsan.v00 --- /vsanheal.v00 --- /vsanmgmt.v00 --- /tools.t00 --- /xorg.v00 --- /gc.v00 --- /imgdb.tgz --- /imgpayld.tgz&lt;BR /&gt;build=7.0.1-0.25.17325551&lt;BR /&gt;updated=0&lt;/P&gt;</description>
      <pubDate>Fri, 09 Apr 2021 06:20:06 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840837#M8</guid>
      <dc:creator>vmezen</dc:creator>
      <dc:date>2021-04-09T06:20:06Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility problem Intel Xeon Gold 6252</title>
      <link>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840846#M9</link>
      <description>&lt;P&gt;I think you can try first by entering the option after pressing the "Shift-O" key.&lt;/P&gt;&lt;P&gt;If you want to make it permanent (assuming it works), then you edit the boot.cfg.&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.esxi.upgrade.doc/GUID-A33C4CAB-18EE-4C8C-A55D-8AD7E8042BFA.html?hWord=N4IghgNiBcIKIDsAuBTATgAgEIHsdIwHkAHJASxwQGcMkcMBlJMNAsBDASWuYgjHKUMOTAFViAczRgAJikYBjNGVIgAvkA" target="_blank"&gt;https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.esxi.upgrade.doc/GUID-A33C4CAB-18EE-4C8C-A55D-8AD7E8042BFA.html?hWord=N4IghgNiBcIKIDsAuBTATgAgEIHsdIwHkAHJASxwQGcMkcMBlJMNAsBDASWuYgjHKUMOTAFViAczRgAJikYBjNGVIgAvkA&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Apr 2021 06:42:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840846#M9</guid>
      <dc:creator>bluefirestorm</dc:creator>
      <dc:date>2021-04-09T06:42:48Z</dc:date>
    </item>
    <item>
      <title>Re: Compatibility problem Intel Xeon Gold 6252</title>
      <link>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840850#M10</link>
      <description>&lt;P&gt;Thank you very much. I tried both ways, but no one works on ESXi 7.0 U1.((((&lt;/P&gt;&lt;P&gt;This works with ESXi 7.0 U2, but we have same situation like ESXi 6.7 U2 U3 - 4 sokets 12 coers per soket&lt;/P&gt;</description>
      <pubDate>Fri, 09 Apr 2021 08:41:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Test-Forum-Discussions/Compatibility-problem-Intel-Xeon-Gold-6252/m-p/2840850#M10</guid>
      <dc:creator>vmezen</dc:creator>
      <dc:date>2021-04-09T08:41:49Z</dc:date>
    </item>
  </channel>
</rss>

