From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/4] sockets: helper functions for qemu.
Date: Fri, 31 Oct 2008 17:50:23 +0000 [thread overview]
Message-ID: <20081031175023.GM29492@redhat.com> (raw)
In-Reply-To: <490B424C.7060404@codemonkey.ws>
On Fri, Oct 31, 2008 at 12:37:16PM -0500, Anthony Liguori wrote:
> Gerd Hoffmann wrote:
> >@@ -8280,6 +8281,9 @@ static void help(int exitcode)
> > "-redir [tcp|udp]:host-port:[guest-host]:guest-port\n"
> > " redirect TCP or UDP connections from host to
> > guest [-net user]\n"
> > #endif
> >+ "-ipv4 Use IPv4 only.\n"
> >+ "-ipv6 Use UPv6 only.\n"
> >+ " By default qemu uses what is available on
> >your machine.\n"
> > "\n"
> > "Linux boot specific:\n"
> > "-kernel bzImage use 'bzImage' as kernel image\n"
> >@@ -8386,6 +8390,8 @@ enum {
> > QEMU_OPTION_bootp,
> > QEMU_OPTION_smb,
> > QEMU_OPTION_redir,
> >+ QEMU_OPTION_ipv4,
> >+ QEMU_OPTION_ipv6,
> >
> > QEMU_OPTION_kernel,
> > QEMU_OPTION_append,
> >@@ -8489,6 +8495,10 @@ static const QEMUOption qemu_options[] = {
> > #endif
> > { "redir", HAS_ARG, QEMU_OPTION_redir },
> > #endif
> >+ { "4", 0, QEMU_OPTION_ipv4 },
> >+ { "6", 0, QEMU_OPTION_ipv6 },
> >+ { "ipv4", 0, QEMU_OPTION_ipv4 },
> >+ { "ipv6", 0, QEMU_OPTION_ipv6 },
>
> I don't like the idea of aliasing these options. Please just stick with
> one set of options.
>
> And do we really need to have options for this? Can't we just do the
> right thing? I can't believe that every application has to have an ipv6
> switch to be ipv6 enabled.
Gerd's patch does 'do the right thing' for 90% of people - it uses the
AI_ADDRCONFIG flag. This means that the getaddrinfo() name lookup will
only return an IPv6 address if there is at least one NIC with IPv6
configured, likewise only return an IPv4 address if there is at least
one NIC with IPv4 configured. There are still times when it is desirable
to restrict it to just IPv4 or just IPv6, regardless of your host NIC
config - mostly when needing to interact with other broken apps which are
not correctly IPv6 aware. Maybe it would be sufficient to just have it added
as a flag to the arg in question though, eg -serial tcp:localhost:123,ipv4
rather than a global -ipv4 flag
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.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:[~2008-10-31 17:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 12:47 [Qemu-devel] [PATCH v2 0/4] ipv6 and autoport patches Gerd Hoffmann
2008-10-31 12:47 ` [Qemu-devel] [PATCH 1/4] Implement "info chardev" command Gerd Hoffmann
2008-10-31 17:32 ` Anthony Liguori
2008-10-31 12:47 ` [Qemu-devel] [PATCH 2/4] sockets: helper functions for qemu Gerd Hoffmann
2008-10-31 17:37 ` Anthony Liguori
2008-10-31 17:50 ` Daniel P. Berrange [this message]
2008-10-31 17:58 ` Anthony Liguori
2008-10-31 19:44 ` Jamie Lokier
2008-11-03 15:35 ` Gerd Hoffmann
2008-10-31 12:47 ` [Qemu-devel] [PATCH 3/4] sockets: switch vnc to new code, support vnc port auto-allocation Gerd Hoffmann
2008-10-31 12:47 ` [Qemu-devel] [PATCH 4/4] sockets: switch over tcp/telnet/unix serial line to new helper functions Gerd Hoffmann
-- strict thread matches above, loose matches on Subject: below --
2008-10-28 12:55 [Qemu-devel] [PATCH 0/4] ipv6 and autoport patches Gerd Hoffmann
2008-10-28 12:55 ` [Qemu-devel] [PATCH 2/4] sockets: helper functions for qemu Gerd Hoffmann
2008-10-28 13:15 ` Daniel P. Berrange
2008-10-28 14:22 ` Gerd Hoffmann
2008-10-28 14:31 ` Daniel P. Berrange
2008-10-28 15:10 ` Gerd Hoffmann
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=20081031175023.GM29492@redhat.com \
--to=berrange@redhat.com \
--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).