[nova] NUMA scheduling
> I would say try without "hw:numa_nodes=1" in flavor properties.
We already tested this long ago.
I mentioned previously:
Without the hw:numa_nodes property, an individual VM is created with its vCPUs and Memory divided between the two NUMA nodes, which is not what we would prefer. We would prefer, instead, to have all vCPUs and Memory for the VM placed into a single NUMA node so all cores of the VM have access to this NUMA node's memory instead of having one core require cross-NUMA communications.