qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: Re: [Qemu-devel] vnc port selection
Date: Thu, 21 Aug 2008 13:35:57 -0500	[thread overview]
Message-ID: <48ADB58D.9070409@codemonkey.ws> (raw)
In-Reply-To: <48ADB43D.9050401@qumranet.com>

Avi Kivity wrote:
> 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?

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.

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

Regards,

Anthony Liguori

  reply	other threads:[~2008-08-21 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 16:37 [Qemu-devel] vnc port selection Gerd Hoffmann
2008-08-21 17:31 ` Anthony Liguori
2008-08-21 14:34   ` acue
2008-08-21 18:30 ` Avi Kivity
2008-08-21 18:35   ` Anthony Liguori [this message]
2008-08-21 19:53     ` [Xen-devel] " Daniel P. Berrange
2008-08-24  8:54     ` Avi Kivity
2008-08-24 10:01       ` Jamie Lokier
2008-08-26 10:15     ` [Xen-devel] " Ian Jackson
2008-08-21 19:52   ` Daniel P. Berrange

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48ADB58D.9070409@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).