From: Markus Frank <m.frank@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-manager v1] ui: qemu: remove highly experimental text for SEV-ES and SEV-SNP
Date: Mon, 17 Nov 2025 11:21:17 +0100 [thread overview]
Message-ID: <20251117102212.102868-1-m.frank@proxmox.com> (raw)
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.
Signed-off-by: Markus Frank <m.frank@proxmox.com>
---
www/manager6/qemu/SevEdit.js | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/www/manager6/qemu/SevEdit.js b/www/manager6/qemu/SevEdit.js
index dfc4a19c..44db34bd 100644
--- a/www/manager6/qemu/SevEdit.js
+++ b/www/manager6/qemu/SevEdit.js
@@ -61,8 +61,8 @@ Ext.define('PVE.qemu.SevInputPanel', {
Proxmox.Utils.defaultText + ' (' + Proxmox.Utils.disabledText + ')',
],
['std', 'AMD SEV'],
- ['es', 'AMD SEV-ES (highly experimental)'],
- ['snp', 'AMD SEV-SNP (highly experimental)'],
+ ['es', 'AMD SEV-ES'],
+ ['snp', 'AMD SEV-SNP'],
],
bind: {
value: '{type}',
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-11-17 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 10:21 Markus Frank [this message]
2025-11-17 14:52 ` [pve-devel] applied: " Thomas Lamprecht
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=20251117102212.102868-1-m.frank@proxmox.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox