All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Roth via <qemu-devel@nongnu.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Xiaoyao Li <xiaoyao.li@intel.com>, <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [ANNOUNCE] QEMU 10.1.0 is now available
Date: Wed, 27 Aug 2025 10:45:35 -0500	[thread overview]
Message-ID: <20250827154535.sqeanvqc4bz3ccf5@amd.com> (raw)
In-Reply-To: <aK7Yl4c9ARijYz0S@redhat.com>

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 :|
> 


      reply	other threads:[~2025-08-27 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26 23:19 [ANNOUNCE] QEMU 10.1.0 is now available Michael Roth
2025-08-27  1:40 ` Xiaoyao Li
2025-08-27 10:06   ` Daniel P. Berrangé
2025-08-27 15:45     ` Michael Roth via [this message]

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=20250827154535.sqeanvqc4bz3ccf5@amd.com \
    --to=qemu-devel@nongnu.org \
    --cc=berrange@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=stefanha@redhat.com \
    --cc=xiaoyao.li@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 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.