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


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

To: Avi Kivity <avi@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Qemu-devel] vnc port selection
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Thu, 21 Aug 2008 20:52:40 +0100
Cc: Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, qemu-devel@xxxxxxxxxx
Delivery-date: Thu, 21 Aug 2008 12:53:06 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48ADB43D.9050401@xxxxxxxxxxxx>
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>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Thu, Aug 21, 2008 at 09:30:21PM +0300, Avi Kivity wrote:
> Gerd Hoffmann wrote:
> >  Hi folks,
> >
> >Xen's qemu-dm version has a '-vncunused' command line switch which asks
> >the internal vnc server to pick any unused tcp port to listen on.  The
> >actual port is communicated to the outside world via xenstore.
> >
> >I'm looking for a reasonable way to implement that functionality in
> >upstream qemu.  First, I think it shouldn't be a separate command line
> >switch but an option for the existion -vnc switch.  Second, we need a
> >way to communicate the port picked which isn't xen-specific.  Obvious
> >choice is a monitor info subcommand.
> >
> >Comments?  Other suggestions?
> >
> >  
> Presumably -vncunused is passed by the management application, which 
> knows about all domains.  Can't it figure out an unused port and pass it on?

Yes & no. Yes, we do this in libvirt, but it open a race condition
unless you pass the actual file descriptor to QEMU. In addition when
we add IPv6 support to QEMU, you will actally have multiple sockets
you need to listen on. It will make it far easier if we just do the
right thing in QEMU, based on a command line flag. 

|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>