[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim

[Mathieu Trudel-Lapierre]

As Laszlo mentioned, this can affect other systems than QEMU. I
definitely can't boot the ISO on my thinkpad when shim debugging is
enabled.

Then, as discussed, fallback.efi shouldn't be on the ISO. It's clearly
not going to work due to the way shim is designed. Given that, we don't
need a debian-cd task to install fallback...

I'm working on preparing the shim update since yesterday. I can get you
a working shim if necessary for testing for a custom remastered CD
image.

** Changed in: grub2 (Ubuntu)
       Status: New => Triaged

** Changed in: debian-cd (Ubuntu)
       Status: Triaged => Invalid

** Changed in: grub2 (Ubuntu)
   Importance: Medium => High

** Changed in: shim (Ubuntu)
       Status: Triaged => In Progress

** Changed in: grub2 (Ubuntu)
       Status: Triaged => In Progress

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

Title:
  yakkety: backport (or rebase to) fix eliminating a double-close in
  shim

Status in debian-cd package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  In Progress
Status in shim package in Ubuntu:
  In Progress

Bug description:
  Sometime after August 25th (or so) something changed in the Yakkety
  ISOs that make them no longer boot under QEMU in UEFI mode. However,
  the ISOs do work fine still on the physical UEFI hardware I've tested
  (3 different systems). I'm not sure about other VM solutions like
  Virtual Box, etc., as I haven't tested under anything other than QEMU.
  But under QEMU, UEFI mode installs are definitely broken.

  You get stuck in the OVMF firmware with the following text on the
  screen (see attached screenshot):

  Boot Failed. EFI Floppy
  Boot Failed. EFI Floppy 1

  Thus far I've only tested with a Xenial host, so I'm not sure whether
  this problem exists with a Yakkety host + Yakkety guest.

  This problem also doesn't seem to be the result of any changes in QEMU
  (and related) in Xenial. With a Xenial host, you can still do UEFI
  mode installs fine under QEMU when the guest is using the 16.04.1
  ISOs, and likewise when the guest is using the latest Xenial daily
  (16.04.2 WIP) ISOs. So the problem seems to be only when using a
  Yakkety guest in UEFI mode.

  Note this problem effects both Yakkety desktop and server ISOs (when
  installing under QEMU in UEFI mode).

  Finally, on the off chance it might be helpful to anyone who comes
  across this bug report, I wrote a blog post a while back on how to use
  QEMU in UEFI mode on a Xenial (or newer) host:

  http://blog.system76.com/post/139138591598/howto-qemu-w-ubuntu-xenial-
  host-uefi-guest

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions