
8 Oct
2021
8 Oct
'21
10:44 a.m.
On Fri, Oct 08, 2021 at 10:19:04 +0200, Kristina Hanicova wrote:
We did not set priv->migMaxBandwidth if '--bandwidth' was specified as an option in the 'migrate' virsh command. This caused in printing the wrong value if virsh command 'migrate-getspeed' was called during the migration. This patch first sets the value to the given bandwidth (if one was specified) and restores the previous value after the migration.
Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1806856
I was wondering whether we should just read the bandwidth back from QEMU instead when miration is running. But I guess this is good enough. Reviewed-by: Jiri Denemark <jdenemar@redhat.com>