Hi,

I am working on a project that runs many concurrent qemu sessions with vnc.
Handling the vnc ports for the different sessions is an issue that also 
project like qemudo tries to solve.
The solution chosen there was to handle a pool of ports and manage them 
internally.
Such a solution ignores the fact that these ports may be occupied by 
other processes on the same OS, and it actually duplicates an OS task.
A solution that uses external port handling facility (like a native OS 
free ports selection), by using a pre-allocated port is suggested.

Currently there is the following vnc option:
-vnc display    [start a VNC server on display]

Adding the following option:
-vnc-socket sd  [force VNC server on an already opened Socket Descriptor]

overrides the new socket opening for the vnc on 5900+display port, and 
uses the given sd socket descriptor instead.

In this way, one can create a socket, bind it to any specific port (e.g. 
arbitrary free port given by the OS), and only then start the qemu with 
the socket descriptor. Doing this, all the ports accounting is done by 
the OS.

The patch is against cvs 2007-06-21, but I think nothing relevant has 
changed since.

Comments are welcome,
Shahar