From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46614) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wstbg-0002kH-L9 for qemu-devel@nongnu.org; Fri, 06 Jun 2014 08:50:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WstbZ-00068C-TO for qemu-devel@nongnu.org; Fri, 06 Jun 2014 08:50:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:4736) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WstbZ-00067Q-MX for qemu-devel@nongnu.org; Fri, 06 Jun 2014 08:50:45 -0400 Date: Fri, 6 Jun 2014 18:20:36 +0530 From: Amit Shah Message-ID: <20140606125036.GB27148@grmbl.mre> References: <1395892646-30283-1-git-send-email-aik@ozlabs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1395892646-30283-1-git-send-email-aik@ozlabs.ru> Subject: Re: [Qemu-devel] [PATCH] migration: Increase default max_downtime from 30ms to 300ms List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexey Kardashevskiy Cc: Paolo Bonzini , qemu-devel@nongnu.org, "Dr . David Alan Gilbert" On (Thu) 27 Mar 2014 [14:57:26], Alexey Kardashevskiy wrote: > The existing timeout is 30ms which on 100MB/s (1Gbit) gives us > 3MB/s rate maximum. If we put some load on the guest, it is easy to > get page dirtying rate too big so live migration will never complete. > In the case of libvirt that means that the guest will be stopped > anyway after a timeout specified in the "virsh migrate" command and > this normally generates even bigger delay. > > This changes max_downtime to 300ms which seems to be more > reasonable value. > > Signed-off-by: Alexey Kardashevskiy Reviewed-by: Amit Shah Amit