From: "Daniel P. Berrange" <berrange@redhat.com>
To: Reinhard Max <max@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch to improve handling of server sockets
Date: Wed, 5 May 2010 09:29:45 +0100 [thread overview]
Message-ID: <20100505082945.GB8862@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1005041450180.13167@nitsch.suse.de>
On Tue, May 04, 2010 at 03:49:50PM +0200, Reinhard Max wrote:
> Hi,
>
> I am maintaining the tightvnc package for openSUSE and was recently
> confronted with an alleged vnc problem with QWMU that turned out to be
> a shortcoming in QEMU's code for handling TCP server sockets, which is
> used by the vnc and char modules.
>
> The problem occurs when the address to listen on is given as a name
> which resolves to multiple IP addresses the most prominent example
> being "localhost" resolving to 127.0.0.1 and ::1 .
>
> The existing code stopped walking the list of addresses returned by
> getaddrinfo() as soon as one socket was successfully opened and bound.
> The result was that a qemu instance started with "-vnc localhost:42"
> only listened on ::1, wasn't reachable through 127.0.0.1. The fact
> that the code set the IPV6_V6ONLY socket option didn't help, because
> that option only works when the socket gets bound to the IPv6 wildcard
> address (::), but is useless for explicit address bindings.
This seems to be something we overlooked in the initial impl. I don't
see any alternative but to make QEMU listen on multiple sockets in
the scenario you describe. An even clear example is to consider binding
QEMU to a machine with multiple non-localhost addresses, eg
myserver.com resolving to 192.168.122.41 + 2a00:123:456::1
because there's no way that the kernel can know/decide to automatically
listen on 192.168.122.41, when given the address 2a00:123:456::1 and if
the machine has many NICs, you can't assume the wildcard address is
suitable either.
> The attached patch against QEMU 0.11.0 extends inet_listen() to create
> sockets for as many addresses from the address list as possible and
> adapts its callers and their data structures to deal with a linked
> list of socket FDs rather than a single file descriptor.
The approach looks reasonable, though the patch is somewhat mangled
by the mix of tabs + spaces
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2010-05-05 8:29 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
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 [this message]
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=20100505082945.GB8862@redhat.com \
--to=berrange@redhat.com \
--cc=max@suse.de \
--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 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.