[Bug 1275162] Re: incorrect efibootmgr command is set by update-grub under OVMF

[Chris J Arges]

Hello Dimitri, or anyone else affected,

Accepted grub2 into trusty-proposed. The package will build now and be
available at
http://launchpad.net/ubuntu/+source/grub2/2.02~beta2-9ubuntu1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: grub2 (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  incorrect efibootmgr command is set by update-grub under OVMF

Status in “efibootmgr” package in Ubuntu:
  Invalid
Status in “grub2” package in Ubuntu:
  Fix Released
Status in “efibootmgr” source package in Trusty:
  Invalid
Status in “grub2” source package in Trusty:
  Fix Committed
Status in “grub2” package in Debian:
  Fix Released

Bug description:
  I'm running OVMF from trusty, under qemu started like this:

  $ qemu-system-x86_64 -pflash OVMF.fd -m 1024 -drive
  file=nvme.img,if=none,id=D22 -device nvme,drive=D22,serial=1234
  --enable-kvm

  where nvme.img is my disk drive.

  After the installation & secure-boot key enrollment, the added
  "ubuntu" boot entry fails to boot. I've added one manually using EFI
  shell and the correct enumerated device drive (fs0:) and made it top
  priority. That one worked. Comparing the output of the two using
  efibootmgr I get the following output:

  BootCurrent: 0006
  BootOrder: 0006,0005,0000,0001,0002,0003,0004
  Boot0000* EFI Floppy	ACPI(a0341d0,0)PCI(1,0)ACPI(60441d0,0)
  Boot0001* EFI Floppy 1	ACPI(a0341d0,0)PCI(1,0)ACPI(60441d0,1)
  Boot0002* EFI DVD/CDROM	ACPI(a0341d0,0)PCI(1,1)ATAPI(1,0,0)
  Boot0003* EFI Misc Device	ACPI(a0341d0,0)PCI(4,0)03171000010000000000000000000000
  Boot0004* EFI Internal Shell	MM(b,3fafd000,3ffbcfff)
  Boot0005* ubuntu	HD(1,0,0,1ca5fb01)File(\EFI\ubuntu\shimx64.efi)
  Boot0006* 'ubuntu-custom'	ACPI(a0341d0,0)PCI(4,0)03171000010000000000000000000000HD(1,800,f3800,075e987d-5ca9-4c04-82f1-7967bc2dca5f)File(\EFI\ubuntu\shimx64.efi)

  
  It appears as if an efi boot entry was added for an HD/MBR like partition, instead of one address by ACPI/PCI and the full partition UUID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1275162/+subscriptions