Mailinglist Archive: opensuse-bugs (4250 mails)

< Previous Next >
[Bug 1018741] after Xen 4.7 -> 4.8 upgrade, Xen PVHVM/UEFI guests fail to boot; hang @~ OVMF
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 10 Jan 2017 17:32:55 +0000
  • Message-id: <bug-1018741-21960-WI1w7w5kRt@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1018741
http://bugzilla.opensuse.org/show_bug.cgi?id=1018741#c24

lists dev <lists@xxxxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?(glin@xxxxxxxx)

--- Comment #24 from lists dev <lists@xxxxxxxxxxxx> ---
(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.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References