From: Chris Lalancette <clalance@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH]: Implement tcp "nowait" option for migration
Date: Wed, 06 Aug 2008 11:26:08 +0200 [thread overview]
Message-ID: <48996E30.3010701@redhat.com> (raw)
In-Reply-To: <4892D241.5090000@redhat.com>
Chris Lalancette wrote:
> Sometimes you want to be able to start up the receiving side of a live migration
> and actually be able to run monitor commands before you do the migration.
> Libvirt, in particular, wants to do this for setting up the migration. This
> patch implements a "nowait" option to the receiving side so that you start up
> the receiving side similar to:
>
> qemu-kvm -M pc -S blah blah -incoming tcp://0:4444,nowait
>
> Then you are able to interact with the monitor before the live migration takes
> place.
Anthony,
Any comments on this patch? I'd like to try to get this in the KVM tree
once Avi gets back, so I would prefer to do any iterations/cleanups now.
Thanks,
Chris Lalancette
prev parent reply other threads:[~2008-08-06 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 9:07 [PATCH]: Implement tcp "nowait" option for migration Chris Lalancette
2008-08-06 9:26 ` Chris Lalancette [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=48996E30.3010701@redhat.com \
--to=clalance@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.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