public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Philipp Giersfeld <philipp.giersfeld@canarybit.eu>
Subject: [pve-devel] applied: [PATCH qemu-server v5 3/4] config: add AMD SEV-SNP support.
Date: Thu, 3 Apr 2025 21:46:08 +0200	[thread overview]
Message-ID: <32a7204d-bc17-4fff-a30e-8cf47dc91f0f@proxmox.com> (raw)
In-Reply-To: <20250331135931.50568-4-philipp.giersfeld@canarybit.eu>

Am 31.03.25 um 15:59 schrieb Philipp Giersfeld:
> This patch is for enabling AMD SEV-SNP support.
> 
> Where applicable, it extends support for existing SEV(-ES) variables
> to SEV-SNP. This means that it retains no-debug and kernel-hashes
> options, but the no-key-sharing option is removed.
> 
> The default policy value is identical to QEMU’s, and the therefore
> required option has been added to configure SMT support.
> 
> The code was tested by running a VM without SEV, with SEV, SEV-ES,
> SEV-SNP. Each configuration was tested with and without an EFI disk
> attached. For SEV-enabled configurations it was also verified that the
> kernel actually used the respective feature.
> 
> Signed-off-by: Philipp Giersfeld <philipp.giersfeld@canarybit.eu>
> Tested-by: Markus Frank <m.frank@proxmox.com>
> ---
>   
>  no changes since last version
> 
>  PVE/API2/Qemu.pm            |  7 +++-
>  PVE/QemuServer.pm           | 52 +++++++++++++++++++++--------
>  PVE/QemuServer/CPUConfig.pm | 66 ++++++++++++++++++++++++++++---------
>  3 files changed, 95 insertions(+), 30 deletions(-)
> 
>

applied, thanks!

Did some smaller (code) style clean-ups as follow-up and added some very
basic config to command (cfg2cmd) tests to have a bit more coverage here.


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2025-04-03 19:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-31 13:59 [pve-devel] [PATCH edk2-firmware/qemu-server/manager v5 0/4] AMD SEV-SNP Philipp Giersfeld
2025-03-31 13:59 ` [pve-devel] [PATCH edk2-firmware v5 1/4] Add OVMF targets for AMD SEV-ES and SEV-SNP Philipp Giersfeld
2025-04-03 16:43   ` [pve-devel] applied: " Thomas Lamprecht
2025-03-31 13:59 ` [pve-devel] [PATCH qemu-server v5 2/4] Convert policy calculation Philipp Giersfeld
2025-04-03 19:45   ` [pve-devel] applied: " Thomas Lamprecht
2025-03-31 13:59 ` [pve-devel] [PATCH qemu-server v5 3/4] config: add AMD SEV-SNP support Philipp Giersfeld
2025-04-03 19:46   ` Thomas Lamprecht [this message]
2025-03-31 13:59 ` [pve-devel] [PATCH pve-manager v5 4/4] Add configuration options for AMD SEV-SNP Philipp Giersfeld
2025-04-02 10:15   ` Markus Frank
2025-04-04 16:46   ` [pve-devel] applied: " Thomas Lamprecht
2025-04-02 15:49 ` [pve-devel] [PATCH edk2-firmware/qemu-server/manager v5 0/4] " Daniel Kral

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=32a7204d-bc17-4fff-a30e-8cf47dc91f0f@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=philipp.giersfeld@canarybit.eu \
    --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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal