On Mon, Feb 23, 2026 at 11:13:02AM +0000, Jonathan Cameron wrote: > Ankit, can you give an example complete with table dumps please. > > I'm a little unsure on where things are getting scrambled. > Everything should be keyed of PXM. Sounds like we have a bug > somewhere but ordering shouldn't be relevant.
I understood the issue is Linux assigns the uAPI visible NUMA node numbers based on the ordering. The proximity/etc internal to the kernel (I thought) was OK? Then the problem is that uAPI has developed meaning based on what the bare metal HW does and now there are SW stacks that are expecting these platforms to have certain NUMA IDs in the Linux uAPI. Sure you can argue this is bad/etc/etc but the point of QEMU is to allow creating VMs that closely match real HW and in this instance real HW produces an ACPI table with a certain ordering and the SW is sensitive to this ordering. Even if there is some Linux bug mis-parsing the ACPI, then that still should be addressed from a qemu perspective by providing the ACPI construction that doesn't trigger any bug so existing VM images will work under qemu. Thus qemu needs a way to reflect the ordering on the command line to properly emulate this system and accomodate the existing VM software... Jason
