[Bug 1912830] Re: Use non-removable uefi bootloader in cloud-images by default

Dimitri John Ledkov 1912830 at bugs.launchpad.net
Tue Feb 9 20:40:39 UTC 2021


>From https://launchpad.net/~xnox/+livefs/ubuntu/focal/any/+build/259783

downloading the .img (qcow) image

mounting p15 i can see that /ubuntu/ paths now exist, and will be used
for booting via BOOTX64.CSV

 tree /mnt/
/mnt/
└── EFI
    ├── BOOT
    │   ├── BOOTX64.EFI
    │   ├── fbx64.efi
    │   └── mmx64.efi
    └── ubuntu
        ├── BOOTX64.CSV
        ├── grub.cfg
        ├── grubx64.efi
        ├── mmx64.efi
        └── shimx64.efi

3 directories, 8 files

Mounting the p1 partition I can see that fsck will be performed on both
partitions

$ cat /mnt/etc/fstab
LABEL=cloudimg-rootfs / ext4 defaults 0 1
LABEL=UEFI /boot/efi vfat defaults 0 1

$ LD_PRELOAD=/mnt/usr/lib/systemd/libsystemd-shared-245.so /mnt/usr/bin/systemd-detect-virt 
none


can be executed and is present (although this image would not have triggered the bug of missing systemd-detect-virt, this bug would need to be verified elsewhere)

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1912830

Title:
  Use non-removable uefi bootloader in cloud-images by default

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Fix Committed
Status in livecd-rootfs source package in Bionic:
  Fix Committed
Status in livecd-rootfs source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

   * use non --removable uefi installation for cloud-images

   * Currently cloud-images use --removable grub installation, which
  makes the disk images look at lot more like our installer .isos, than
  installed systems.

     This causes many issues:

   * ubuntu efiboot entry is not created by the fallback manager from shim
   * one cannot reorder ubuntu boot entry, and/or boot and apply fwupdate updates (if possible)
   * measurements are unstable, and change if one call grub-install and or upgrades things
   * often grub & shim upgrades are not applied at all as \EFI\ubuntu does not exist on the ESP

   * We should switch to only shipping shim/fallback/mm in \ESP\Boot and
  ship \ESP\ubuntu on the cloud-image ESPs such that we regain stable
  measurements; ubuntu boot entry; and upgrades of grub and shim.

  [Test Case]

   * After UEFI firstboot $ efibootmgr --verbose => should contain
  `ubuntu` entry pointing at ESP\ubuntu\shim*.efi binary, which should
  be added to the bootorder

  [Where problems could occur]

   * Existing systems which were booted from previous style images, will
  not upgrade shim|grub on the ESP, and must call `grub-install` or
  `grub-multi-install` to correct that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912830/+subscriptions



More information about the foundations-bugs mailing list