23 Sep
2015
23 Sep
'15
12:56 p.m.
On Wed, Sep 23, 2015 at 02:23:09PM +0200, Peter Krempa wrote:
Qemu unfortunately doesn't update internal state right after migration and so the actual balloon size as returned by 'query-balloon' are invalid for a while after the CPUs are started after migration. If we'd refresh our internal state at this point we would report invalid current memory size until the next balloon event would arrive.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1242940 --- Version 2: - completely different from original posting due to unexpected qemu behavior
src/qemu/qemu_process.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
ACK Jan