On Fri, Oct 08, 2021 at 12:56:24 +0200, Michal Prívozník wrote:
On 10/8/21 12:44 PM, Jiri Denemark wrote:
> 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.
I was looking into this, but I believe that 'query-migrate' returns the
actual bandwidth and not the limit. Or do you mean other command?
Yes, query-migrate-parameters, which is internally mapped to
qemuMigrationParamsFetch.
Jirka