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: Mon, 09 Jan 2017 04:30:08 +0000
  • Message-id: <bug-1018741-21960-BglCoWVZiN@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1018741
http://bugzilla.opensuse.org/show_bug.cgi?id=1018741#c4

--- Comment #4 from Gary Ching-Pang Lin <glin@xxxxxxxx> ---
(In reply to lists dev from comment #3)
When the TianoCore logo showed (in the very beginning)

I do not see the TianoCore logo when booting my DomU clients.

The only time I can *recall* seeing it was "way back" when I installed the
DomU.

Which "beginning" are you referring to?

Can I get BACK into the config menu for this existing Guest ?

It's easier to see the logo when booting the guest with sdl or vnc, and the
logo will be gone quickly.

Another possible way is to clear NvVars. Don't do it in the guest since ovmf
will write the current configuration later. Mount the disk image directly and
remove NvVars. If there is no NvVars, ovmf will just use the default values.

I guess the guest booted with ovmf-x86_64-ms before so the MS keys were
written into NvVars. I'll try to reproduce the issue with my machine.

Wouldn't the guest only boot with ovmf-x86_64-ms if it was SPECIFIED in the
.cfg?

My .cfg has always had

bios_override = '/usr/share/qemu/ovmf-x86_64.bin'

specified.
By default, xen in openSUSE use ovmf-x86_64-ms.bin. But if the guest always
booted with ovmf-x86_64.bin, it's very strange to see the MS keys existed in
NvVars.

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