From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: [Qemu-devel] vnc port selection
Date: Thu, 21 Aug 2008 18:37:35 +0200 [thread overview]
Message-ID: <48AD99CF.6070004@redhat.com> (raw)
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/
WARNING: multiple messages have this Message-ID (diff)
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
Subject: vnc port selection
Date: Thu, 21 Aug 2008 18:37:35 +0200 [thread overview]
Message-ID: <48AD99CF.6070004@redhat.com> (raw)
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/
next reply other threads:[~2008-08-21 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 16:37 Gerd Hoffmann [this message]
2008-08-21 16:37 ` vnc port selection Gerd Hoffmann
2008-08-21 17:31 ` [Qemu-devel] " Anthony Liguori
2008-08-21 14:34 ` acue
2008-08-21 14:34 ` acue
2008-08-21 18:30 ` [Qemu-devel] " Avi Kivity
2008-08-21 18:35 ` Anthony Liguori
2008-08-21 19:53 ` [Xen-devel] " Daniel P. Berrange
2008-08-21 19:53 ` Daniel P. Berrange
2008-08-24 8:54 ` Avi Kivity
2008-08-24 10:01 ` Jamie Lokier
2008-08-24 10:01 ` Jamie Lokier
2008-08-26 10:15 ` [Xen-devel] Re: [Qemu-devel] " Ian Jackson
2008-08-26 10:15 ` Ian Jackson
2008-08-21 19:52 ` [Xen-devel] " Daniel P. Berrange
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=48AD99CF.6070004@redhat.com \
--to=kraxel@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.