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

[Dimitri John Ledkov]

Public bug reported:

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.

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

** Package changed: grub (Ubuntu) => grub2 (Ubuntu)

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

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

Status in “grub2” package in Ubuntu:
  New

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/grub2/+bug/1275162/+subscriptions