From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1KWEvS-0005ha-KQ
	for qemu-devel@nongnu.org; Thu, 21 Aug 2008 14:30:26 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1KWEvQ-0005hH-6i
	for qemu-devel@nongnu.org; Thu, 21 Aug 2008 14:30:25 -0400
Received: from [199.232.76.173] (port=53686 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1KWEvQ-0005hE-3T
	for qemu-devel@nongnu.org; Thu, 21 Aug 2008 14:30:24 -0400
Received: from il.qumranet.com ([212.179.150.194]:28090)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@qumranet.com>) id 1KWEvP-00034N-NT
	for qemu-devel@nongnu.org; Thu, 21 Aug 2008 14:30:24 -0400
Message-ID: <48ADB43D.9050401@qumranet.com>
Date: Thu, 21 Aug 2008 21:30:21 +0300
From: Avi Kivity <avi@qumranet.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] vnc port selection
References: <48AD99CF.6070004@redhat.com>
In-Reply-To: <48AD99CF.6070004@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>

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?

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

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.