| commit | c38c1c142e64901b09f5ac000695071ed8c0e3a5 | |
| author | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Fri, 8 Mar 2019 10:12:10 +0000 (8 10:12 +0000) | ||
| committer | Juan Quintela <quintela@redhat.com> | |
| Mon, 25 Mar 2019 17:46:03 +0000 (25 18:46 +0100) | ||
| tree | 77a705aed44fdeaf7cdf339e6fa4b4b45d00117d | treesnapshot (tar.gz zip) |
| parent | 5ed0deca41b201a66d858d7296fe6b780d757404 | commitdiff |
migration/postcopy: Update the bandwidth during postcopy
The recently added max-postcopy-bandwidth parameter is only read
at the transition from precopy->postcopy where as the older
max-bandwidth parameter updates the migration bandwidth when changed
even if the migration is already running.
Fix this discrepency so that:
a) You can change the bandwidth during postcopy by setting
max-postcopy-bandwidth
b) Changing max-bandwidth during postcopy has no effect
(it currently changes the postcopy bandwidth which isn't
expected).
Fixes: 7e555c6c
bz: https://bugzilla.redhat.com/show_bug.cgi?id=1686321
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
The recently added max-postcopy-bandwidth parameter is only read
at the transition from precopy->postcopy where as the older
max-bandwidth parameter updates the migration bandwidth when changed
even if the migration is already running.
Fix this discrepency so that:
a) You can change the bandwidth during postcopy by setting
max-postcopy-bandwidth
b) Changing max-bandwidth during postcopy has no effect
(it currently changes the postcopy bandwidth which isn't
expected).
Fixes: 7e555c6c
bz: https://bugzilla.redhat.com/show_bug.cgi?id=1686321
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
| migration/migration.c | diffblobblamehistory |