mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-22 21:55:25 +00:00
qemu: Refresh memory size only on fresh starts
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
This commit is contained in:
parent
624ec1c2f9
commit
d7a0386e22
@ -5023,7 +5023,8 @@ int qemuProcessStart(virConnectPtr conn,
|
|||||||
/* Since CPUs were not started yet, the balloon could not return the memory
|
/* Since CPUs were not started yet, the balloon could not return the memory
|
||||||
* to the host and thus cur_balloon needs to be updated so that GetXMLdesc
|
* to the host and thus cur_balloon needs to be updated so that GetXMLdesc
|
||||||
* and friends return the correct size in case they can't grab the job */
|
* and friends return the correct size in case they can't grab the job */
|
||||||
if (qemuProcessRefreshBalloonState(driver, vm, asyncJob) < 0)
|
if (!migrateFrom && !snapshot &&
|
||||||
|
qemuProcessRefreshBalloonState(driver, vm, asyncJob) < 0)
|
||||||
goto cleanup;
|
goto cleanup;
|
||||||
|
|
||||||
VIR_DEBUG("Detecting actual memory size for video device");
|
VIR_DEBUG("Detecting actual memory size for video device");
|
||||||
|
Loading…
Reference in New Issue
Block a user