From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: "Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Vikrant Garg" <vikrant1garg@gmail.com>
Subject: Re: [PATCH] x86/loader: Don't update kernel header for CoCo VMs
Date: Thu, 14 Aug 2025 12:28:33 +0200 [thread overview]
Message-ID: <b1093581-fb6d-4e4a-bcac-da9793f3df77@redhat.com> (raw)
In-Reply-To: <20250814092111.2353598-1-xiaoyao.li@intel.com>
On 8/14/25 11:21, Xiaoyao Li wrote:
> Update the header makes it different from the original kernel that user
> provides via "-kernel", which leads to a different hash and breaks the
> attestation, e.g., for TDX.
>
> We already skip it for SEV VMs. Instead of adding another check of
> is_tdx_vm() to cover the TDX case, check machine->cgs to cover all the
> confidential computing case for x86.
>
> Reported-by: Vikrant Garg <vikrant1garg@gmail.com>
> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
Applied for 10.2, thanks!
Paolo
> hw/i386/x86-common.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/i386/x86-common.c b/hw/i386/x86-common.c
> index b1b5f11e7396..7512be64d67b 100644
> --- a/hw/i386/x86-common.c
> +++ b/hw/i386/x86-common.c
> @@ -952,7 +952,7 @@ void x86_load_linux(X86MachineState *x86ms,
> * kernel on the other side of the fw_cfg interface matches the hash of the
> * file the user passed in.
> */
> - if (!sev_enabled() && protocol > 0) {
> + if (!MACHINE(x86ms)->cgs && protocol > 0) {
> memcpy(setup, header, MIN(sizeof(header), setup_size));
> }
>
prev parent reply other threads:[~2025-08-14 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 9:21 [PATCH] x86/loader: Don't update kernel header for CoCo VMs Xiaoyao Li
2025-08-14 10:28 ` Paolo Bonzini [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-all 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=b1093581-fb6d-4e4a-bcac-da9793f3df77@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vikrant1garg@gmail.com \
--cc=xiaoyao.li@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).