From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Zhao Liu" <zhao1.liu@intel.com>,
"Eric Blake" <eblake@redhat.com>,
roy.hopkins@randomman.co.uk
Subject: Re: [PATCH] igvm: add initial support for non-cc firmware in igvm format
Date: Wed, 9 Jul 2025 15:34:20 +0200 [thread overview]
Message-ID: <1c4e3024-3ba4-4ab6-a8ce-f5ab24ffe1d4@linaro.org> (raw)
In-Reply-To: <20250709123007.1039675-1-kraxel@redhat.com>
Hi Gerd,
On 9/7/25 14:30, Gerd Hoffmann wrote:
> Implement a ConfidentialGuestSupportClass for non-confidential VMs.
> This allows the igvm support code work without sev/tdx.
Is this something we only want in non-KVM builds due to security
boundary concerns?
>
> RfC: Not fully sure this is the best way to implement this.
> Alternatively we could add this directly into the igvm backend and run
> it in case no confidential guest support object is present.
>
> TODO: Implement proper reset.
> - re-initialize memory regions from igvm file content.
> - load initial register state (if present).
>
> Usage:
> qemu-system-x86_64 \
> -object nocc,id=nocc0 \
> -machine confidential-guest-support=nocc0
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> target/i386/nocc.c | 283 ++++++++++++++++++++++++++++++++++++++++
> qapi/qom.json | 1 +
> target/i386/meson.build | 1 +
> 3 files changed, 285 insertions(+)
> create mode 100644 target/i386/nocc.c
next prev parent reply other threads:[~2025-07-09 13:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 12:30 [PATCH] igvm: add initial support for non-cc firmware in igvm format Gerd Hoffmann
2025-07-09 13:34 ` Philippe Mathieu-Daudé [this message]
2025-07-09 14:22 ` Gerd Hoffmann
2025-09-12 13:25 ` Gerd Hoffmann
2025-09-12 13:29 ` Daniel P. Berrangé
2025-09-15 6:52 ` Gerd Hoffmann
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=1c4e3024-3ba4-4ab6-a8ce-f5ab24ffe1d4@linaro.org \
--to=philmd@linaro.org \
--cc=anisinha@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roy.hopkins@randomman.co.uk \
--cc=zhao1.liu@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).