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.

Created attachment 1774729 [details]
dual boot kickstart file

Description of problem:
When I use the kickstart file to build a BIOS+UEFI dual boot image, it cannot boot after installed.
I worked well with RHEL-9.0.0-20210414.0 but cannot work with RHEL-9.0.0-20210418.3 and later composes.

Version-Release number of selected components (if applicable):
RHEL-9.0.0-20210418.3 and later composes

How reproducible:
100%

Steps to Reproduce:
1. Prepare a dual boot kickstart file(see the attachment). Create a 10G qcow2 file:
# qemu-img create rhel-9.qcow2 10G -f qcow2
2. Create a .iso file and put the ks file in
3. Use virt-install to build the image:
# virt-install --name walatestimg --ram 2048 --network bridge=virbr0 --vcpus 2 --cdrom ks.iso --disk path=rhel-9.qcow2,bus=virtio --noreboot --boot uefi
4. Use virt-manager to boot it in KVM

Actual results:
1. First boot: can boot up and go to "login", but actually cannot login
2. After reboot, it hangs during boot:
systemd[1]: No /sbin/init, trying fallback
systemd[1]: Failed to execute /bin/sh, giving up: No such file or directory
systemd[1]: Freezing execution.

Expected results:
Can boot successfully.

Additional info:
If build a BIOS only image, it works well.

Hi Javier, 

Do you know of anything in grub2 from RHEL-9.0.0-20210418.3  (or later) that could impact dual boot image from booting?

Now I can use rhel-guest-image as a workaround. The rhel-guest-image is a dual boot image. So there might be something wrong in the kickstart file(although it worked well in RHEL-9 Alpha).

Removed testblocker keyword and change priority/severity to low.

Test in RHEL-9.0.0-20210905.7. It works now. Close this BZ.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days