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>
This commit is contained in:
		
							parent
							
								
									51cf4c1a99
								
							
						
					
					
						commit
						40596834c0
					
				@ -596,7 +596,7 @@ static void *migration_thread(void *opaque)
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
                ret = vm_stop_force_state(RUN_STATE_FINISH_MIGRATE);
 | 
					                ret = vm_stop_force_state(RUN_STATE_FINISH_MIGRATE);
 | 
				
			||||||
                if (ret >= 0) {
 | 
					                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_savevm_state_complete(s->file);
 | 
				
			||||||
                }
 | 
					                }
 | 
				
			||||||
                qemu_mutex_unlock_iothread();
 | 
					                qemu_mutex_unlock_iothread();
 | 
				
			||||||
 | 
				
			|||||||
		Loading…
	
	
			
			x
			
			
		
	
		Reference in New Issue
	
	Block a user