From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager/qemu-server 0/3] custom cpu models: tighten reported-model handling
Date: Tue, 19 May 2026 16:06:20 +0200 [thread overview]
Message-ID: <20260519140623.594472-1-a.bied-charreton@proxmox.com> (raw)
The default reported-model for custom CPU models is kvm64, a legacy
model with a limited set of features.
This series tightens the handling around reported-model:
1. Require reported-model on creation via the API, as the UI already
does
2. Prevent deletion of reported-model via PUT
3. Resolve and write out the default explicitly on config writes
This will be useful in case we ever want to make reported-model
required in a future major release.
pve-manager:
Arthur Bied-Charreton (2):
custom cpu models: make 'reported-model' required in POST
custom cpu models: do not allow deleting 'reported-model'
PVE/API2/Cluster/Qemu/CustomCPUModels.pm | 5 +++++
test/CustomCPUModels_test.pl | 19 +++++++++++++------
2 files changed, 18 insertions(+), 6 deletions(-)
qemu-server:
Arthur Bied-Charreton (1):
cpu config: resolve default reported-model on write
src/PVE/QemuServer/CPUConfig.pm | 2 ++
1 file changed, 2 insertions(+)
Summary over all repositories:
3 files changed, 20 insertions(+), 6 deletions(-)
--
Generated by murpp 0.11.0
next reply other threads:[~2026-05-19 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 14:06 Arthur Bied-Charreton [this message]
2026-05-19 14:06 ` [PATCH pve-manager 1/3] custom cpu models: make 'reported-model' required in POST Arthur Bied-Charreton
2026-05-19 14:06 ` [PATCH pve-manager 2/3] custom cpu models: do not allow deleting 'reported-model' Arthur Bied-Charreton
2026-05-19 14:06 ` [PATCH qemu-server 3/3] cpu config: resolve default reported-model on write Arthur Bied-Charreton
2026-05-19 14:50 ` [PATCH manager/qemu-server 0/3] custom cpu models: tighten reported-model handling Fiona Ebner
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=20260519140623.594472-1-a.bied-charreton@proxmox.com \
--to=a.bied-charreton@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