public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Crystal Lee via groups.io" <CrystalLee=ami.com@groups.io>
To: "Xu, Min M" <min.m.xu@intel.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Felix Polyudov" <Felixp@ami.com>,
	"David Hsieh (謝坤智)" <DavidHsieh@ami.com>,
	"James Wang (王家明)" <JamesWang@ami.com>,
	"Ni, Ray" <ray.ni@intel.com>,
	"Sun, CepingX" <cepingx.sun@intel.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	"Ard Biesheuvel" <ardb+tianocore@kernel.org>,
	"Ard Biesheuvel" <ardb@kernel.org>
Subject: Re: [edk2-devel] PR#5939 broke the legacy VM bootup
Date: Wed, 15 Jan 2025 03:04:35 +0000	[thread overview]
Message-ID: <DS7PR10MB5278B2E31A1C68AAED3D2D8EDE192@DS7PR10MB5278.namprd10.prod.outlook.com> (raw)
In-Reply-To: <CAMj1kXG8kWeWY-uwRWpgCAjVMZ8z5AoqyF7tNORioe3WMtMzLw@mail.gmail.com>

Hi Min,

We have the same issue with Ubuntu 22.04.04 after loading shim, Ubuntu 22.04.5(using shim 15.8) has fixed the issue.

Thanks,
Crystal
-----Original Message-----
From: Ard Biesheuvel <ardb@kernel.org>
Sent: Tuesday, January 14, 2025 4:35 PM
To: Xu, Min M <min.m.xu@intel.com>
Cc: devel@edk2.groups.io; Crystal Lee (李怡萱) <CrystalLee@ami.com>; Felix Polyudov <Felixp@ami.com>; David Hsieh (謝坤智) <DavidHsieh@ami.com>; James Wang (王家明) <JamesWang@ami.com>; Ni, Ray <ray.ni@intel.com>; Sun, CepingX <cepingx.sun@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>; Gerd Hoffmann <kraxel@redhat.com>; Tom Lendacky <thomas.lendacky@amd.com>; Ard Biesheuvel <ardb+tianocore@kernel.org>.
Subject: [EXTERNAL] Re: PR#5939 broke the legacy VM bootup


**CAUTION: The e-mail below is from an external source. Please exercise caution before opening attachments, clicking links, or following guidance.**

On Tue, 14 Jan 2025 at 09:31, Xu, Min M <min.m.xu@intel.com> wrote:
>
> On Tuesday, January 14, 2025 4:22 PM, Ard Biesheuvel wrote:
> >
> > On Tue, 14 Jan 2025 at 03:54, Xu, Min M <min.m.xu@intel.com> wrote:
> > >
> > > Hi, Crystal
> > >
> > > PR#5939
> > > (https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%252
> > > Fgithub.com%2Ftianocore%2Fedk2%2Fpull%2F5939&data=05%7C02%7Ccrysta
> > > llee%40ami.com%7C953a53f4b7ed44f018c008dd34766aab%7C27e97857e15f48
> > > 6cb58e86c2b3040f93%7C1%7C0%7C638724405414190413%7CUnknown%7CTWFpbG
> > > Zsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIs
> > > IkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=FQomYihkLvcY9d
> > > jL%2BQmI0by2vmbQkDfodjny3MOexVY%3D&reserved=0) was merged
> > > yesterday
> > but it seems it broke the legacy VM bootup.
> > >
> > >
> > >
> > > Below is the crash log of the failure.
> > >
> >
> > I take it this crash occurs after loading shim?
>
> That's right. It seems in the EDK2 CI, there are only cases of "run to shell". So it is not triggered in CI test.
>

This is a long standing bug in shim, that has been fixed 2 years ago [0] but the distros keep shipping outdated versions, due to the reluctance of MS to sign new shim builds.

The solutions are:
- disable the EFI memory attributes protocol altogether.
- ignore the distros so they are forced to clean up their mess.



[0] https://github.com/rhboot/shim/commit/c7b305152802c8db688605654f75e1195def9fd6
-The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121025): https://edk2.groups.io/g/devel/message/121025
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]
-=-=-=-=-=-=-=-=-=-=-=-



      parent reply	other threads:[~2025-01-15 18:54 UTC|newest]

Thread overview: 6+ 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-01-15  3:04       ` Crystal Lee via groups.io [this message]

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=DS7PR10MB5278B2E31A1C68AAED3D2D8EDE192@DS7PR10MB5278.namprd10.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