Re: [libvirt] [PATCH] libxl: Set current memory value after successful balloon

On Thu, Jan 10, 2019 at 03:39:38PM -0700, Jim Fehlig wrote:

The libxl driver does not set the new memory value in the active domain def after a successful balloon. This results in the old memory value in <currentMemory>. E.g.

virsh dumpxml test | grep currentMemory <currentMemory unit='KiB'>20971520</currentMemory> virsh setmem test 16777216 --live virsh dumpxml test | grep currentMemory <currentMemory unit='KiB'>20971520</currentMemory>

Set the new memory value in active domain def after a successful call to libxl_set_memory_target().

Signed-off-by: Jim Fehlig <jfehlig@suse.com> --- src/libxl/libxl_driver.c | 1 + 1 file changed, 1 insertion(+)

Reviewed-by: Ján Tomko <jtomko@redhat.com> Jano