The heart of the patchset are the last two patches. Long story
short, if a domain is configured to be pinned onto a set of NUMA
nodes stricly, we use both CGroups and numa_set_membind(). While
we can change the former later on a user's wish, we can't change
the latter. Therefore, any subsequent memory enlargement (e.g.
via virsh setmem $dom) will result in memory still being
allocated from old NUMA nodes and OOM killer interference is
likely to occur.
Michal Privoznik (6):
virCgroupNewPartition: Fix comment
virCgroupNew: Enhance debug message
virCgroupController: Check the enum fits into 'int'
qemuDomainGetNumaParameters: Check for the correct CGroup controller
qemuProcessHook: Call virNuma*() iff needed
virLXCControllerSetupResourceLimits: Call virNuma*() iff needed
src/lxc/lxc_controller.c | 31 +++++++++++++++++++++++++------
src/qemu/qemu_driver.c | 2 +-
src/qemu/qemu_process.c | 32 ++++++++++++++++++++++++++++----
src/util/vircgroup.c | 6 +++---
src/util/vircgroup.h | 5 +++++
5 files changed, 62 insertions(+), 14 deletions(-)
--
2.0.5