From: Chris Lalancette <clalance@redhat.com>
To: anthony@codemonkey.ws
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH]: Allow monitor interaction when using migrate -exec
Date: Wed, 27 May 2009 09:10:17 +0200 [thread overview]
Message-ID: <4A1CE759.70109@redhat.com> (raw)
In-Reply-To: <4A1AAD5F.2070403@redhat.com>
Chris Lalancette wrote:
> All,
> I've recently been playing around with migration via exec. Unfortunately,
> when starting the incoming qemu process with "-incoming exec:cmd", it suffers
> the same problem that -incoming tcp used to suffer; namely, that you can't
> interact with the monitor until after the migration has happened. This causes
> problems for libvirt usage of -incoming exec, since libvirt expects to be able
> to access the monitor ahead of time. This fairly simple patch allows you to
> access the monitor both before and after the migration has completed using exec.
>
> (note: developed/tested with qemu-kvm, but applies perfectly fine to qemu)
>
> Signed-off-by: Chris Lalancette <clalance@redhat.com>
>
ping?
--
Chris Lalancette
prev parent reply other threads:[~2009-05-27 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 14:38 [Qemu-devel] [PATCH]: Allow monitor interaction when using migrate -exec Chris Lalancette
2009-05-27 7:10 ` 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=4A1CE759.70109@redhat.com \
--to=clalance@redhat.com \
--cc=anthony@codemonkey.ws \
--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).