From: "Gerd Hoffmann via groups.io" <kraxel=redhat.com@groups.io>
To: "Aithal, Srikanth" <sraithal@amd.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] edk2 master: AMD guest boot with AmdSevX64 fails
Date: Thu, 23 Jan 2025 13:05:25 +0100 [thread overview]
Message-ID: <eam4m5l5xujsgyhqruemvwx6p2dmxhwvikrutqq57vfg3ee7l6@zqr7xjytebl5> (raw)
In-Reply-To: <11c4ec16-1150-40cf-a365-14edf138ce18@amd.com>
On Wed, Jan 22, 2025 at 06:14:23PM +0530, Aithal, Srikanth wrote:
> Hello,
>
> With current edk2/master booting AMD SEV-ES and SNP guests with AmdSevX64
> package is failing with below error:
> Same test had passed yesterdays master, I did git bisect which points to
> below commit. The commit before this passes the same boot test.
>
> commit 459f5ffa24ae8574657c4105af0ff7dc30ac428d
> Author: Gerd Hoffmann <kraxel@redhat.com>
> Date: Tue Jan 14 17:36:39 2025 +0100
>
> OvmfPkg/QemuKernelLoaderFsDxe: rework direct kernel boot filesystem
[ ... ]
> No (intentional) change in filesystem protocol behavior.
Oops So it did not work out as intended ...
My first guess would be that the VerifyBlob re-arrangements break SEV
boot somehow.
Can you send the complete log for both working and non-working case?
thanks,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#121041): https://edk2.groups.io/g/devel/message/121041
Mute This Topic: https://groups.io/mt/110751667/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2025-01-23 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 12:44 [edk2-devel] edk2 master: AMD guest boot with AmdSevX64 fails Aithal, Srikanth via groups.io
2025-01-23 12:05 ` Gerd Hoffmann 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=eam4m5l5xujsgyhqruemvwx6p2dmxhwvikrutqq57vfg3ee7l6@zqr7xjytebl5 \
--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