The coresPerSocket value set in install-config does not match the actual result. When setting controlPlane.platform.vsphere.cpus to 16 and controlPlane.platform.vsphere.coresPerSocket to 8.The actual result I checked was: "NumCPU": 16,"NumCoresPerSocket": 16, NumCoresPerSocket should match the setting in install-config instead of NumCPU.

Check the setting in VSphereMachine-openshift-cluster-api-guests-wwei1215a-42n48-master-0.yaml, the numcorespersocket is 0:
    numcpus: 16    
    numcorespersocket: 0

    4.16.0-0.nightly-2024-05-08-222442

    See description

    1.setting coresPerSocket for control plane in install-config. cpu needs to be a multiple of corespersocket.
    2.install the cluster
    

    The NumCoresPerSocket is equal to NumCPU. In file VSphereMachine-openshift-cluster-api-guests-xxxx-xxxx-master-0.yaml, the numcorespersocket is 0. and in vm setting: "NumCoresPerSocket": 8.

    The NumCoresPerSocket should match the setting in install-config.

installconfig setting:
controlPlane:
  architecture: amd64
  hyperthreading: Enabled
  name: master
  platform:
    vsphere:
      cpus: 16
      coresPerSocket: 8
check result:     
"Hardware": {          "NumCPU": 16,          "NumCoresPerSocket": 16,
the check result for compute node is expected.
installconfig setting:
compute:- architecture: amd64
  hyperthreading: Enabled
  name: worker
  platform:
    vsphere:
      cpus: 8
      coresPerSocket: 4
check result:
"Hardware": {          "NumCPU": 8,          "NumCoresPerSocket": 4,