From: Jamie Lokier <jamie@shareable.org>
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>
Subject: Re: [Qemu-devel] Re: [CFR 6/10] cont command
Date: Wed, 16 Jun 2010 18:22:03 +0100 [thread overview]
Message-ID: <20100616172203.GA30917@shareable.org> (raw)
In-Reply-To: <4C19044B.6010602@codemonkey.ws>
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
next prev parent reply other threads:[~2010-06-16 17:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 16:30 [Qemu-devel] [CFR 0/10] QMP specification review Anthony Liguori
2010-06-15 16:30 ` [Qemu-devel] [CFR 1/10] qmp: balloon command Anthony Liguori
2010-06-15 16:42 ` Anthony Liguori
2010-06-15 16:30 ` [Qemu-devel] [CFR 2/10] qmp: block_passwd command Anthony Liguori
2010-06-15 16:44 ` Anthony Liguori
2010-06-16 13:33 ` Kevin Wolf
2010-06-16 13:57 ` Daniel P. Berrange
2010-06-15 16:30 ` [Qemu-devel] [CFR 3/10] command Anthony Liguori
2010-06-15 16:30 ` [Qemu-devel] [CFR 4/10] command Anthony Liguori
2010-06-15 17:02 ` Anthony Liguori
2010-06-15 16:30 ` [Qemu-devel] [CFR 5/10] closefd command Anthony Liguori
2010-06-15 16:45 ` Anthony Liguori
2010-06-15 16:30 ` [Qemu-devel] [CFR 6/10] cont command Anthony Liguori
2010-06-15 16:46 ` Anthony Liguori
2010-06-16 13:11 ` [Qemu-devel] " Juan Quintela
2010-06-16 13:47 ` Anthony Liguori
2010-06-16 16:17 ` Juan Quintela
2010-06-16 17:05 ` Anthony Liguori
2010-06-16 17:22 ` Jamie Lokier [this message]
2010-06-16 22:25 ` Juan Quintela
2010-06-16 16:25 ` Daniel P. Berrange
2010-06-16 17:18 ` Anthony Liguori
2010-06-16 22:05 ` Juan Quintela
2010-06-16 22:26 ` Anthony Liguori
2010-06-16 23:00 ` Juan Quintela
2010-06-15 16:30 ` [Qemu-devel] [CFR 7/10] cpu command Anthony Liguori
2010-06-15 16:59 ` Anthony Liguori
2010-06-15 17:00 ` [Qemu-devel] " Jan Kiszka
2010-06-15 16:30 ` [Qemu-devel] [CFR 8/10] device_add command Anthony Liguori
2010-06-15 16:49 ` Anthony Liguori
2010-06-15 16:30 ` [Qemu-devel] [CFR 9/10] device_del command Anthony Liguori
2010-06-15 16:49 ` Anthony Liguori
2010-06-15 16:59 ` [Qemu-devel] " Jan Kiszka
2010-06-15 20:48 ` Miguel Di Ciurcio Filho
2010-06-15 21:14 ` Anthony Liguori
2010-06-15 16:30 ` [Qemu-devel] [CFR 10/10] eject command Anthony Liguori
2010-06-17 14:49 ` [Qemu-devel] Re: [CFR 0/10] QMP specification review Luiz Capitulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100616172203.GA30917@shareable.org \
--to=jamie@shareable.org \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.