- Package:
- grub-common
- Source:
- grub2
- Description:
- GRand Unified Bootloader (common files)
- Submitter:
- Sergio Gelato
- Date:
- 2020-11-27 03:24:03 UTC
- Severity:
- normal
xen-hypervisor-4.11-amd64 in buster installs the following files: /boot/xen-4.11-amd64.gz /boot/xen-4.11-amd64.efi /boot/xen-4.11-amd64.config The first one is bootable (usually; but see #924360). The second one may or may not be bootable by GRUB (I didn't succeed); it's probably meant for booting directly by UEFI. The third is just a summary of the hypervisor's build configuration and clearly not meant for booting. /etc/grub.d/20_linux_xen generates boot menu entries for all three. This seems excessive. The .config entry definitely shouldn't be there, and the .efi one does not work in its present form (although for all I know this may be fixable with better module settings). At the very least the .config file should be filtered out by file_is_not_sym(), grub_file_is_not_garbage() or similar. The .efi file clearly also requires attention but I'm not going to suggest a specific resolution yet. If GRUB can be made to boot it, maybe that would help solve #924360 on affected hardware; otherwise it would be better not to generate a menu entry for it (perhaps by not installing it in /boot, which would be a matter for the Debian Xen maintainers).
Some minor additions: 1. It turns out #924360 is no longer a concern. Not that I can see, anyway. 2. This is what I get when trying to boot from the .efi entry:----<snip>------ Loading Xen 4.11-amd64.efi ...Loading Xen 4.11-amd64.efi ... error: invalid arch-dependent ELF magic. error: invalid arch-dependent ELF magic. Loading Linux 4.19.0-9-amd64 ...Loading Linux 4.19.0-9-amd64 ... error: you need to load the kernel first. error: you need to load the kernel first. Loading initial ramdisk ...Loading initial ramdisk ... error: you need to load the kernel first. error: you need to load the kernel first. Press any key to continue...Press any key to continue... ----<snip>------ So at this time I don't see a point in generating those .efi menu entries.
found 963962 2.02+dfsg1-20+deb10u2 2.04-10 quit I was going to report I'd never observed this bug, but then I examined the grub.cfg files and I discover they're present. I would tend to rate this as minor, but the original submitter didn't adjust severity. With 2.04-10 the xen-4.*.config file entries are absent, but entries for both the .efi file and the other are produced. On an aarch64 system the .efi file can be booted by GRUB 2.04.