From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Markus Frank <m.frank@proxmox.com>
Subject: [pve-devel] applied: [PATCH pve-manager v1] ui: qemu: remove highly experimental text for SEV-ES and SEV-SNP
Date: Mon, 17 Nov 2025 15:52:39 +0100 [thread overview]
Message-ID: <176339115499.3680407.13462084603739623828.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251117102212.102868-1-m.frank@proxmox.com>
On Mon, 17 Nov 2025 11:21:17 +0100, Markus Frank wrote:
> Since the SEV-SNP patch series was applied, both SEV-ES and SEV-SNP have
> functioned correctly on supported hardware, as it added OVMF files
> containing all the necessary features for SEV-ES and SEV-SNP. The highly
> experimental text was included because an SEV-ES VM could not initially
> be started due to missing edk2 firmware features after the initial SEV
> patch series.
>
> [...]
Applied, thanks!
[1/1] ui: qemu: remove highly experimental text for SEV-ES and SEV-SNP
commit: 9f758fc0a7a9d077348e7bb18d27810683e392be
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-17 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 10:21 [pve-devel] " Markus Frank
2025-11-17 14:52 ` Thomas Lamprecht [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=176339115499.3680407.13462084603739623828.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.frank@proxmox.com \
--cc=pve-devel@lists.proxmox.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.