Your message dated Sun, 22 Nov 2020 21:37:57 +0100
with message-id <[email protected]>
and subject line Re: Bug#924360: Solved: ERR: Bootloader shutdown EFI x64 boot
services!
has caused the Debian Bug report #924360,
regarding xen-hypervisor-4.11-amd64: HVM Boot failure: "ERR: Bootloader
shutdown EFI x64 boot services!"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
924360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924360
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xen-hypervisor-4.11-amd64
Version: 4.11.1+26-g87f51bf366-3
Severity: important
Dear Maintainer,
* What led up to the situation?
unfortunately xen hypervisor does not boot on my machine (Asus Prime B360M-C
Mainboard, in Setup only EFI enabled, Intel VMX Virtalization Technology is
enabled, too). Installation was done according to https://wiki.debian.org/Xen .
With a serial connection, I get the boot messages (the last line is not visible
on the HDMI screen):
Loading Xen 4.11-amd64 ...
Loading Linux 4.19.0-2-amd64 ...
Loading initial ramdisk ...
error: no suitable video mode found.
ERR: Bootloader shutdown EFI x64 boot services!
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
"Normal" Linux (intended as dom0) boots perfectly.
By providing load_video on grub2 commandline I do not have the line "error: no
suitable video mode found." any more. However, the last error line stays the
same and only reset is possible.
After installing stable first I tried to upgrade/dist-upgrade to testing but
the problem stays the same.
I already tried to find something with Google related to the error but could
not find anything.
Kind regards,
Henning
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
xen-hypervisor-4.11-amd64 depends on no packages.
Versions of packages xen-hypervisor-4.11-amd64 recommends:
ii xen-hypervisor-common 4.11.1+26-g87f51bf366-3
ii xen-utils-4.11 4.11.1+26-g87f51bf366-3
xen-hypervisor-4.11-amd64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Sergio,
On 6/29/20 4:07 PM, Sergio Gelato wrote:
> The system I had encountered the problem on had been freshly upgraded from
> stretch. It turned out that while the GRUB *packages* had been upgraded, the
> boot loader in the EFI system partition was still from stretch. I had to
> explicitly
> grub-install --target=x86_64-efi
>
> After this, things are booting fine. So: GRUB issue, fixed in buster (but
> do pay attention to the version string on the GRUB menu screen at boot!)
Great, thanks for sharing this information. One of those things which
are easy to overlook...
Since there are no actionable items any more, we can close this one now.
And of course it'll be searchable so that if anyone else runs into the
same problem, this hint might show up.
Thanks,
Hans
--- End Message ---
