Quoting Chris Friesen (<email address hidden>):
> 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.
That would definitely be the case if it had been on in precise or trusty,
but that doesn't seem to be the case.
> 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.
If you only want this in utopic, I think I feel comfortable trying for
that. For trusty I'd be more hesitant, but we can still try - with
a lot of testing.
Quoting Chris Friesen (<email address hidden>):
> 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.
That would definitely be the case if it had been on in precise or trusty,
but that doesn't seem to be the case.
> 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.
If you only want this in utopic, I think I feel comfortable trying for
that. For trusty I'd be more hesitant, but we can still try - with
a lot of testing.