From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KWDAK-0005nh-LX for qemu-devel@nongnu.org; Thu, 21 Aug 2008 12:37:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KWDAJ-0005nJ-QM for qemu-devel@nongnu.org; Thu, 21 Aug 2008 12:37:40 -0400 Received: from [199.232.76.173] (port=33882 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KWDAJ-0005nC-Kl for qemu-devel@nongnu.org; Thu, 21 Aug 2008 12:37:39 -0400 Received: from mx1.redhat.com ([66.187.233.31]:35141) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KWDAJ-0008WR-Du for qemu-devel@nongnu.org; Thu, 21 Aug 2008 12:37:39 -0400 Message-ID: <48AD99CF.6070004@redhat.com> Date: Thu, 21 Aug 2008 18:37:35 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] vnc port selection Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Xen Development Mailing List 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? cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/