Re: [PATCH 1/2] qemu_migration: set bandwidth in priv during migration

2021-10-08 Thread Jiri Denemark
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.

Re: [PATCH 1/2] qemu_migration: set bandwidth in priv during migration

2021-10-08 Thread Michal Prívozník
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

Re: [PATCH 1/2] qemu_migration: set bandwidth in priv during migration

2021-10-08 Thread Jiri Denemark
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 1/2] qemu_migration: set bandwidth in priv during migration

2021-10-08 Thread Kristina Hanicova
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)