I'm setting up GRUB2-booting of Xen on EFI
Reading
http://lists.xenproject.org/archives/html/xen-users/2014-03/msg00142.html
http://wiki.xenproject.org/wiki/Xen_EFI
Booting Xen.gz via GRUB2 can't be done directly, but needs a chainloader
workaround. The example GRUB2 config given is:
menuentry 'Xen EFI' {
insmod part_gpt
insmod search_fs_uuid
insmod chain
chainloader (hd0,gpt1)/EFI/XEN/xen.efi
}
On EFI opensuse with grub2 & Xen installed,
find / | egrep "xen|grub" | grep "\.efi$"
/boot/grub2/x86_64-efi/grub.efi
/boot/grub2/x86_64-efi/core.efi
/boot/efi/EFI/opensuse/grubx64.efi
/usr/lib/grub2/x86_64-efi/grub.efi
/usr/lib64/efi/grub.efi
/usr/lib64/efi/xen.efi
/usr/lib64/efi/xen-4.efi
/usr/lib64/efi/xen-4.5.0_03-359.efi
/usr/lib64/efi/xen-4.5.efi
The xen.efi file is located
/usr/lib64/efi/xen.efi
not at the target path
chainloader (hd0,gpt1)/EFI/XEN/xen.efi
(1) Is the right procedure to simply
mkdir -p /boot/efi/EFI/XEN
cp /usr/lib64/efi/xen.efi /boot/efi/EFI/XEN/
(2) If the Xen install doesn't populate xen.efi into that directory, then at
every Xen update/upgrade, will xen.efi need to be re-copied manually?
(3) With the GRUB2-installed opensuse, I find no more 'device.map' file under
/boot/...
Is device.map still used? If none exists, what's the default mapping?
For a given location, how do you query/return the device-map drive ?
E.g.,
grub2-probe --target=device /boot/efi
returns
/dev/sdc2
In order to correctly modify the example's "(hd0,gpt1)" in
chainloader (hd0,gpt1)/EFI/XEN/xen.efi
I need to know whether /dev/sdc2 is (hd0) or (hd1) etc.
LT
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
