One could argue that the NUMA functionality wasn't intentionally turned off (it was inherited from debian) and thus re-enabling it would be fixing a bug.
Just as some background...the kilo release of OpenStack (currently under way) introduced support for NUMA guests (per-NUMA node hugepage support, guests with multiple NUMA nodes, pinning guest NUMA node to host NUMA node, etc.). If Ubuntu (which is currently one of the more popular OpenStack host distros) doesn't support NUMA in qemu by default, it's going to complicate things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417937 Title: qemu appears to be built without CONFIG_NUMA defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1417937/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
