From: "Min Xu via groups.io" <min.m.xu=intel.com@groups.io>
To: Ard Biesheuvel <ardb@kernel.org>,
Gerd Hoffmann <kraxel@redhat.com>,
"Qiang, Chenyi" <chenyi.qiang@intel.com>
Cc: Fiona Ebner <f.ebner@proxmox.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"crystallee@ami.com" <crystallee@ami.com>,
"POLUDOV, FELIX" <felixp@ami.com>,
"davidhsieh@ami.com" <davidhsieh@ami.com>,
"jameswang@ami.com" <jameswang@ami.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Sun, CepingX" <cepingx.sun@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Tom Lendacky" <thomas.lendacky@amd.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
"Xu, Min M" <min.m.xu@intel.com>
Subject: Re: [edk2-devel] PR#5939 broke the legacy VM bootup
Date: Tue, 25 Mar 2025 08:10:58 +0000 [thread overview]
Message-ID: <PH0PR11MB5064D00492F3575F46F5163EC5A72@PH0PR11MB5064.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAMj1kXHUiQsSqcEa7CrutwVT-J=NXneJtMM+avbeSZd=0jK-Mg@mail.gmail.com>
Hi, Gerd
We tried to fix this issue based on your suggested workaround (at Jan 14) but it still hang.
Did we miss something?
@Qiang, Chenyi Can provide more information.
>Workaround for centos stream 9:
> (1) turn off secure boot (if enabled)
> (2) install latest shim (unsigned):
> sudo dnf install shim-unsigned-x64
> (3) replace shim on the ESP:
> sudo cp /usr/share/shim/15.8-2.el9/x64/shimx64.efi /boot/efi/EFI/centos/shimx64.efi
> -----Original Message-----
> From: Ard Biesheuvel <ardb@kernel.org>
> Sent: Tuesday, March 25, 2025 3:48 PM
> To: Gerd Hoffmann <kraxel@redhat.com>
> Cc: Fiona Ebner <f.ebner@proxmox.com>; devel@edk2.groups.io; Xu, Min M
> <min.m.xu@intel.com>; crystallee@ami.com; POLUDOV, FELIX
> <felixp@ami.com>; davidhsieh@ami.com; jameswang@ami.com; Ni, Ray
> <ray.ni@intel.com>; Sun, CepingX <cepingx.sun@intel.com>; Yao, Jiewen
> <jiewen.yao@intel.com>; Tom Lendacky <thomas.lendacky@amd.com>; Ard
> Biesheuvel <ardb+tianocore@kernel.org>
> Subject: Re: [edk2-devel] PR#5939 broke the legacy VM bootup
>
> On Mon, 24 Mar 2025 at 18:27, Gerd Hoffmann <kraxel@redhat.com> wrote:
> >
> > Hi,
> >
> > > > The solutions are:
> > > > - disable the EFI memory attributes protocol altogether.
> > >
> > > Is this possible via a build macro/flag? Or alternatively via the
> > > QEMU commandline/fw_cfg?
> >
> > fedora builds are using this downstream:
> > https://github.com/tianocore/edk2/pull/10667
> >
> > > > - ignore the distros so they are forced to clean up their mess.
> > >
> > > Is this the solution the EDK2 project opted for/status quo?
> >
> > It's the status quo.
> >
>
> Note that EDK2 is the reference implementation of UEFI. OVMF is an outlier
> because it is used in production almost unmodified, but in the general case,
> the reference implementation is used as the basis for production platforms
> shipping in the future. Therefore, it is not the place to put hacks to work
> around nasty issues that the downstream users cannot be bothered to
> address.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121220): https://edk2.groups.io/g/devel/message/121220
Mute This Topic: https://groups.io/mt/110601533/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2025-03-25 8:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 2:54 [edk2-devel] PR#5939 broke the legacy VM bootup Min Xu via groups.io
2025-01-14 8:21 ` Ard Biesheuvel via groups.io
2025-01-14 8:30 ` Min Xu via groups.io
2025-01-14 8:35 ` Ard Biesheuvel via groups.io
2025-01-14 13:02 ` Gerd Hoffmann via groups.io
2025-03-13 2:22 ` Chenyi Qiang via groups.io
2025-01-15 3:04 ` Crystal Lee via groups.io
2025-03-24 15:55 ` Fiona Ebner
2025-03-24 17:27 ` Gerd Hoffmann via groups.io
2025-03-25 7:48 ` Ard Biesheuvel via groups.io
2025-03-25 8:10 ` Min Xu via groups.io [this message]
2025-03-26 13:28 ` Gerd Hoffmann via groups.io
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=PH0PR11MB5064D00492F3575F46F5163EC5A72@PH0PR11MB5064.namprd11.prod.outlook.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