Re: [PATCH 4/4] kvm: svm: Support KVM_SEV_SNP_PAGE_TYPE_VMSA at SNP_LAUNCH_UPDATE

Jörg Rödel <[email protected]> Wed, 17 Jun 2026 08:45:04 +0200
Newsgroups dev.linux.lists.coconut-svsm,org.kernel.vger.kvm,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
On Tue, Jun 16, 2026 at 10:55:28AM -0700, Sean Christopherson wrote:
> Isn't this essentially the same thing as hot-plugging vCPUs after launch?  I
> have yet to review it in depth (sorry Jethro), but it looks a *lot* simpler.

Replacing the VMSA after launch (as supported with the AP_CREATE GHCB call) is
different because this has no influence on the launch measurement.

The point of providing an initial VMSA is to get a predictable launch
measurement which is independent of the number of VCPUs the guest has.

With the current code KVM will create its own VMSA for each created VCPU and
measure it into the guests initial image. This makes predicting the initial
launch measurement difficult (as it depends on KVM internals) and fragile because
KVM-internal changes always carry a risk to change the launch measurement
(which has happened a couple of times already).


-Joerg