public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Pavan Kumar Aravapalli <pavankumar_a@accelerite.com>,
	devel@edk2.groups.io
Subject: Re: [edk2-devel] Help needed in building UEFI qcow2 images
Date: Wed, 5 Jun 2019 07:49:43 +0200	[thread overview]
Message-ID: <20190605054943.so4v63o7c2hqw42r@sirius.home.kraxel.org> (raw)
In-Reply-To: <64f4a3ff-01c8-42b1-c2d0-41807aba03b2@redhat.com>

  Hi,

> However: you're using a systemd-related UEFI boot loader, and I have
> no clue whether it implements the above-referenced "fallback"
> behavior. For now, I would suggest trying the shim+grub2 variant, and
> even Fedora 29 rather than Fedora 28:
> "fedora-29-efi-grub2-x86_64.qcow2.xz".

I can boot the images just fine with empty vars.

Just noticed that the systemd image has a lowercase efi directory, so
the fallback bootloader path is "efi/BOOT/BOOTX64.EFI" not
"EFI/BOOT/BOOTX64.EFI".  Possibly that is the root cause for the
problem.  In theory it should not, FAT is case-insensitive after all,
but who knows ...

> ... I guess it's also possible that the UEFI boot loader in the disk
> image that you've tried isn't properly signed, against the
> certificates enrolled in "/usr/share/OVMF/OVMF_VARS.secboot.fd". If
> that's the case, the OVMF debug log will show it.

Oh, in secure boot mode.  The systemd images don't use shim, so that
most likely isn't going to fly due to bootloader being unsigned.  The
grub2 variants should work.  Never actually tested that though.  

cheers,
  Gerd


  reply	other threads:[~2019-06-05  5:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 11:02 Help needed in building UEFI qcow2 images Pavan Kumar Aravapalli
2019-05-22 11:19 ` Tomas Pilar (tpilar)
2019-05-22 15:58   ` [edk2-devel] " Andrew Fish
2019-05-22 16:57     ` Tomas Pilar (tpilar)
2019-05-22 17:05       ` Andrew Fish
2019-05-22 19:05     ` Laszlo Ersek
2019-05-22 19:10       ` Andrew Fish
2019-05-23 13:45         ` Laszlo Ersek
2019-06-03 19:21   ` Pavan Kumar Aravapalli
2019-06-04 10:49     ` Laszlo Ersek
2019-06-04 11:28       ` Pavan Kumar Aravapalli
2019-06-04 16:10         ` Laszlo Ersek
2019-06-05  5:49           ` Gerd Hoffmann [this message]
2019-06-07  9:13             ` Pavan Kumar Aravapalli
2019-06-05 18:19           ` Pavan Kumar Aravapalli
2019-06-06  7:43             ` Laszlo Ersek

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=20190605054943.so4v63o7c2hqw42r@sirius.home.kraxel.org \
    --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