This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [Qemu-devel] vnc port selection

To: qemu-devel@xxxxxxxxxx
Subject: [Xen-devel] Re: [Qemu-devel] vnc port selection
From: Avi Kivity <avi@xxxxxxxxxxxx>
Date: Sun, 24 Aug 2008 11:54:46 +0300
Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 24 Aug 2008 01:55:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48ADB58D.9070409@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <48AD99CF.6070004@xxxxxxxxxx> <48ADB43D.9050401@xxxxxxxxxxxx> <48ADB58D.9070409@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20080723)
Anthony Liguori wrote:

Alternatively, have the management application pass an fd denoting the socket.

If you are allocating the ports in the management tool, then just tell QEMU what port to open up. I don't think you gain anything passing an fd.

It prevents races, allows listening on non-traditional sockets (vnc over unix-domain), and allows privilege separation.

error compiling committee.c: too many arguments to function

Xen-devel mailing list