From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH-SERIES qemu/qemu-server 0/2] generate and ship static list of CPU models with pve-qemu-kvm
Date: Tue, 10 Feb 2026 14:52:27 +0100 [thread overview]
Message-ID: <20260210135417.184127-1-f.ebner@proxmox.com> (raw)
Before, it was often forgotten to pick up new QEMU CPU models and
hard-coding the information in Perl is also not the cleanest way to do
it.
Generate a list of supported models during build of the pve-qemu-kvm
and use that instead. The build will fail when any changes appear, so
they are not missed and can be adapted to.
The qemu-server patch requires the following series by Dominik to be
applied:
https://lore.proxmox.com/pve-devel/20260205141959.3615131-1-d.csapak@proxmox.com/T/
qemu:
Fiona Ebner (1):
generate and ship static list of CPU models
debian/cpu-models-aarch64.json | 1 +
debian/cpu-models-x86_64.json | 1 +
debian/parse-cpu-models.pl | 121 +++++++++++++++++++++++++++++++++
debian/rules | 12 ++++
4 files changed, 135 insertions(+)
create mode 100644 debian/cpu-models-aarch64.json
create mode 100644 debian/cpu-models-x86_64.json
create mode 100755 debian/parse-cpu-models.pl
qemu-server:
Fiona Ebner (1):
cpu config: use static CPU model list shipped by QEMU package if
available
src/PVE/QemuServer/CPUConfig.pm | 237 +++++++++++++++++---------------
1 file changed, 126 insertions(+), 111 deletions(-)
Summary over all repositories:
5 files changed, 261 insertions(+), 111 deletions(-)
--
Generated by git-murpp 0.5.0
next reply other threads:[~2026-02-10 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 13:52 Fiona Ebner [this message]
2026-02-10 13:52 ` [PATCH qemu 1/2] generate and ship static list of CPU models Fiona Ebner
2026-02-11 10:33 ` Thomas Lamprecht
2026-02-11 11:41 ` Fiona Ebner
2026-02-17 18:28 ` applied: " Thomas Lamprecht
2026-02-10 13:52 ` [PATCH qemu-server 2/2] cpu config: use static CPU model list shipped by QEMU package if available 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=20260210135417.184127-1-f.ebner@proxmox.com \
--to=f.ebner@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