diff options
| author | Matthew Garrett <matthew.garrett@nebula.com> | 2013-11-25 14:42:43 -0500 |
|---|---|---|
| committer | Juan Quintela <quintela@redhat.com> | 2014-01-13 12:39:48 +0100 |
| commit | 40596834c0d57a223124a956ccbe39dfeadc9f0e (patch) | |
| tree | bc2556f6ac09cfa0eb58b15ef32c52c8bb388d47 /migration.c | |
| parent | 51cf4c1a99a172679c2949a2d58a2a4ee307b557 (diff) | |
migration: Fix rate limit
The migration thread appears to want to allow writeout to occur at full
speed rather than being rate limited during completion of state saving,
but sets the limit to INT_MAX when xfer_limit is INT64_MAX. This causes
problems if there's more than 2GB of state left to save at this point. It
probably ought to just be INT64_MAX instead.
Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'migration.c')
| -rw-r--r-- | migration.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/migration.c b/migration.c index 4ee341b06e..e5f6b98023 100644 --- a/migration.c +++ b/migration.c @@ -596,7 +596,7 @@ static void *migration_thread(void *opaque) ret = vm_stop_force_state(RUN_STATE_FINISH_MIGRATE); if (ret >= 0) { - qemu_file_set_rate_limit(s->file, INT_MAX); + qemu_file_set_rate_limit(s->file, INT64_MAX); qemu_savevm_state_complete(s->file); } qemu_mutex_unlock_iothread(); |