From: Matthew Garrett <matthew.garr...@nebula.com> 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.garr...@nebula.com> Reviewed-by: Paolo Bonzini <pbonz...@redhat.com> Signed-off-by: Juan Quintela <quint...@redhat.com> --- migration.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migration.c b/migration.c index 4ee341b..e5f6b98 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(); -- 1.8.4.2