From: Michael Brown <mcb30@ipxe.org>
To: Gerd Hoffmann <kraxel@redhat.com>, Cole Robinson <crobinso@redhat.com>
Cc: ipxe-devel@ipxe.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu
Date: Wed, 27 Jan 2016 13:06:05 +0000 [thread overview]
Message-ID: <56A8C0BD.4080406@ipxe.org> (raw)
In-Reply-To: <1453818064.24277.29.camel@redhat.com>
On 26/01/16 14:21, Gerd Hoffmann wrote:
>> A fedora user requested it here:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1280318
>
> Ping?
>
> What is the reason for ipv6 not being enabled by default?
> Just historical?
> Rarely used in practice?
> ROM image size issues?
> Stability concerns?
>
> From qemu point of view this change is fine.
> ROM becomes slightly larger (~15k), but that isn't a problem.
ROM image size concerns.
I've been thinking for some time now that it would be useful to have a
"minimal" configuration used for building real BIOS option ROM images
and a "normal" configuration for everything else (undionly.kpxe,
ipxe.efi, UEFI ROMs, qemu ROMs, etc). There are several features that
are sufficiently commonly used that it would be worth having them
generally available in the default binaries, but which are currently
disabled by default due to BIOS ROM size concerns.
We already have the named config mechanism. I wonder if building a BIOS
option ROM for a real NIC is sufficiently specialised that it would make
sense to have a CONFIG=rom or CONFIG=minimal named configuration.
Thoughts from anyone?
Michael
next prev parent reply other threads:[~2016-01-27 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 17:25 [Qemu-devel] [PATCH ipxe] build: Enable IPv6 for qemu Cole Robinson
2016-01-12 22:18 ` Cole Robinson
2016-01-26 14:21 ` Gerd Hoffmann
2016-01-27 13:06 ` Michael Brown [this message]
2016-01-27 13:49 ` [Qemu-devel] [ipxe-devel] " Gerd Hoffmann
2016-01-27 16:39 ` Christian Nilsson
2016-01-28 10:19 ` Gerd Hoffmann
2016-01-28 16:42 ` Michael Brown
2016-01-28 17:49 ` Laszlo Ersek
2016-01-28 17:50 ` Laszlo Ersek
2016-01-28 11:50 ` Tore Anderson
2016-03-03 12:56 ` Tore Anderson
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=56A8C0BD.4080406@ipxe.org \
--to=mcb30@ipxe.org \
--cc=crobinso@redhat.com \
--cc=ipxe-devel@ipxe.org \
--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 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.