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 F3F551FF14C for ; Fri, 15 May 2026 11:45:22 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 642201689B; Fri, 15 May 2026 11:45:21 +0200 (CEST) Date: Fri, 15 May 2026 11:45:16 +0200 From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com Subject: Re: [PATCH pve-manager v5 14/21] api: add endpoint querying available CPU flags cluster-wide Message-ID: References: <20260515092839.238064-1-a.bied-charreton@proxmox.com> <20260515092839.238064-15-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260515092839.238064-15-a.bied-charreton@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1778838311068 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.766 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 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: 7LNIEGTRNC4HA3MLS4VX3NBUIDOW5E3T X-Message-ID-Hash: 7LNIEGTRNC4HA3MLS4VX3NBUIDOW5E3T 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 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 Fri, May 15, 2026 at 11:28:31AM +0200, Arthur Bied-Charreton wrote: > Add endpoint at `/cluster/qemu/cpu-flags` allowing to query the CPU > flags available on the whole cluster, filtered by acceleration type > (kvm/tcg). > > For each flag, a list of nodes supporting it is returned. This gives an > accurate picture of which flags will actually be accepted by QEMU when > starting a VM. I meant to reword that, sorry - since the endpoint also returns the 'nested-virt' flag, this is not really true, should rather be 'accepted by PVE in a processor config'. > > Currently only return available flags for x86_64, see documentation of > query_available_cpu_flags. > > Signed-off-by: Arthur Bied-Charreton [...]