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 D8F1C1FF15C for ; Fri, 14 Nov 2025 16:07:19 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0921B16C2F; Fri, 14 Nov 2025 16:08:16 +0100 (CET) Message-ID: Date: Fri, 14 Nov 2025 16:07:42 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta To: Proxmox VE development discussion , Fiona Ebner References: <20251107144429.126790-1-f.ebner@proxmox.com> <20251107144429.126790-5-f.ebner@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <20251107144429.126790-5-f.ebner@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1763132835488 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.023 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 Subject: [pve-devel] applied: [PATCH qemu-server v2 4/8] cpu config: introduce vendor-agnostic 'nested-virt' CPU flag 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: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 07.11.25 um 15:44 schrieb Fiona Ebner: > The flag will automatically resolve to the flag required for the > current CPU on the host. The 'nested-virt' flag takes precendence over > the CPU-specific flag for nesting which might already be present with > custom CPU models. In that case, a warning is printed. > > Also make sure that the actual resolved flag is passed along during > live migration, since the nested-virt flag can resolve differently on > different hosts. > > Suggested-by: Thomas Lamprecht > Signed-off-by: Fiona Ebner > --- > > Changes in v2: > * Pass running CPU configuration when using 'nested-virt'. This > ensures that migration fails early if the flag resolves differently > on the target. > * Describe that live migration still only works if it's the same flag. > > I was thinking about using special characters in the flag name or some > custom-/pve-/special- prefix to distinguish from regular flags, but > decided against it in the end, because I got the gut feeling it might > cause more confusion than it helps. Users who are interested in > details will hopefully read the description and for others, having the > flag name be direct and descriptive is better. > > src/PVE/QemuServer/CPUConfig.pm | 52 +++++++++++++++++++++++++++++++-- > 1 file changed, 49 insertions(+), 3 deletions(-) > > Thanks for your follow-up mail, I tested again with EPYX-v4 vCPU for matching the AMD EPYC 9475F in my test server and it worked well. Now the virtualization flag also shows up for the CPU inside the guest from Windows POV, e.g. when checking in the task managers (CTRL+SHIT+ESC) performance tab. I amended the commit message with a note for the cpu model, getting some docs might be nice, especially adapting our nested-virt guide in the wiki with that info. applied, thanks! _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel