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.
Bug 1427899 - RFE: add support for initrd overlays in grub2-mkconfig
Summary: RFE: add support for initrd overlays in grub2-mkconfig
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: grub2
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Peter Jones
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-01 13:29 UTC by Jaroslav Škarvada
Modified: 2022-01-14 19:52 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:32:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Proposed fix (988 bytes, patch)
2017-03-01 13:29 UTC, Jaroslav Škarvada
no flags Details | Diff

Description Jaroslav Škarvada 2017-03-01 13:29:42 UTC
Created attachment 1258681 [details]
Proposed fix

Description of problem:
Linux supports initrd overlays. User could have her/his own initrd overlay extending distro's provided initrd image. By using custom overlays user doesn't need to rebuild the main initrd image (which can take long time) nor need to customize it every time after e.g. kernel update.

We are going to use this functionality in RHEL to introduce performance / realtime related tunings into initrd. Grub2 seems to support it, but unfortunately i doesn't have configuration option for grub2-mkconfig.

Version-Release number of selected component (if applicable):
grub2-2.02-0.44.el7

How reproducible:
Always

Steps to Reproduce:
1. Try to install initrd overlay by using grub2-mkconfig

Actual results:
There is no way how to install initrd overlay by using grub2-mkconfig

Expected results:
An option in /etc/default/grub that will allow setting initrd overlay.

Additional info:
Attached patch adds support for GRUB_INITRD_OVERLAY option which could be used in /etc/default/grub to add the initrd overlay when running grub2-mkconfig.

Comment 2 Jaroslav Škarvada 2017-03-01 13:40:14 UTC
We would like to use this functionality in RFE bug 1414098.

Comment 3 Jiří Mencák 2019-11-26 08:08:50 UTC
Is there a reason not to accept the proposed fix?  There is an inconsistency that can affect users when tuned runs with the [bootloader] plugin and an admin re-creates /boot/grub2/grub.cfg by grub2-mkconfig.  Thanks!

Comment 5 RHEL Program Management 2021-01-15 07:32:18 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.