From: Tore Anderson <tore@fud.no>
To: Michael Brown <mcb30@ipxe.org>
Cc: qemu-devel@nongnu.org, ipxe-devel@ipxe.org,
Gerd Hoffmann <kraxel@redhat.com>,
Cole Robinson <crobinso@redhat.com>
Subject: Re: [Qemu-devel] [ipxe-devel] [PATCH ipxe] build: Enable IPv6 for qemu
Date: Thu, 28 Jan 2016 12:50:49 +0100 [thread overview]
Message-ID: <20160128125049.10c8ed59@envy> (raw)
In-Reply-To: <56A8C0BD.4080406@ipxe.org>
* Michael Brown
> 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?
This makes a lot of sense to me. It is a shame that the default builds
of images meant for chain-loading are lacking many of the bells and
whistles. It seems sensible to me to let space-constrained builds
explicitly disable features in order to sufficiently shrink the image,
rather than allowing them to force a "lowest common denominator"
default set on features on all builds.
The lack of default IPv6 support in ipxe.efi is complicating the IPv6
migration for us. Not that it is particularly difficult to build and
distribute our own iPXE images, but it had been much more convenient if
we could use the distribution packages. It's just one more hoop that'd
we'd rather we didn't have to jump through.
It would be nice to have IPv6 support in the default undionly.kpxe too,
but it is less of an issue there as non-UEFI hardware generally
requires IPv4 to be present in the first place.
Tore
next prev parent reply other threads:[~2016-01-28 11:51 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 ` [Qemu-devel] [ipxe-devel] " Michael Brown
2016-01-27 13:49 ` 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 [this message]
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=20160128125049.10c8ed59@envy \
--to=tore@fud.no \
--cc=crobinso@redhat.com \
--cc=ipxe-devel@ipxe.org \
--cc=kraxel@redhat.com \
--cc=mcb30@ipxe.org \
--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.