Cannot assign more than 2 cores per socket

Cannot assign more than 2 cores per socket

15127
Created On 09/26/18 13:39 PM - Last Modified 06/02/23 09:22 AM


Symptom


Symptoms

While trying to deploy a firewall with 4 cores, one has to use two sockets. It's not possible to assign all 4 cores to a single socket.

 

Diagnosis

This issue is specific to VMware ESXi build VMware-VMvisor-Installer-6.5.0a-4887370.x86_64.iso. It works just fine with other builds.

 

The VMware image is interpreting the following line in the OVF file as maximum 2 cores per socket, which is not compulsory. It may allow it to have 4 cores per socket, but refer to the settings.

        <vmw:CoresPerSocket ovf:required="false">2</vmw:CoresPerSocket>

 

Original.PNG

Resolution


As a workaround, so the ESX would not be rebuilt to a newer image, we modified the OVA file PA-VM-ESX-8.0.5.ova to accommodate this issue.

 

Old Entry:

        <vmw:CoresPerSocket ovf:required="false">2</vmw:CoresPerSocket>

 

New Entry :

        <vmw:CoresPerSocket ovf:required="false">16</vmw:CoresPerSocket>

 

Edited.PNG

 

If more than 2 sockets are used, then there could be performance issues because packets may have to travel across the sockets.

 

 
Other users also viewed:
Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000CllUCAS&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Choose Language