El 15/02/12 13:35, Joey Boggs escribió:
On 02/15/2012 11:05 AM, Federico Alberto Sayd wrote:
El 15/02/12 12:34, Joey Boggs escribió:
On 02/15/2012 10:20 AM, Federico Alberto Sayd wrote:
El 14/02/12 13:29, Joey Boggs escribió:
On 02/14/2012 10:36 AM, Federico Alberto Sayd wrote:
El 14/02/12 10:35, Joey Boggs escribió:
On 02/14/2012 08:29 AM, Federico Alberto Sayd wrote:
Hello:
Recently I downloaded the ovirt stable node image. According to
releases notes since 2.2.2 UEFI installation bug has been
fixed, but I still can't boot from my server with UEFI. Ovirt
installs without problem, but when the system reboots nothing
happens, the system don't boot. Then I try to boot with super
grub disk 2 live cd, it detects ovirt installation and boots
the system.
I think that still there is a problem with UEFI in certain
hardware:
Mi system is a IBM blade center HS22 7870
Can anyone confirm problems with UEFI in 2.2.2 version?
Thanks
Federico
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Can you boot the image like you did with the grub livecd and run
efibootmgr -v also mount /dev/disk/by-label/EFI and run find on
where you mounted it.
Ok,
efibootmgr -v
Fatal: Couldn't open either sysfs or procfs directories for
accessing EFI variables.
Try 'modprobe efivars' as root
I can't mount /dev/disk/by-label/EFI, when I create a directory
and try to mount the partition, mount says:
mount: /dev/sda1 already mounted or disco busy
however, mount output don't show that /dev/sda1 is mounted
Some directories are in read only mode and I could not create a
directory to mount the partition, I tried into /config and /live.
/dev/disk/by-label/EFI points to /dev/sda1 and "disco" is the
directory mount point.
Also, /proc/efi/vars/ and /sys/firmware/efi/vars/ are not
present
Thanks
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Ah.. was assuming the grub disc you booted from was EFI enabled.
Try booting the node iso in EFI mode and run through those steps
again.
Super grub disk detects the grub.cfg from ovirt's installation and
loads the system from this configuration. Therefore I assume that
the kernel parameters from grub config loads the system with EFI
enabled.
The grub config from grub's console is:
setparams 'oVirt Node Hypervisor 2.2.2-2.2.fc16'
set root=(hd0,3)
linux /vmlinuz0 root=live:LABEL=Root ro rootfstype=auto
rootflags=ro crashkernel=512M-2G:64M,2G-:128M elevator=deadline
quiet rd_NO_LVM rhgb rd.luks=0 rd.md=0 rd.dm=0
initrd /initrd0.img
EFI boot process is done before the grub config comes into play, and
the grub config has a few extra lines in it. The machine I'm testing
on when you goto the boot menu will show UEFI: $CD_DEVICE_NAME or
for boot entries for ovirt it would show: oVirt Node Hypervisor If
your grub cd supports efi booting it will be noticeable in the boot
menu. In order to do an efi installation it has to be booted in efi
mode for it to properly setup the boot entries.
Before the Ovirt entry on Grub menu, Grub2 displays the config detected:
setparams '(hd0,gpt3)/grub2/grub.cfg' 'hd0,gpt3'
'(hd0,gpt3)/grub2/grub.cfg'
cfg_device="$2"
cfg="$3"
root="$cfg_device"
configfile "$cfg"
Is there where "UEFI:" parameter must be present?
Sorry, I am a newbie to UEFI and Grub2, meanwhile I am reading all I
can about Grub2 and UEFI
Thanks
Thanks
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
You would see it just past the machine posting, on mine you would
press F8 to reach a boot menu and then select cd/usb/etc from there.
The uefi trigger happens similar to the machine reading a mbr on a
drive. One way to notice if its working or not it a higher resolution
perception on the monitor, text is smaller and the screen doesn't
appear as the normal 80x25 console line/columns. You just need to find
the right combination of keys to get in the menu. By livecd-tools
defaults the ovirt-node iso supports efi loading. Grub2/uefi support
in Fedora isn't quite there yet, so in this case we're still using
legacy grub's efi loader and writing an alternate grub config to match
it, similar to how Fedora is doing it until grub2 support is there.
I guess now I understand you. I have been searching in the UEFI text
interface of the blade and it allows browse the EFI System Partition and
choose a file to boot. However this EFI interface don't show any file to
boot.
Then I booted the system with another livecd and mounted the EFI
partition; I found that there was not any file in the EFI partition. It
seems that blade don't boot because it don't find the efi boot archives.
Could it be that ovirt installation fails to write efi boot files? Any
idea to debug the installation process?
Thanks and sorry for my basic English.
_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
