From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MaT33-0007yp-Oa
	for qemu-devel@nongnu.org; Mon, 10 Aug 2009 07:28:17 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MaT2z-0007yd-Pi
	for qemu-devel@nongnu.org; Mon, 10 Aug 2009 07:28:17 -0400
Received: from [199.232.76.173] (port=60780 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MaT2z-0007ya-ID
	for qemu-devel@nongnu.org; Mon, 10 Aug 2009 07:28:13 -0400
Received: from mx2.redhat.com ([66.187.237.31]:57407)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1MaT2z-00040m-4Q
	for qemu-devel@nongnu.org; Mon, 10 Aug 2009 07:28:13 -0400
Message-ID: <4A8005B4.9030600@redhat.com>
Date: Mon, 10 Aug 2009 14:34:12 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] Migration via unix sockets.
References: <1249485869-23590-1-git-send-email-clalance@redhat.com>
	<4A7FF53F.2000106@redhat.com>
In-Reply-To: <4A7FF53F.2000106@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Chris Lalancette <clalance@redhat.com>
Cc: qemu-devel@nongnu.org

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