From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:52920) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RxN6W-0005hO-DL for qemu-devel@nongnu.org; Tue, 14 Feb 2012 13:27:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RxN6Q-0005Dd-RO for qemu-devel@nongnu.org; Tue, 14 Feb 2012 13:27:52 -0500 Received: from thoth.sbs.de ([192.35.17.2]:26333) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RxN6Q-0005DL-H9 for qemu-devel@nongnu.org; Tue, 14 Feb 2012 13:27:46 -0500 Message-ID: <4F3AA796.90900@siemens.com> Date: Tue, 14 Feb 2012 19:27:34 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <4F333AAA.1070601@cn.fujitsu.com> <4F333D77.8040104@cn.fujitsu.com> <4F3AA24E.5070201@siemens.com> In-Reply-To: <4F3AA24E.5070201@siemens.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC][PATCH 10/16 v6] run dump at the background List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wen Congyang Cc: Eric Blake , HATAYAMA Daisuke , Dave Anderson , qemu-devel , Luiz Capitulino On 2012-02-14 19:05, Jan Kiszka wrote: > On 2012-02-09 04:28, Wen Congyang wrote: >> The new monitor command dump may take long time to finish. So we need run it >> at the background. > > How does it work? Like live migration, i.e. you retransmit (overwrite) > already written but then dirtied pages? Hmm... no. > > What does background mean then? What is the use case? What if the user > decides to resume the vm? OK, that is addressed in patch 15! I would suggest merging it into this patch. It makes sense to handle that case gracefully right from the beginning. OK, now I have some other question: What is the point of rate-limiting the dump? The guest is not running, thus not competing for bandwidth. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux