|| That seems to be the correct behavior. Could this flag on the host kernel be the one responsible of it?
Does not seems like it because even trying to pin core 20-127 shows 64 vcores inside the os.
Here is something interesting that I just found while checking the console during the boot of the VM:
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
TSC deadline timer available
smpboot: 108 Processors exceeds NR_CPUS limit of 64
smpboot: Allowing 64 CPUs, 0 hotplug CPUs
KVM setup pv sched yield
[mem 0x40000000-0xafffffff] available for PCI devices
Booting paravirtualized kernel on KVM
108 Processors exceeds NR_CPUS limit of 64
According to duckduckgo:
Maximum number of processors that an SMP kernel could support
But I am not setting it on the host. I will now try to find out where can I set that flag on the linux kernel but it seems like its being set on the guest’s kernel and not on the host.
What image did you use to create the VM?
lxc launch ubuntu sampleVM --vm
or another one?