From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 6D7521FF13A for ; Wed, 01 Apr 2026 10:02:55 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 42D2E12A53; Wed, 1 Apr 2026 10:01:15 +0200 (CEST) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com Subject: [PATCH pve-manager v2 11/17] ui: CPUModelSelector: Allow filtering out custom models Date: Wed, 1 Apr 2026 10:00:22 +0200 Message-ID: <20260401080028.62513-12-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260401080028.62513-1-a.bied-charreton@proxmox.com> References: <20260401080028.62513-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.119 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: J5FKWDWKEVNP4BTNCAQFYUWFLWI7M32R X-Message-ID-Hash: J5FKWDWKEVNP4BTNCAQFYUWFLWI7M32R 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: Add 'showCustomModels' configuration parameter. When set to false, only default CPU models will be shown. This is needed when using the CPUModelSelector in the context of creating a new custom CPU model, where we do not want to allow the reported-model being another custom CPU model. Based on patch by Stefan Reiter, with allowCustom renamed to showCustomModels: https://lore.proxmox.com/pve-devel/20211028114150.3245864-8-s.reiter@proxmox.com/ Signed-off-by: Arthur Bied-Charreton --- www/manager6/form/CPUModelSelector.js | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/www/manager6/form/CPUModelSelector.js b/www/manager6/form/CPUModelSelector.js index 2ebd08eb..890a7cb1 100644 --- a/www/manager6/form/CPUModelSelector.js +++ b/www/manager6/form/CPUModelSelector.js @@ -19,7 +19,9 @@ Ext.define('PVE.form.CPUModelSelector', { autoSelect: false, deleteEmpty: true, - + config: { + showCustomModels: true, + }, listConfig: { columns: [ { @@ -96,4 +98,11 @@ Ext.define('PVE.form.CPUModelSelector', { }, }, }, + initComponent: function () { + let me = this; + me.callParent(); + if (!me.showCustomModels) { + me.getStore().addFilter({ filterFn: (rec) => !rec.data.custom }); + } + }, }); -- 2.47.3