CPU count is not good when CPU hotplug is enabled

[tuxtof]

Bug Report

Description

on machine deployed on cpu hot-plug compatible hardware (or virtual hardware) the number of cpu shown in the interface is not correct

example with vsphere: 128
example with AHV: 240

if we look dmidecode output in details there is the Status field who get more details

dmidecode -t processor | grep Status
	Status: Populated, Enabled
	Status: Populated, Enabled
	Status: Populated, Disabled By BIOS
	Status: Populated, Disabled By BIOS
	Status: Populated, Disabled By BIOS

we see the two cpu and the X empty hot-plug slot

second issue , if we hotadd cpu looks like dmidecode is not updated and the third cpu is always seen as disabled despite we can see in in /proc/cpuinfo

The reason we don't see hot-plugged CPUs in the dmidecode output is that dmidecode relies on SMBIOS (System Management BIOS) data, which is typically collected at boot time only

Environment

• Talos version:1.9.2
• Kubernetes version: not yet deployed
• Platform: tested on AHV and vSphere

[smira]

CPU hot-plug would be of quite limited usage with Kubernetes, I'm not quite sure how it would interact with scheduler in a meaningful way, or what would be an actual use-case for it, given that it's not a single VM, but a cluster of machines.

The labels in the screenshot are coming from Omni, and they are populated from SMBIOS data for CPU & memory.