[ANNOUNCE] QEMU 10.1.0 is now available

[ANNOUNCE] QEMU 10.1.0 is now available

[Michael Roth]

Hello,

On behalf of the QEMU Team, I'd like to announce the availability of
the QEMU 10.1.0 release. This release contains 2700+ commits from 226
authors.

You can grab the tarball from our download page here:

  https://www.qemu.org/download/#source

The full list of changes are available at:

  https://wiki.qemu.org/ChangeLog/10.1

Highlights include:

 * VFIO: Initial support for accessing/mapping memory for confidential
   guests when guest_memfd is being utilized, allowing passthrough support
   for virtual machines running under SEV-SNP/TDX
 * Live migration: support for utilizing multifd to accelerate post-copy
   migration, optimizations for pre-copy migration, and RDMA migration
   support for ipv6
 * QEMU guest agent: support for querying load of virtual machines
   running Windows via new 'guest-get-load' command

 * ARM: support for CPU features FEAT_SME2, FEAT_SME2p1, FEAT_SME_B16B16,
   FEAT_SME_F16F16, FEAT_SVE_B16B16, and FEAT_SVE2p1
 * ARM: support for new board/machine models 'max78000fthr',
   'ast2700fc', 'catalina-bmc', 'gb200-bmc', and 'ast2700a0-evb'
 * ARM: 'virt' board now supports nested virtualization under KVM, CXL,
   and ACPI-based PCI hotplug
 * LoongArch: support for in-kernel irqchip
 * Microblaze: support for selecting the endianess of 'petalogix_s3adsp1800'
   machine type
 * RISC-V: ISA/extension support for atomic instruction fetch (Ziccif),
   'Svrsw60t59b', and numerous other improvements/additions/fixes
 * RISC-V: support for Kunminghu CPU and platform
 * x86: KVM support for running confidential guests via Intel TDX
 * x86: Support for initializing confidential TDX or SEV-SNP virtual
   machines using the IGVM file format

 * and lots more...

Thank you to everyone involved!

Re: [ANNOUNCE] QEMU 10.1.0 is now available

[Xiaoyao Li]

On 8/27/2025 7:19 AM, Michael Roth wrote:
>   * x86: Support for initializing confidential TDX or SEV-SNP virtual
>     machines using the IGVM file format

Can IGVM really work for TDX?

Re: [ANNOUNCE] QEMU 10.1.0 is now available

[Daniel P. Berrangé]

On Wed, Aug 27, 2025 at 09:40:29AM +0800, Xiaoyao Li wrote:
> On 8/27/2025 7:19 AM, Michael Roth wrote:
> >   * x86: Support for initializing confidential TDX or SEV-SNP virtual
> >     machines using the IGVM file format
> 
> Can IGVM really work for TDX?

I doubt it. Early versions of the IGVM patches had some TDX code in them,
but this was all removed since QEMU lacked TDX support, and I don't see
any TDX references re-added to the IGVM code in QEMU that was merged.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

Re: [ANNOUNCE] QEMU 10.1.0 is now available

[Michael Roth via]

On Wed, Aug 27, 2025 at 11:06:15AM +0100, Daniel P. Berrangé wrote:
> On Wed, Aug 27, 2025 at 09:40:29AM +0800, Xiaoyao Li wrote:
> > On 8/27/2025 7:19 AM, Michael Roth wrote:
> > >   * x86: Support for initializing confidential TDX or SEV-SNP virtual
> > >     machines using the IGVM file format
> > 
> > Can IGVM really work for TDX?
> 
> I doubt it. Early versions of the IGVM patches had some TDX code in them,
> but this was all removed since QEMU lacked TDX support, and I don't see
> any TDX references re-added to the IGVM code in QEMU that was merged.

That's unfortunate. I'd pulled that from https://wiki.qemu.org/ChangeLog/10.1
but looking through the code I indeed only see SEV enablement, so maybe that
changelog entry was out of sync with what actually went upstream.

The ship has sailed on the announcement email obviously but I'll fix it up in
the blog post at least.

-Mike

> 
> With regards,
> Daniel
> -- 
> |: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org         -o-            https://fstop138.berrange.com :|
> |: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
>