From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MOu0b-0002nU-4v
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:49:57 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MOu0W-0002jU-5O
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:49:56 -0400
Received: from [199.232.76.173] (port=36519 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MOu0V-0002iu-Sk
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:49:51 -0400
Received: from rv-out-0708.google.com ([209.85.198.249]:6905)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1MOu0V-0001Q4-Fs
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:49:51 -0400
Received: by rv-out-0708.google.com with SMTP id b17so37923rvf.22
	for <qemu-devel@nongnu.org>; Thu, 09 Jul 2009 06:49:50 -0700 (PDT)
Message-ID: <4A55F57B.3030306@codemonkey.ws>
Date: Thu, 09 Jul 2009 08:49:47 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 3/3] add live dumping capability
References: <1247140059-5034-1-git-send-email-pbonzini@redhat.com>
	<1247140059-5034-4-git-send-email-pbonzini@redhat.com>
In-Reply-To: <1247140059-5034-4-git-send-email-pbonzini@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org

Paolo Bonzini wrote:
> With the previous cleanups in place, it is easy to trigger
> restart when the state machine goes from the COMPLETING to the
> COMPLETED state.  Besides this, the patch is just simple
> scaffolding for the monitor command and to migrate to a file
> rather than a pipe (which is a bit simpler because we do not
> need non-blocking I/O).
>   

Then this isn't live migration.

This is functionally equivalent to migrate "exec:dd of=filename", no?

I don't think there's value in introduce a new monitor command that just 
does the above.

If you were truly dumping an actual core file and things remained 
"live", that would be compelling, but it would be a lot easier to just 
implement that as an external process.  If you just used a table that 
mapped section names and versions to length, you only really need to 
understand the format of ram and cpu save sections.

Regards,

Anthony Liguori