From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MoSe5-0005Th-Q3 for qemu-devel@nongnu.org; Thu, 17 Sep 2009 21:52:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MoSe0-0005TT-Sl for qemu-devel@nongnu.org; Thu, 17 Sep 2009 21:52:21 -0400 Received: from [199.232.76.173] (port=56151 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MoSe0-0005TQ-Me for qemu-devel@nongnu.org; Thu, 17 Sep 2009 21:52:16 -0400 Received: from mail2.shareable.org ([80.68.89.115]:44880) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MoSe0-0002qH-B3 for qemu-devel@nongnu.org; Thu, 17 Sep 2009 21:52:16 -0400 Date: Fri, 18 Sep 2009 02:52:13 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH] Option to continue after migration Message-ID: <20090918015213.GA22922@shareable.org> References: <1253237786.7425.145.camel@athens.parenthephobia.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1253237786.7425.145.camel@athens.parenthephobia.org.uk> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nathan Baum Cc: qemu-devel@nongnu.org Nathan Baum wrote: > Hello, > > This patch adds a -c "continue" option to the migrate command which > causes the originating VM to remain running after migration, assuming it > was running before. > > I've done this primarily so that I can do "migrate -d -c exec:cat>file" > to take a snapshot without needing to have a snapshot-capable drive > attached, or wait until migration is complete and continue the VM > manually. When you later resume from the snapshot, isn't the state of virtual disks corrupted by the activity after the snapshot was taken? When the guest resumes, even though the disks will be corrupted, it won't _know_ they are corrupted (unlike a reboot), so may proceed to make things worse. -- Jamie