Frank, can you confirm if copying efi/EFI/redhat/grub.efi to the rhevh's Root partition is enough?

I tried it on a IBM x3650 M3
RHEL 6.1 installs correct with efi

RHEV-hypervisor (latest beta) Does install but doesn't setup EFI correct so the machine won't boot.

result:
It did make 2 boot partitions but both were formatted as ext3 and it did only put date on the boot-partition. 

expected result:
2 boot partitions: 1 for grub/kernels and 1 (formatted as vfat) for EFI.

(In reply to comment #4)
> RHEV-hypervisor (latest beta) Does install but doesn't setup EFI correct so the
> machine won't boot.

Is there an option to choose Legacy boot or something like that?

(In reply to comment #2)
> Frank, can you confirm if copying efi/EFI/redhat/grub.efi to the rhevh's Root
> partition is enough?

Replying to myself: no, it is not. Here's boot partition layout from RHEL 6.1 on an EFI box:

Boot disk:
p1      1049kB  211MB  210MB  fat16              boot
p2      211MB   735MB  524MB  ext4
p3      735MB   146GB  145GB                     lvm

p2 is mounted at /boot, p1 at /boot/efi
   /boot/efi/EFI/redhat/grub.conf
   /boot/efi/EFI/redhat/grub.efi
   /etc/grub.conf -> ../boot/efi/EFI/redhat/grub.conf
   /boot/grub/splash.xpm.gz
   /boot/grub/device.map

So we need to distinguish between EFI and Legacy machines, grub setup is quite different in each case.

(In reply to comment #5)

> 
> Is there an option to choose Legacy boot or something like that?

Yes I used it as workaround.

could reproduce on IBM x3550 machine, legacy boot is ok, boot with UEFI fail, as just  1 for grub/kernels and no boot partation (formatted as vfat) for EFI

Created attachment 530329 [details]
Patch 1

Small followup patch coming shortly

Created attachment 530330 [details]
Patch 2

Testing coming shortly

What the patch does:

Adds a new partition:  256MB (hard coded) with vfat filesystem that is flagged for boot
Also copies EFI contents to the new partition and automounts to /boot/efi in the running image

At this point, it has not been tested to boot EFI systems, but has been tested on non-EFI systems for no regressions.

Autoinstall fails due to inability to unmount liveos because of EFI mount


--- a/scripts/ovirt-config-boot
+++ b/scripts/ovirt-config-boot
@@ -183,6 +183,7 @@ ovirt_boot_setup() {
     mkdir -p $grub_dir/efi
     mount LABEL=EFI $grub_dir/efi
     cp -ra /boot/efi/* $grub_dir/efi
+    umount $grub_dir/efi
     cat > $grub_dir/grub.conf << EOF
 default saved
 timeout 5

Adding fstab entry was missed in TUI install

Created attachment 530505 [details]
Screenshot of grub menu booted with grub.efi

grub.conf also needs to be in the same folder with grub.efi
When grub.efi is selected manually in UEFI setup menu, it shows grub menu but fails to find partition - need to investigate why.

See bug 748725 comment 5 - if default is to try EFI and then legacy, fixing EFI boot shouldn't be a blocker. We only need to push the disk layout change since that affects future upgrades.

Cloned to bug 749621 for enabling EFI installs.

For this bug, we'll setup partitions only.

*** Bug 749477 has been marked as a duplicate of this bug. ***

Created attachment 530554 [details]
followup patch

fixes install on cciss
fixes missed umount in autoinstall
removes efi mount from fstab
doesn't set efi mount as "boot"

Test version:
rhev-hypervisor6-6.2-20111019.5.el6

TUI install RHEVH to cciss, after reboot will cause kernel panic. 
No such problem when auto install to cciss.
Please see attachment for more details.
So change bug status to ASSIGNED.

Created attachment 530610 [details]
kernel panic

(In reply to comment #28)
> Test version:
> rhev-hypervisor6-6.2-20111019.5.el6
> 
> TUI install RHEVH to cciss, after reboot will cause kernel panic. 
> No such problem when auto install to cciss.
> Please see attachment for more details.
> So change bug status to ASSIGNED.

The same issue occurs in version rhev-hypervisor6-6.2-20111026.2.el6.

Can you please provide the ovirt.log from the installation?  (You can boot from media, and extract it that way).  Or provide a console log for the installation?

(In reply to comment #32)
> Can you please provide the ovirt.log from the installation?  (You can boot from
> media, and extract it that way).  Or provide a console log for the
> installation?

About a few  seconds after boot to grub menu, the kernel panic will occur. So I can't obtain the ovirt.log file. 
There is no any output by serial console.

The ovirt log can be obtained by installing via TUI, then instead of choosing to reboot, drop to the shell, manually setup networking (use /usr/libexec/ovirt-config-networking) and root password/ssh password auth (use /usr/libexec/ovirt-config-password) then scp the log file off.

Created attachment 531054 [details]
/tmp/ovirt.log

Created attachment 531055 [details]
/var/log/ovirt.log-tmp

Thanks to jboggs and apevec


diff --git a/scripts/install.py b/scripts/install.py
index a80f049..d54c121 100755
--- a/scripts/install.py
+++ b/scripts/install.py
@@ -155,6 +155,8 @@ def ovirt_boot_setup():
         os.makedirs(grub_dir + "/efi")
         system("mount LABEL=EFI "+grub_dir+"/efi")
         system("cp -ra /boot/efi/* " + grub_dir + "/efi")
+        system("umount /liveos/grub/efi")
+
     if not system("cp -p /live/" + syslinux + "/vmlinuz0 " + initrd_dest):
         log("kernel image copy failed.")
         return False

    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:
Upgrades from beta to GA will result in an incorrect partitioning of the host.  GA version must be installed clean.

    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,3 @@
-Upgrades from beta to GA will result in an incorrect partitioning of the host.  GA version must be installed clean.+Upgrades from beta to GA will result in an incorrect partitioning of the host.  GA version must be installed clean.
+
+UEFI machines must be set to legacy boot options for RHEV-H to boot successfully after installation.

Informational only, here are the steps to boot in legacy mode on IBM M3 servers with UEFI BIOS, needed to properly install and boot RHEV-H:

* To enter the UEFI\Basic Input/Output System (BIOS) menu, power on the server and press F1 during the IBM splash screen.

* Using the arrow keys to navigate, scroll down to highlight "Boot Manager" and press Enter.

* “Add Boot Option” is highlighted by default. Press Enter.

* Using the down arrow key, scroll down until "Legacy Only" is highlighted. Press Enter.

* Select “Change Boot Order” and press Enter.

* Press Enter to begin changing the boot order.

* Highlight Legacy Only and press Shift + to move it to the top. Press Enter.

* Press the down arrow once to highlight "Commit Changes" and press Enter.

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-2011-1783.html