From: "Jörg Rödel" <joro@8bytes.org>
To: coconut-svsm@lists.linux.dev
Subject: SVSM Linux and QEMU host branches updated
Date: Thu, 17 Sep 2026 13:50:35 +0200 [thread overview]
Message-ID: <aqvQzI_5GRTjzkG3@8bytes.org> (raw)
Hi all,
As announced in the development call, I have updated the SVSM host branches for
Linux/KVM and QEMU to the Linux v7.2-based branches. The new QEMU branch is
based on QEMU v11.1.0.
Both repositories have the updated code in the `svsm` branch. On the Linux/KVM
side there have been some updates to the v7.1-based code:
- Support for KVMs in-kernel IOAPIC with KVM planes.
- Support for PCI device assignment with KVM planes.
- Updated version of direct vmsa-setting support in KVM. This includes
a user-space ABI change.
Both branches need to be used together because the kernel/user interface for
KVM planes has changed. The new QEMU branch contains:
- A new version of the QEMU Planes patches, completely rewritten so
that QEMU now maintains QOM-representations of KVM plane state.
- Updated QEMU support for direct-vmsa setting.
- QEMU now ignores IGVM command line directives.
As of now, running COCONUT-SVSM on these new branches will cause
launch-measurment mismatches on SEV-SNP. This is a know issue and will be fixed
by SVSM PR #1209. But since this PR makes the SVSM incompatible with any
previous host-side branches (including the v7.1 ones), everyone will get a week
to update their host environments before #1209 gets merged.
So please everyone go forth and update your host environments for SVSM testing
and development. If you experience any issues besides the unexpected launch
measurements, please shout out so that I can fix it.
Thanks,
Joerg
reply other threads:[~2026-09-17 11:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aqvQzI_5GRTjzkG3@8bytes.org \
--to=joro@8bytes.org \
--cc=coconut-svsm@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.