[PATCH manager/storage 0/2] fix #6202: warn if sockets exceed target node

[Nicolas Frey <n.frey@proxmox.com>]

and guard against division by zero in the import.

The latter came up in enterprise support, which is only tangentially
related to the original issue (but got me into fixing this issue in
the first place).

Tested using an ESXi VM with the entry 'cpuid.coresPerSocket'
manually set to '0', which can normally only happen when it is set to
"Assigned at power on" [0], i.e. the number of cores per socket is
"optimally selected" by ESXi.

Feedback on what to use as the nodeSocket heuristic would be great,
the initial bug report suggests the # of sockets on the node, but if
e.g. NUMA is enabled, then the # of CPU cores is the actual max for VM
sockets. Or do we want to generally warn about the differences between
how PVE and ESXi model CPU topology, regardless of the node's sockets?

[0] https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/9-0/vsphere-resource-management/using-numa-systems-with-esxi/virtual-numa-controls.html

pve-manager:

Nicolas Frey (1):
  fix #6202: ui: guest import: warn if sockets exceed target node

 www/manager6/window/GuestImport.js | 33 ++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)


pve-storage:

Nicolas Frey (1):
  esxi: guard against zero 'cpuid.coresPerSocket'

 src/PVE/Storage/ESXiPlugin.pm | 8 ++++++++
 1 file changed, 8 insertions(+)


Summary over all repositories:
  2 files changed, 41 insertions(+), 0 deletions(-)

--
Generated by murpp 0.12.1