mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-23 14:15:28 +00:00
qemu: Fix issues with maxMemory in qemuDomainSetMemoryFlags()
qemuDomainSetMemoryFlags() would allow to set the initial memory greater than the <maxMemory> field. While the configuration would not work as memory hotplug requires NUMA to be enabled and the qemuDomainSetMemoryFlags() API does not work on NUMA guests this just fixes a corner case. The fix is still worth though as it allows to induce an invalid configuration and make the VM vanish on libvirt restart. Additionally this tweaks error message to be more accurate. Signed-off-by: Luyao Huang <lhuang@redhat.com> Signed-off-by: Peter Krempa <pkrempa@redhat.com>
This commit is contained in:
parent
d0baac09e6
commit
d174394105
@ -2313,11 +2313,19 @@ static int qemuDomainSetMemoryFlags(virDomainPtr dom, unsigned long newmem,
|
||||
* is no way to change the individual node sizes with this API */
|
||||
if (virDomainNumaGetNodeCount(persistentDef->numa) > 0) {
|
||||
virReportError(VIR_ERR_OPERATION_INVALID, "%s",
|
||||
_("maximum memory size of a domain with NUMA "
|
||||
_("initial memory size of a domain with NUMA "
|
||||
"nodes cannot be modified with this API"));
|
||||
goto endjob;
|
||||
}
|
||||
|
||||
if (persistentDef->mem.max_memory &&
|
||||
persistentDef->mem.max_memory < newmem) {
|
||||
virReportError(VIR_ERR_OPERATION_INVALID, "%s",
|
||||
_("cannot set initial memory size greater than "
|
||||
"the maximum memory size"));
|
||||
goto endjob;
|
||||
}
|
||||
|
||||
virDomainDefSetMemoryInitial(persistentDef, newmem);
|
||||
|
||||
if (persistentDef->mem.cur_balloon > newmem)
|
||||
|
Loading…
Reference in New Issue
Block a user