I see wrong mappings using cpumanager and the following configuration.

E.g. in VM config

cores: 10
sockets: 2
threads: 2
dedicatedCpuPlacement: true
features:

• name: invtsc
  policy: require
  isolateEmulatorThread: true
  model: host-passthrough
  numa:
  guestMappingPassthrough: {}

gives

[cloud-user@hana-test-108 ~]$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 40
On-line CPU(s) list: 0-39
Thread(s) per core: 2
Core(s) per socket: 10
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E7-8880 v4 @ 2.20GHz
Stepping: 1
CPU MHz: 2194.710
BogoMIPS: 4389.42
Virtualization: VT-x
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
L3 cache: 16384K
NUMA node0 CPU(s): 0-5
NUMA node1 CPU(s): 6-39

and

cores: 10
sockets: 4
threads: 2
dedicatedCpuPlacement: true
features:

• name: invtsc
  policy: require
  isolateEmulatorThread: true
  model: host-passthrough
  numa:
  guestMappingPassthrough: {}

gives

[cloud-user@hana-test4 ~]$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 80
On-line CPU(s) list: 0-79
Thread(s) per core: 2
Core(s) per socket: 10
Socket(s): 4
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E7-8880 v4 @ 2.20GHz
Stepping: 1
CPU MHz: 2194.710
BogoMIPS: 4389.42
Virtualization: VT-x
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
L3 cache: 16384K
NUMA node0 CPU(s): 0-35
NUMA node1 CPU(s): 36-79

I have enabled cpumanager as described here:
https://docs.openshift.com/container-platform/4.10/scalability_and_performance/using-cpu-manager.html

Note that NUMA node0 CPU(s) is wrong in both case, in the latter also the NUMA node(s) is wrong. This seems to be a bug. Please advice.