Project

General

Profile

Actions

tickets #167404

open

download.i.o.o does not preserve boot entry

Added by crameleon about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Core services and virtual infrastructure
Target version:
-
Start date:
2024-09-25
Due date:
% Done:

0%

Estimated time:

Description

After the OVMF issue which caused us to switch to the smm-suse variant https://progress.opensuse.org/projects/opensuse-admin/repository/salt/revisions/33649b89410ab0ec65bb3c576de27cf96d46025d we reset the NVRAM of all affected VMs and reinstalled shim/grub. Now it seems download.i.o.o did not appreciate this treatment, it always boots into what seems to be the GRUB image instead of the Shim one, effectively causing the loading of Linux to fail. Manually selecting shim.efi in the EFI boot menu makes it boot fine. Reinstalling shim through pbl --install (which does installs shim and creates the EFI boot entry as can be confirmed in /var/log/pbl.log) as done already before does not help / the opensuse-secureboot entry appears in efibootmgr but is gone again with the next reboot. A manually created "permanent" boot entry in the EFI setup does not persist either.
So far, download.i.o.o seems to be the only machine with this issue, another which got the same OVMF switching treatment seems to have rebooted fine, but we should reboot all of them once or observe update reboots over the next days to gather if any others are effected.

Actions #1

Updated by crameleon about 2 months ago

  • Private changed from Yes to No
Actions #2

Updated by crameleon about 2 months ago

I confirmed now none of the other VMs on the same hypervisor have this issue albeit them all using the same loader/nvram domain configuration on the host as well as the same bootloader configuration in the guest. I tried to un- and redefine download.i.o.o (including deleting its nvram variables again), it did not help.

Actions

Also available in: Atom PDF