[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Daniel P. Berrange
Subject: Re: [Xen-devel] Re: [Qemu-devel] vnc port selection
Date: Thu, 21 Aug 2008 20:53:30 +0100
User-agent: Mutt/1.4.1i

On Thu, Aug 21, 2008 at 01:35:57PM -0500, Anthony Liguori wrote:
> 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?
> An argument for this sort of semantics is that if you just launch 
> vncserver with no argument, it'll sit on the first unused port.  So 
> people are sort of used to this behavior.
> >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.

And it as I mentioned it'll make adding IPv6 support harder. 

|: 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 :|

reply via email to

[Prev in Thread] Current Thread [Next in Thread]