From: Markus Frank <m.frank@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server/docs/manager v11 0/5] AMD SEV
Date: Wed, 29 May 2024 14:23:43 +0200 [thread overview]
Message-ID: <20240529122348.1267369-1-m.frank@proxmox.com> (raw)
Patch series to enable AMD Secure Encrypted Virtualization (SEV)
https://www.amd.com/en/developer/sev.html
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
changes v10:
* removed include of sys/types.h in C Program
* also die if the BIOS is not set, since the default is SeaBIOS
* added pve-manager patch
apply/compile order:
1. qemu-server: add C program to get hardware capabilities from CPUID
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):
add C program to get hardware capabilities from CPUID
config: add AMD SEV support
migration: add check_non_migratable_resources function
Makefile | 1 +
PVE/API2/Qemu.pm | 5 +-
PVE/QemuMigrate.pm | 2 +-
PVE/QemuServer.pm | 36 +++++++-
PVE/QemuServer/CPUConfig.pm | 83 ++++++++++++++++++-
query-machine-capabilities/Makefile | 18 ++++
.../query-machine-capabilities.c | 79 ++++++++++++++++++
7 files changed, 219 insertions(+), 5 deletions(-)
create mode 100644 query-machine-capabilities/Makefile
create mode 100644 query-machine-capabilities/query-machine-capabilities.c
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
--
2.39.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-05-29 12:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-29 12:23 Markus Frank [this message]
2024-05-29 12:23 ` [pve-devel] [PATCH qemu-server v11 1/5] add C program to get hardware capabilities from CPUID Markus Frank
2024-07-24 13:05 ` Fiona Ebner
2024-05-29 12:23 ` [pve-devel] [PATCH qemu-server v11 2/5] config: add AMD SEV support Markus Frank
2024-07-24 13:05 ` Fiona Ebner
2024-05-29 12:23 ` [pve-devel] [PATCH qemu-server v11 3/5] migration: add check_non_migratable_resources function Markus Frank
2024-07-24 13:05 ` Fiona Ebner
2024-05-29 12:23 ` [pve-devel] [PATCH docs v11 4/5] add AMD SEV documentation Markus Frank
2024-05-29 12:23 ` [pve-devel] [PATCH manager v11 5/5] ui: add AMD SEV configuration to Options Markus Frank
2024-07-23 8:11 ` [pve-devel] [PATCH qemu-server/docs/manager v11 0/5] AMD SEV Markus Frank
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=20240529122348.1267369-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