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.
Created attachment 1478427[details]
OVMF iPXE dhcp server guest configure document
Description of problem:
The RHEL7.5 guest can not be booted via iPXE under the secure boot on RHEL7.6 host. It is because the Image is not signed.
The guest booting log said that "The image doesn't pass verification". The full log is in attachment.
It can be confirm that the RHEL7.5 guest is released. The guest can use secure boot via local iso. If the guest is booted via iPXE without the secure boot, the guest can work as well. However, it only can not be booted via iPXE and under the secure boot.
Version-Release number of selected component (if applicable):
[1] OVMF-20180508-3.gitee3198e672e2.el7.noarch
[2] qemu-img-rhev-2.12.0-11.el7.x86_64
[3] kernel:3.10.0-938.el7.x86_64
How reproducible:
See the attachment.
Steps to Reproduce:
1.Set up the efi pxe booting dhcp server guest;
2.Start an other guest and enable the secure boot;
3.Boot the guest via iPXE.
Actual results:
The guest is stuck.
Expected results:
The guest can go into install process.
Additional info:
In Raycom office, there is no uefi pxe booting dhcp server in public net. Thus, it is necessary that using a guest as the uefi pxe booting dhcp server. There is a document in attachment shows how to configure the efi pxe booting dhcp server guest.
This is not an OVMF bug. If you enable Secure Boot in OVMF and then try to net-boot (PXE-boot or HTTP-boot) an "ipxe.efi" UEFI binary that is not signed at all (or not signed with a key matching the Secure Boot certificate enrollment), it is then *expected* that OVMF reject the "ipxe.efi" image. If the unsigned "ipxe.efi" image were accepted, *that* would be a bug (a security bug at that).
I can see that you reused the example iPXE chainboot configuration that I created originally for bug 1462351. Please understand that I only created that configuration because Dan Yasny asked me specifically about iPXE, and I meant to check whether that would be technically feasible (see bug 1462351 comment 15). However, chain-booting with iPXE is not what the RHEL7 installation guide describes, for UEFI network installation. The guide describes firmware->shim->grub (no iPXE), and indeed that is expected to work with OVMF Secure Boot out of the box. (The setup is documented mainly in bug 1462351 comment 9.)
If you'd like to test iPXE with SB enabled, you will have to generate a new private key and self-signed certificate, manually sign iPXE with the private key, manually enroll the certificate in OVMF, and then netboot the signed iPXE image. There are tutorials on the net about signing UEFI images with personal keys for SB purposes, but that's out of scope for RHEL.
In addition, I strongly doubt we would ourselves sign (or ask Microsoft to sign) the "ipxe.efi" image that we ship in the "ipxe-bootimgs" subpackage. If you wish, you can open an RHBZ about that for the "ipxe-bootimgs" subcomponent (which is not under virt team jurisdiction), but, again, I strongly doubt we would sign "ipxe.efi".
Created attachment 1478427 [details] OVMF iPXE dhcp server guest configure document Description of problem: The RHEL7.5 guest can not be booted via iPXE under the secure boot on RHEL7.6 host. It is because the Image is not signed. The guest booting log said that "The image doesn't pass verification". The full log is in attachment. It can be confirm that the RHEL7.5 guest is released. The guest can use secure boot via local iso. If the guest is booted via iPXE without the secure boot, the guest can work as well. However, it only can not be booted via iPXE and under the secure boot. Version-Release number of selected component (if applicable): [1] OVMF-20180508-3.gitee3198e672e2.el7.noarch [2] qemu-img-rhev-2.12.0-11.el7.x86_64 [3] kernel:3.10.0-938.el7.x86_64 How reproducible: See the attachment. Steps to Reproduce: 1.Set up the efi pxe booting dhcp server guest; 2.Start an other guest and enable the secure boot; 3.Boot the guest via iPXE. Actual results: The guest is stuck. Expected results: The guest can go into install process. Additional info: In Raycom office, there is no uefi pxe booting dhcp server in public net. Thus, it is necessary that using a guest as the uefi pxe booting dhcp server. There is a document in attachment shows how to configure the efi pxe booting dhcp server guest.