From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 1AA93C189A for ; Tue, 16 Jan 2024 16:20:28 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EEADC38D57 for ; Tue, 16 Jan 2024 16:20:27 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Tue, 16 Jan 2024 16:20:26 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 4260149156; Tue, 16 Jan 2024 16:20:26 +0100 (CET) Message-ID: Date: Tue, 16 Jan 2024 16:20:24 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: "DERUMIER, Alexandre" , "pve-devel@lists.proxmox.com" , "d.csapak@proxmox.com" , "aderumier@odiso.com" References: <20240112200806.309336-1-aderumier@odiso.com> <9c1ce32e-e54d-460d-81e4-8e4829853b24@proxmox.com> <5fd038cc440c6dfd4e97961f8e098dae4c3f328a.camel@groupe-cyllene.com> From: Fiona Ebner In-Reply-To: <5fd038cc440c6dfd4e97961f8e098dae4c3f328a.camel@groupe-cyllene.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.075 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 T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pve-devel] [PATCH pve-manager] qemu: bump max cores to 256 by socket X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jan 2024 15:20:28 -0000 Am 16.01.24 um 15:08 schrieb DERUMIER, Alexandre: > >>> Is the QEMU error message understandable? If yes, I don't see much >>> value > > Well, indeed, the message is pretty clear. > maybe just add documentation about limit for q35 && i440fx ? > > (I have a customer with a new epyc v4, asking me about this, and I had > no idea that they was a different limit between q35 && i440fx) > Sure, we can mention that the limit depends on the machine version in the CPU section and/or machine version section. Note it's not only type, but version, e.g. q35-8.0 has 288 as a limit: https://github.com/qemu/qemu/blob/master/hw/i386/pc_q35.c#L419