From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=59318 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OOwJk-0001tS-Uy
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 13:22:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1OOwJU-0006Ep-4D
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 13:22:09 -0400
Received: from mail2.shareable.org ([80.68.89.115]:44075)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <jamie@shareable.org>) id 1OOwJT-0006Ef-Ui
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 13:22:08 -0400
Date: Wed, 16 Jun 2010 18:22:03 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: [CFR 6/10] cont command
Message-ID: <20100616172203.GA30917@shareable.org>
References: <1276619430-15871-1-git-send-email-aliguori@us.ibm.com>
	<1276619430-15871-7-git-send-email-aliguori@us.ibm.com>
	<m3631jnmv7.fsf@trasno.mitica> <4C18D5FF.1050703@codemonkey.ws>
	<m3iq5jx884.fsf@trasno.mitica> <4C19044B.6010602@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4C19044B.6010602@codemonkey.ws>
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.nongnu.org/archive/html/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, Luiz Capitulino <lcapitulino@redhat.com>, Markus Armbruster <armbru@redhat.com>, Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>, Juan Quintela <quintela@redhat.com>

Anthony Liguori wrote:
> On 06/16/2010 11:17 AM, Juan Quintela wrote:
> >Consider the example that I showed you:
> >
> >(host A)		(host B)
> >launch qemu             launch qemu -incoming
> >migrate host B
> >                         .....
> >                         do your things
> >                         exit/poweroff/...
> >
> >At this point you have a qemu launched on machine A, with nothing on
> >machine B.  running "cont" on machine A, have disastreus consecuences,
> >and there is no way to prevent it :(
> >   
> 
> If there was a reasonable belief that it wouldn't result in disaster, I 
> would fully support you.  However, I can't think of any rational reason 
> why someone would do this.  I can't think of a better analogy to 
> shooting yourself in the foot.

That looks like a useful way to fork a guest for testing, if host B is
launched with -snapshot, or a copy of the disk image, or a qcow2 child of it.

Does it work? :-)

-- Jamie