From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Markus Frank <m.frank@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH qemu-server/docs/manager v13 0/5] AMD SEV
Date: Mon, 18 Nov 2024 22:16:54 +0100 [thread overview]
Message-ID: <e5de8455-57e1-42af-ac63-b38dd315180c@proxmox.com> (raw)
In-Reply-To: <20241118111700.110077-1-m.frank@proxmox.com>
Am 18.11.24 um 12:16 schrieb Markus Frank:
> changes v13:
> * renamed amd_sev to amd-sev
> * removed already applied patches
> * add systemd service file for query-machine-capabilities
> * removed now unused $efidisk0 parameter from the get_amd_sev_object
> function
>
> changes v12:
> * new pve-guest-common patch
> * improved error handling in C
> * small perl style changes
>
> changes v11:
> * removed systemd service and added run_command in qemu-server instead
> * moved SEV related code to CPUConfig
> * instead of the no-debug and no-key-sharing checkboxes there are no
> "allow debug/key-sharing" checkboxes in the WebUI with true beeing
> the default.
> * add check_non_migratable_resources function in qemu-server
>
>
> apply/compile order:
> * pve-guest-common: AbstractConfig: add abstract method to check for
> resources preventing a snapshot -> already applied
> * qemu-server: add C program to get hardware capabilities from CPUID
> -> already applied
> 1. qemu-server: query-machine-capabilities: add systemd service file
> -> new to v13
> 2. qemu-server: config: add AMD SEV support
> 3. qemu-server: migration: add check_non_migratable_resources function
> 4. pve-docs: add AMD SEV documentation
> 5. pve-manager: ui: add AMD SEV configuration to Options
>
>
> qemu-server:
>
> Markus Frank (3):
> query-machine-capabilities: add systemd service file
> config: add AMD SEV support
> migration: add check_non_migratable_resources function
>
> PVE/API2/Qemu.pm | 5 +-
> PVE/QemuConfig.pm | 5 ++
> PVE/QemuMigrate.pm | 2 +-
> PVE/QemuServer.pm | 36 +++++++-
> PVE/QemuServer/CPUConfig.pm | 87 ++++++++++++++++++-
> query-machine-capabilities/Makefile | 2 +
> .../query-machine-capabilities.service | 13 +++
> 7 files changed, 145 insertions(+), 5 deletions(-)
> create mode 100644 query-machine-capabilities/query-machine-capabilities.service
>
>
> docs:
>
> Markus Frank (1):
> add AMD SEV documentation
>
> qm.adoc | 103 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 103 insertions(+)
>
>
>
> manager:
>
> Markus Frank (1):
> ui: add AMD SEV configuration to Options
>
> www/manager6/Makefile | 1 +
> www/manager6/qemu/Options.js | 11 ++++
> www/manager6/qemu/SevEdit.js | 121 +++++++++++++++++++++++++++++++++++
> 3 files changed, 133 insertions(+)
> create mode 100644 www/manager6/qemu/SevEdit.js
>
applied series, with some minor nits from Shannon and me fixed directly or as
follow-up, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-18 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 11:16 [pve-devel] " Markus Frank
2024-11-18 11:16 ` [pve-devel] [PATCH qemu-server v13 1/5] query-machine-capabilities: add systemd service file Markus Frank
2024-11-18 11:16 ` [pve-devel] [PATCH qemu-server v13 2/5] config: add AMD SEV support Markus Frank
2024-11-18 11:16 ` [pve-devel] [PATCH qemu-server v13 3/5] migration: add check_non_migratable_resources function Markus Frank
2024-11-18 11:16 ` [pve-devel] [PATCH docs v13 4/5] add AMD SEV documentation Markus Frank
2024-11-18 14:34 ` Shannon Sterz
2024-11-18 11:17 ` [pve-devel] [PATCH manager v13 5/5] ui: add AMD SEV configuration to Options Markus Frank
2024-11-18 14:38 ` Shannon Sterz
2024-11-18 21:16 ` 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=e5de8455-57e1-42af-ac63-b38dd315180c@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox