From: Anthony Liguori <anthony@codemonkey.ws>
To: Nathan Baum <nathan@parenthephobia.org.uk>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Option to continue after migration
Date: Wed, 30 Sep 2009 08:46:05 -0500 [thread overview]
Message-ID: <4AC3611D.70506@codemonkey.ws> (raw)
In-Reply-To: <1253237786.7425.145.camel@athens.parenthephobia.org.uk>
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"
>
Just do a 'cont' as soon as migration completes. If you don't use -d,
you'll have a way to be notified when migration completes.
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-09-30 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 1:36 [Qemu-devel] [PATCH] Option to continue after migration Nathan Baum
2009-09-18 1:52 ` Jamie Lokier
2009-09-18 7:42 ` [Qemu-devel] [RFC][PATCH] " Nathan Baum
2009-09-18 8:17 ` [Qemu-devel] " Jan Kiszka
2009-09-30 13:46 ` Anthony Liguori [this message]
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=4AC3611D.70506@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=nathan@parenthephobia.org.uk \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).