MAAS reports 383 cores, but system has (and shows) 384

[Jeff Lane ]

I've a HPE DL385 Gen11 with a set of the largest Genoa CPUs. It is commissioned in MAAS 3.4 but the summary info in MAAS says the machine has 383 cores (see screen shot attached).

lscpu on the machine shows that there are 384 cores that the OS sees, numbered 0-383.

ubuntu@hoodin:~$ lscpu
Architecture: x86_64
  CPU op-mode(s): 32-bit, 64-bit
  Address sizes: 52 bits physical, 57 bits virtual
  Byte Order: Little Endian
CPU(s): 384
  On-line CPU(s) list: 0-383
Vendor ID: AuthenticAMD
  Model name: AMD EPYC 9654 96-Core Processor
    CPU family: 25
    Model: 17
    Thread(s) per core: 2
    Core(s) per socket: 96
    Socket(s): 2
    Stepping: 1
    Frequency boost: enabled
    CPU max MHz: 2400.0000
    CPU min MHz: 1500.0000
    BogoMIPS: 4792.92
    Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good amd_lbr_v2 nopl nonst
                         op_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm
                         sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 invpcid_single hw_pstate ssbd mba perfmon_v2 ibrs ibpb sti
                         bp ibrs_enhanced vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xg
                         etbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local avx512_bf16 clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushb
                         yasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif x2avic v_spec_ctrl vnmi avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vp
                         opcntdq la57 rdpid overflow_recov succor smca fsrm flush_l1d
Virtualization features:
  Virtualization: AMD-V
Caches (sum of all):
  L1d: 6 MiB (192 instances)
  L1i: 6 MiB (192 instances)
  L2: 192 MiB (192 instances)
  L3: 768 MiB (24 instances)
NUMA:
  NUMA node(s): 2
  NUMA node0 CPU(s): 0-95,192-287
  NUMA node1 CPU(s): 96-191,288-383
Vulnerabilities:
  Gather data sampling: Not affected
  Itlb multihit: Not affected
  L1tf: Not affected
  Mds: Not affected
  Meltdown: Not affected
  Mmio stale data: Not affected
  Retbleed: Not affected
  Spec rstack overflow: Mitigation; safe RET
  Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2: Mitigation; Enhanced / Automatic IBRS, IBPB conditional, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
  Srbds: Not affected
  Tsx async abort: Not affected
ubuntu@hoodin:~$

The issue seems to be in what MAAS is calling NUMA node 0, which is weird, because MAAS says the machine has 8 NUMA nodes... and numactl on the machine shows only 2 nodes. AND MAAS is displaying the cores spread out across all 8 nodes while numactl shows that Node0 has 0-95 and 192-287

(MAAS NUMA info is also int he attached screen shot).,

Here is numactl on the machine:
ubuntu@hoodin:~$ numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287
node 0 size: 128601 MB
node 0 free: 114406 MB
node 1 cpus: 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383
node 1 size: 128862 MB
node 1 free: 126779 MB
node distances:
node 0 1
  0: 10 32
  1: 32 10

[Björn Tillenius (bjornt)]

Could you attach the output of the 50-maas-01-commissioning commissioning script? That's where we get the CPU information from.