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: Mon, 10 Aug 2009 14:34:12 +0300 [thread overview]
Message-ID: <4A8005B4.9030600@redhat.com> (raw)
In-Reply-To: <4A7FF53F.2000106@redhat.com>
On 08/10/2009 01:23 PM, Chris Lalancette wrote:
> Chris Lalancette wrote:
>
>> Implement migration via unix sockets. While you can fake this using
>> exec and netcat, this involves forking another process and is
>> generally not very nice. By doing this directly in qemu, we can avoid
>> the copy through the external nc command. This is useful for
>> implementations (such as libvirt) that want to do "secure" migration;
>> we pipe the data on the sending side into the unix socket, libvirt
>> picks it up, encrypts it, and transports it, and then on the remote
>> side libvirt decrypts it, dumps it to another unix socket, and
>> feeds it into qemu.
>>
>> The implementation is straightforward and looks very similar to
>> migration-exec.c and migration-tcp.c
>>
>
> ping?
>
It would be nice to support migration via arbitrary fd using the recent
SCM_RIGHTS support.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-10 11:28 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 [this message]
2009-08-11 9:15 ` Chris Lalancette
2009-08-11 9:35 ` Avi Kivity
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=4A8005B4.9030600@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 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.