Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The linux-firmware package is huge:
# echo n | yum -C remove linux-firmware | grep size
Installed size: 96 M
None of this is useful on VMs / cloud images and is one of the biggest packages pulled in for no reason when creating minimal (cloud) images.
(For some reason one can actually do "yum -C remove linux-firmware" without issues but the next time kernel is upgraded linux-firmware is pulled in again.)
Version-Release number of selected component (if applicable):
RHEL 7.3 Beta / kernel-3.10.0-493.el7.x86_64
I'm going to close that as NOTABUG. The statement "None of this is useful on
VMs" isn't correct. Its often not needed, but thats not guaranteed. Some VF devices may well need firmware support, and I could easily
imagine that firmware would be needed for many usb devices that are assigned via
usb passthrough.
There is also the unified kernel issue to contend with. That is to say, the
same kernel that runs on a VM runs on a physical system, and while firmware may
often not be needed on the former, it is almost always needed on the latter.
If a VM wants to save the 100M that firmware offers, a custom install would be in order in which the %post section of a kickstart script removed the exact firmware files that an administrator knows aren't needed for that installation
Comment 3Richard W.M. Jones
2016-10-25 14:03:01 UTC
An alternative to consider is to reduce the strength of the
dependency from Requires -> Recommends. This would allow
kickstarts to remove the linux-firmware package without
forcing RPM.
Note that weak dependencies are a RHEL 8 feature AIUI, so
it wouldn't change the resolution of this bug.