Hide Forgot
Description of problem: burn the iso to cdrom/usb, fail to boot with UEFI enable in IBM x3550, but ok to boot with the legacy bios, compare with rhel6.2, could boot with UEFI enable Version-Release number of selected component (if applicable): rhev-hypervisor 6.2(snapshot3) 19.2 How reproducible: always Steps to Reproduce: 1.burn the iso to cdrom/livecd-iso-to-disk $usb 2.boot with legacy biso(ok to boot) 3.boot with UEFI(fail to boot) Actual results: in x3550, rhev-hypervisor install disk always fail to boot in UEFI mode, Expected results: rhev-hypervisor could boot in UEFI mode Additional info:
(In reply to comment #0) > 3.boot with UEFI(fail to boot) How do you choose between UEFI/legacy? It seems that default (at least on those machines) is to try UEFI and automatically boot legacy if EFI fails, in which case this is not that critical issue.
Created attachment 577660 [details] Dell R210 UEFI
Created attachment 577661 [details] fail to boot
Since the usb disk media can boot with efi mode and the iso is blocked by bz810060, move this bug to ON_QA and we will verify it after bz810060 is fixed.
I retry UEFI boot with latest build rhev-hypervisor6-6.3-20120509.1.el6 according to comment#30 steps.Both Dell R210 and Dell optiplex 990 fail to boot from usb disk under UEFI mode. But the Dell optiplex 990 success to boot rhev-hypervisor6-6.3-20120502.3.el6 under UEFI mode. So it may be a regression bug. I will go on to try the Dell R210 UEFI boot with rhev-hypervisor6-6.3-20120502.3.el6 tomorrow.
I retry the UEFI boot test, the Dell R210 can boot the rhev-hypervisor6-6.3-20120502.3.el6 from usb disk under UEFI mode. I also retry the Dell optiplex 990 to boot rhev-hypervisor6-6.3-20120509.1.el6 from usb disk under UEFI mode and find that the boot failure is mainly caused by /EFI/BOOT/BOOTX64.conf of the boot media, which specifies path of vmlinuz0 and initrd0.img as "/EFI/BOOT". While the last build rhev-hypervisor6-6.3-20120502.3.el6 specifies the correct path as "/syslinux". So edit the UEFI boot item as the correct path, the Dell optiplex 990 also can boot rhev-hypervisor6-6.3-20120509.1.el6 from usb disk under UEFI mode. After bootting under UEFI mode, install the rhev-hypervisor6-6.3-20120509.1.el6 into local disk, it successes without error. But it fails to boot from local disk with UEFI or legacy BIOS mode. This is tracked by another bug 749621.
Environment: rhev-hypervisor6-6.3-20120516.0.el6 rhev-hypervisor-tools-2.3.0-7.el6 rhevh-iso-to-disk --format --efi rhevh-6.3-20120516.0.el6.iso /dev/sdb It still fails to boot from usb disk under UEFI mode. The main cause is the specified path of vmlinuz0 and initrd0.img, "/EFI/BOOT/", but there's no vmlinuz0 and initrd0.img in that directory.
Verify this bug with rhevh-6.3-20120523.1 on Dell R510. Make the usb boot media with command "rhevh-iso-to-disk --format --efi rhevh-6.3-20120523.1.el6.iso /dev/sdb" and boot from the usb disk under UEFI mode, it successes.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously, the ISO image did not include UEFI kernel and initramfs. Now, the image correctly includes the components and directory structure needed to boot the ISO on a UEFI enabled machine.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -Previously, the ISO image did not include UEFI kernel and initramfs. Now, the image correctly includes the components and directory structure needed to boot the ISO on a UEFI enabled machine.+Previously, the ISO image did not include a UEFI kernel and initramfs. As a result it was not possible to boot UEFI enabled systems from optical media created using the image. The image has been updated. It now includes the components and directory structure needed to boot on a UEFI enabled machine.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0741.html