From f227ed1842180b0faeef0b4f9cde184cfd46cafc Mon Sep 17 00:00:00 2001 From: Matthew Garrett Date: Mon, 25 Nov 2013 14:42:43 -0500 Subject: [PATCH] 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 Reviewed-by: Paolo Bonzini Signed-off-by: Juan Quintela (cherry picked from commit 40596834c0d57a223124a956ccbe39dfeadc9f0e) Signed-off-by: Michael Roth --- migration.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/migration.c b/migration.c index 2b1ab20c54f..ff00bfbe365 100644 --- a/migration.c +++ b/migration.c @@ -583,7 +583,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(); -- 2.39.5