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:

In order to better support "minivm" use cases, e.g. for kubevirt, we should consider reducing the emulated flash device sizes. The flash devices consume much more memory than necessary as they get fully mapped into the guest memory, whether the space is needed or not. Currently less than 1 MB is needed, but 128 MB (64 MB for edk2 and 64 MB for varstore) are mapped.

Shrinking the size will have machine type compatibility issues and may introduce issues with later expansion, so we need to consider this carefully. Gerd Hoffmann suggested that we shrinking may be OK as long we we maintain the same offsets for the devices in the memory map, but it needs more investigation.

This looks like a duplicate of BZ 2131254 ("Remove the necessity to pad the edk2 images to 64MB"). Gerd, can we close this BZ as dup?

(In reply to Eric Auger from comment #4)
> This looks like a duplicate of BZ 2131254 ("Remove the necessity to pad the
> edk2 images to 64MB"). Gerd, can we close this BZ as dup?

Yes.

*** This bug has been marked as a duplicate of bug 2131254 ***