From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KWE0u-0001ER-Tc for qemu-devel@nongnu.org; Thu, 21 Aug 2008 13:32:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KWE0t-0001BT-4f for qemu-devel@nongnu.org; Thu, 21 Aug 2008 13:32:00 -0400 Received: from [199.232.76.173] (port=58301 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KWE0s-0001BK-R3 for qemu-devel@nongnu.org; Thu, 21 Aug 2008 13:31:58 -0400 Received: from hs-out-0708.google.com ([64.233.178.247]:40249) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KWE0s-0006aM-Dj for qemu-devel@nongnu.org; Thu, 21 Aug 2008 13:31:58 -0400 Received: by hs-out-0708.google.com with SMTP id k27so48100hsc.2 for ; Thu, 21 Aug 2008 10:31:50 -0700 (PDT) Message-ID: <48ADA659.2030201@codemonkey.ws> Date: Thu, 21 Aug 2008 12:31:05 -0500 From: Anthony Liguori 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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Xen Development Mailing List 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. Maybe something like a to=N option. So you would have: -vnc localhost:0,to=10 That would try from displays 0 to 10 and select the first one it could attach to. > Second, we need a > way to communicate the port picked which isn't xen-specific. Obvious > choice is a monitor info subcommand. > There's already an info vnc. It can be added to that. Regards, Anthony Liguori > Comments? Other suggestions? > > cheers, > Gerd > >