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

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

Anthony Liguori writes ("[Xen-devel] Re: [Qemu-devel] vnc port selection"):
> Avi Kivity wrote:
> > 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.

Exactly.  So that's why we need both the ability to do this, and the
ability to find out what port was eventually used.

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

That has a race, because you commit to the port before having
prevented another application from grabbing it.  I think the `pick
unused port' option is more sensible.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.