qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Migration via unix sockets.
Date: Tue, 11 Aug 2009 12:35:43 +0300	[thread overview]
Message-ID: <4A813B6F.8040908@redhat.com> (raw)
In-Reply-To: <4A8136CF.5040304@redhat.com>

On 08/11/2009 12:15 PM, Chris Lalancette wrote:
> A possible implementation of that is attached.  I have to say, though, that it
> is way more clumsy to use than the unix implementation I posted earlier.  On the
> outgoing side, you have to use the "getfd" monitor command to pass the fd using
> SCM_RIGHTS, then you have to issue another monitor command to start the migration:
>
> (qemu) getfd migration # passes opened fd via SCM_RIGHTS
> (qemu) migrate -d fd:migration
>    

That doesn't seem so bad, especially if you're a program.

> On the incoming side, you have to pass the fd via the command-line.  That means
> that you have to first arrange for it not to be closed on exec, and it also
> means that qemu is now depending on the external program to correctly set up the
> incoming socket so that qemu can just do the accept() on it.
>
>    

I'd like to see a qemu monitor incoming migration command.

> None of these problems are insurmountable, but they do make it cumbersome to use
> in general, and very difficult to use from the command-line.
>    

These are intended for qemu control programs, not humans.

> The other option is that I've misunderstood your intent, and if that is the
> case, please correct me where I'm wrong :).
>    

No, I think you got it.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2009-08-11  9:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05 15:24 [Qemu-devel] [PATCH] Migration via unix sockets Chris Lalancette
2009-08-10 10:23 ` Chris Lalancette
2009-08-10 11:34   ` Avi Kivity
2009-08-11  9:15     ` Chris Lalancette
2009-08-11  9:35       ` Avi Kivity [this message]
2009-08-11  9:44       ` [Qemu-devel] " Paolo Bonzini
2009-08-11 10:06         ` Avi Kivity
2009-08-12 12:20           ` [Qemu-devel] [PATCH] add file descriptor migration Paolo Bonzini
2009-08-18 13:56             ` [Qemu-devel] [PATCH v2] " Paolo Bonzini
2009-08-18 13:59               ` [Qemu-devel] " Chris Lalancette
2009-08-11 10:20       ` [Qemu-devel] [PATCH] Migration via unix sockets Daniel P. Berrange

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=4A813B6F.8040908@redhat.com \
    --to=avi@redhat.com \
    --cc=clalance@redhat.com \
    --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).