From: gregory.lee.bartholomew@gmail.com
To: devel@edk2.groups.io
Subject: BUG: tianocore does not honor the bootorder
Date: Wed, 15 Feb 2023 14:20:23 -0600 [thread overview]
Message-ID: <e0d5559bd69cc97ba85ffc7212350008b01d3875.camel@gmail.com> (raw)
I have a script that uses Qemu to install a Linux OS to the supplied device. At
the end of the install script, efibootmgr is called to create UEFI boot entries
and set the boot order. However, every time I boot the VM, it boots to entry
0004 "UEFI Misc Device" instead of the proper entry specified in the bootorder.
This is confusing a script that I have for managing multiple ESPs (the script
needs to detect the current ESP and sync its contents to secondary/backup ESPs).
Below is the output from efibootmgr on one of my scripted installations.
# efibootmgr
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0002,0001,0000,0003,0004,0005,0006,0007,0008,0009,000A
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-
7614-4503-836e-8ab6f4662331)
Boot0001* boot@b HD(1,GPT,b0077ac5-be27-4b22-bdf1-
e7256e4731de,0x800,0x200000)/File(\efi\systemd\systemd-bootx64.efi)
Boot0002* boot@a HD(1,GPT,70d1956e-7522-47d4-8319-
49a96674ecf1,0x800,0x200000)/File(\efi\systemd\systemd-bootx64.efi)
Boot0003* UEFI QEMU DVD-ROM QM00003
PciRoot(0x0)/Pci(0x1,0x1)/Ata(1,0,0){auto_created_boot_option}
Boot0004* UEFI Misc
Device PciRoot(0x0)/Pci(0x5,0x0){auto_created_boot_option}
Boot0005* UEFI Misc Device
2 PciRoot(0x0)/Pci(0x6,0x0){auto_created_boot_option}
Boot0006* UEFI PXEv4
(MAC:8232FE36D480) PciRoot(0x0)/Pci(0x3,0x0)/MAC(8232fe36d480,1)/IPv4(0.0.0.00.0.0.0,0,0){auto_created_boot_option}
Boot0007* UEFI PXEv6
(MAC:8232FE36D480) PciRoot(0x0)/Pci(0x3,0x0)/MAC(8232fe36d480,1)/IPv6([::]:<->[::]:,0,0){auto_created_boot_option}
Boot0008* UEFI HTTPv4
(MAC:8232FE36D480) PciRoot(0x0)/Pci(0x3,0x0)/MAC(8232fe36d480,1)/IPv4(0.0.0.00.0.0.0,0,0)/Uri(){auto_created_boot_option}
Boot0009* UEFI HTTPv6
(MAC:8232FE36D480) PciRoot(0x0)/Pci(0x3,0x0)/MAC(8232fe36d480,1)/IPv6([::]:<->[::]:,0,0)/Uri(){auto_created_boot_option}
Boot000A* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-
3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Please fix tianocore to honor the bootorder instead of creating its own entries.
Thanks.
--
Gregory Lee Bartholomew
PGP Key ID: 3B67510E
next reply other threads:[~2023-02-15 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 20:20 gregory.lee.bartholomew [this message]
2023-02-17 13:08 ` [edk2-devel] BUG: tianocore does not honor the bootorder Gerd Hoffmann
2023-02-17 16:23 ` Gregory Lee Bartholomew
2023-02-20 7:10 ` Gerd Hoffmann
2023-02-20 16:44 ` Gregory Lee Bartholomew
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0d5559bd69cc97ba85ffc7212350008b01d3875.camel@gmail.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox