Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Luigi Leonardi <leonardi@redhat.com>
Cc: "Stefano Garzarella" <sgarzare@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Ani Sinha" <anisinha@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Marcelo Tosatti" <mtosatti@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [PATCH 4/4] igvm/sev: forward the IGVM guest policy to the platform before launch
Date: Fri, 4 Sep 2026 07:45:29 +0200	[thread overview]
Message-ID: <appYz1617QTPH-Qf@ghoffman-na.rmtde.csb> (raw)
In-Reply-To: <apl3wnsHORCNP4k-@leonardi-redhat>

  Hi,

> > > If the user choose to override policy on the CLI, isn't it now just
> > > their problem to also figure out what the new expected measurement
> > > will be ?
> > > 
> > > Why wouldn't we just honour the IGVM by default, and if the CLI
> > > has further customizations let them override the IGVM, and leave
> > > the user to figure out the implications.
> > 
> > I also slightly prefer this behaviour too, I see some advantages,
> > especially for testing and debugging, where you don't want to regenerate
> > the IGVM. But I don't have a strong opinion on this; if there is a
> > mismatch, though, I agree that it's better to get an error than to
> > ignore the CLI.
> 
> In this series, if there is a mismatch between IGVM and CLI, QEMU returns an error.
> Debugging sounds very reasonable to me, so I'm fine on letting the CLI override IGVM.

qemu should flag this mismatch in any case.  Either throw an error and
exit, or log a warning and continue.  Given that changing the policy
changes the launch measurement I'd tend to prefer an error.  If people
see value and real use cases for policy overrides I'm fine with a
warning too.

Silently accepting the override is IMHO not an option.  We had enough
problems with qemu silently doing things not expected by users in the
past.

take care,
  Gerd


  reply	other threads:[~2026-09-04  5:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 10:09 [PATCH 0/4] igvm/sev: apply the IGVM guest policy before launch Luigi Leonardi
2026-09-01 10:09 ` [PATCH 1/4] sev: rename set_guest_policy to set_id_block and remove dead policy code Luigi Leonardi
2026-09-03  8:47   ` Ani Sinha
2026-09-03 10:32   ` Stefano Garzarella
2026-09-03 10:47     ` Luigi Leonardi
2026-09-03 13:55       ` Stefano Garzarella
2026-09-04  5:29         ` Gerd Hoffmann
2026-09-01 10:09 ` [PATCH 2/4] igvm: move set_id_block call into the SNP ID block directive handler Luigi Leonardi
2026-09-03 12:57   ` Stefano Garzarella
2026-09-03 13:29     ` Luigi Leonardi
2026-09-03 15:53       ` Stefano Garzarella
2026-09-01 10:09 ` [PATCH 3/4] i386/sev: convert the guest policy properties to custom accessors Luigi Leonardi
2026-09-03  8:46   ` Ani Sinha
2026-09-01 10:09 ` [PATCH 4/4] igvm/sev: forward the IGVM guest policy to the platform before launch Luigi Leonardi
2026-09-03  8:46   ` Ani Sinha
2026-09-03  9:01     ` Luigi Leonardi
2026-09-03 10:03       ` Ani Sinha
2026-09-03 11:02         ` Luigi Leonardi
2026-09-03 11:34           ` Ani Sinha
2026-09-03 11:50           ` Daniel P. Berrangé
2026-09-03 13:28             ` Stefano Garzarella
2026-09-03 13:40               ` Luigi Leonardi
2026-09-04  5:45                 ` Gerd Hoffmann [this message]
2026-09-03 13:14   ` Stefano Garzarella

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=appYz1617QTPH-Qf@ghoffman-na.rmtde.csb \
    --to=kraxel@redhat.com \
    --cc=anisinha@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=leonardi@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --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