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 A378A1FF136 for ; Mon, 18 May 2026 10:03:43 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2A17B54B5; Mon, 18 May 2026 10:03:41 +0200 (CEST) Date: Mon, 18 May 2026 10:03:05 +0200 From: Arthur Bied-Charreton To: Thomas Lamprecht Subject: Re: [PATCH manager/qemu-server v6 00/21] Add API and UI for custom CPU models Message-ID: References: <20260518064526.117067-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779091375040 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.620 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 POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: ZUQD3E5QX6L6QDOTM57MAS3J6UULUDON X-Message-ID-Hash: ZUQD3E5QX6L6QDOTM57MAS3J6UULUDON X-MailFrom: a.bied-charreton@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 CC: pve-devel@lists.proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, May 18, 2026 at 10:00:25AM +0200, Thomas Lamprecht wrote: > Am 18.05.26 um 08:47 schrieb Arthur Bied-Charreton: > > > > Changes since v5 (thanks @Max): > > > > qemu-server: > > - Add 'builtin' flag to models returned by > > /nodes/{node}/capabilities/qemu/cpu > > > > pve-manager: > > - Filter builtin models out of the CPU model selector > > Thanks for this, but FYI: I tested this a bit more over the weekend and > have a v5 with follow-ups ready here, will push it out soon. It includes > something like this, but doesn't calls it built-in, because those are not > built-in CPU models, especially not more than the actual existing vendor > one (like e.g. SkyLake, which are even "more" builtin). Rather, these > are abstract CPU profiles that define a base CPU feature (flag) set, so I > used "abstract". Makes sense, I just used builtin because that was the terminology used in qemu-server, but abstract makes more sense to me as well. > > Anyway, I'll send out a full list of changes in my v5 reply soon, please > take a look at them yourself then. Will do, thanks!