From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MOtx2-0006kZ-4y
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:46:16 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MOtww-0006de-J0
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:46:15 -0400
Received: from [199.232.76.173] (port=49657 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MOtww-0006dP-Cf
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:46:10 -0400
Received: from mx2.redhat.com ([66.187.237.31]:35294)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <pbonzini@redhat.com>) id 1MOtwv-0000pE-Pj
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 09:46:10 -0400
Message-ID: <4A55F49F.1070601@redhat.com>
Date: Thu, 09 Jul 2009 15:46:07 +0200
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH 0/3] add "core dump"-like capability
References: <1247140059-5034-1-git-send-email-pbonzini@redhat.com>
	<4A55F3DD.3080802@codemonkey.ws>
In-Reply-To: <4A55F3DD.3080802@codemonkey.ws>
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: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org


> But really, live migration gives you all the state you need. Why not
> just introduce a third-party program that you could live migrate to via
> exec?

dd can be such a program, but how would you restart the VM at the end of 
migration?

Paolo