From: Reinhard Max <max@suse.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch to improve handling of server sockets
Date: Wed, 5 May 2010 01:42:54 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1005050128400.785@nitsch.suse.de> (raw)
In-Reply-To: <4BE0960E.5000407@redhat.com>
On Tue, 4 May 2010 at 23:47, Gerd Hoffmann wrote:
> My tigervnc (tightvnc successor) has IPv6 support and handles this
> just fine.
Well, as I wrote, the code is not just used for vnc, but also for
server sockets that (if I got that right) could be connected from
telnet or netcat implementations that don't speak IPv6.
> When going for multiple listening sockets in qemu we have to figure
> how we'll handle this in a number of places as there is no single
> listening address any more.
Well, that's what my patch is about. Did you take a look at it?
> Reporting the vnc server address in QMP is one.
Not sure what QMP is (this was the first time I looked at QEMU's
internals), but I think my patch only leaves one place TODO where I
chose to report only the first address for now, but it shouldn't be
too hard to fix that as well.
BTW, in some places I circumvented the need for reporting multiple
addresses by simply reporting the name that was passed to QEMU
instead.
cu
Reinhard
next prev parent reply other threads:[~2010-05-04 23:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 13:49 [Qemu-devel] Patch to improve handling of server sockets Reinhard Max
2010-05-04 16:23 ` Anthony Liguori
2010-05-04 20:44 ` Reinhard Max
2010-05-04 21:47 ` Anthony Liguori
2010-05-04 21:47 ` Gerd Hoffmann
2010-05-04 21:50 ` Anthony Liguori
2010-05-04 23:28 ` Reinhard Max
2010-05-05 15:01 ` Daniel P. Berrange
2010-05-04 23:42 ` Reinhard Max [this message]
2010-05-05 8:53 ` Gerd Hoffmann
2010-05-05 10:42 ` Reinhard Max
2010-05-05 11:04 ` Gerd Hoffmann
2010-05-05 17:14 ` Daniel P. Berrange
2010-05-05 8:29 ` Daniel P. Berrange
2010-05-05 17:44 ` Reinhard Max
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=alpine.LNX.2.00.1005050128400.785@nitsch.suse.de \
--to=max@suse.de \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).