Sean Christopherson seanjc@google.com writes:
On Sun, Jul 13, 2025, Nikunj A Dadhania wrote:
Sean Christopherson seanjc@google.com writes:
On Fri, Jul 11, 2025, Nikunj A Dadhania wrote:
Require a minimum GHCB version of 2 when starting SEV-SNP guests through KVM_SEV_INIT2. When a VMM attempts to start an SEV-SNP guest with an incompatible GHCB version (less than 2), reject the request early rather than allowing the guest to start with an incorrect protocol version and fail later.
What happens with ghcb_version==1? I.e. what failure occurs, and when?
SNP guest terminates with following error:
So this probably isn't stable@ worth then? Because I don't see any risk to the kernel, this is ultimately only a problem if the VMM is broken, and the "fix" doesn't provide any meaningful change in functionality (the VM is dead no matter what).
Agree, VM start will fail no matter what, just that it will be early. I will send a v2 with updated change log and dropping the stable@ tag.
Regards, Nikunj