From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 0581A1FF141 for ; Tue, 19 May 2026 16:06:45 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B98D8890B; Tue, 19 May 2026 16:06:30 +0200 (CEST) From: Arthur Bied-Charreton 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 Message-ID: <20260519140623.594472-1-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.135 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: VKUNUGQFQFDVKTHC454R3GULDMSRCGK6 X-Message-ID-Hash: VKUNUGQFQFDVKTHC454R3GULDMSRCGK6 X-MailFrom: abied-charreton@jett.proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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