Red Hat Bugzilla – Bug 1303624
[Alcatel vRAN Project] Provide a mechanism to hotplug memory in non-numa guests
Last modified: 2016-02-01 09:04:05 EST
Description of problem:
It seems that libvirt only support hotplug of memory for guests that exhibit NUMA topology. The only way to hot plug/unplug memory is using the balloon driver which is not a safe mechanism for cloud environments as guests may not be cooperating or even malicious.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set MaxMemory element in XML.
2. Boot Instance
3. Boot fails with libvirt error.
For x86, qemu mandates the use of a NUMA node to maintain compatibility with windows guests. As the NUMA node is added by qemu, we have to enforce it so that the XML matches the expected config.
A workaround is to add 1 NUMA node to the domain XML, which will be equivalent to the normal configuration.
For non-x86 guests, use of NUMA is not mandated.