From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 7/10] Switch the memory savevm handler to be "live" Date: Tue, 9 Sep 2008 23:25:19 +0100 Message-ID: <20080909222519.GA13022@shareable.org> References: <1220989802-13706-1-git-send-email-aliguori@us.ibm.com> <1220989802-13706-8-git-send-email-aliguori@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Chris Wright , Uri Lublin , Anthony Liguori , kvm@vger.kernel.org To: qemu-devel@nongnu.org Return-path: Received: from mail2.shareable.org ([80.68.89.115]:34003 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751298AbYIIWZe (ORCPT ); Tue, 9 Sep 2008 18:25:34 -0400 Content-Disposition: inline In-Reply-To: <1220989802-13706-8-git-send-email-aliguori@us.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: Anthony Liguori wrote: > This patch replaces the static memory savevm/loadvm handler with a > "live" one. This handler is used even if performing a non-live > migration. Excellent. One of the annoyances of savevm currently is it pauses the VM for a significant time, so you can't use it to snapshot production systems being used. > The key difference between this handler and the previous is that each page is > prefixed with the address of the page. The QEMUFile rate limiting code, in > combination with the live migration dirty tracking bits, is used to determine > which pages should be sent and how many should be sent. > > The live save code "converges" when the number of dirty pages > reaches a fixed amount. Currently, this is 10 pages. This is > something that should eventually be derived from whatever the > bandwidth limitation is. Does this mean that a snapshot could record the same page many times, perhaps even unbounded, while the guest is dirtying pages at a high rate? Or is the guest dirtying rate limited too to ensure the file writer will converge in bounded time? Thanks, -- Jamie