http://bugzilla.opensuse.org/show_bug.cgi?id=1018741
http://bugzilla.opensuse.org/show_bug.cgi?id=1018741#c27
--- Comment #27 from Gary Ching-Pang Lin
(In reply to Gary Ching-Pang Lin from comment #20) opensuse ignores the presence/use of it?
Just putting some context around that question,
since -- from within the chroot'd Guest -- apparently I
(1) can't manage to write to the OVMF bios boot menu (2) startup.nsh is ignored
If I were to create a standalone .efi, e.g.,
grub2-mkstandalone \ -d /usr/lib/grub2/x86_64-efi/ \ -O x86_64-efi \ --modules="..." \ --fonts="..." \ --locales="..." \ --themes="..." \ -o "/boot/efi/EFI/opensuse/grub-standalone-test.efi" \ "boot/grub2/grub.cfg=/boot/grub2/grub.cfg"
how would I convince opensuse xen/ovmf to use that^ on boot if startup.nsh is not used ?
Would I have to rename it as grub.efi or grubx64.efi? That doesn't seem a good idea.
For the one-time boot, enter the "Boot Maintenance Manager" and choose "Boot
From File" to find the specific efi image. To create a permanent boot option, choose "Boot Options" -> "Add Boot Option". You can change the boot order with "Boot Options" -> "Change Boot Order". But it seems your guest has problem to save NvVars correctly, I'm not sure if the boot option will be saved.
-- You are receiving this mail because: You are on the CC list for the bug.