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 DDFDF9A25A for ; Wed, 17 May 2023 09:03:27 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BAA6E241BC for ; Wed, 17 May 2023 09:02:57 +0200 (CEST) Received: from bastionodiso.odiso.net (bastionodiso.odiso.net [185.151.191.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Wed, 17 May 2023 09:02:54 +0200 (CEST) Received: from kvmformation3.odiso.net (formationkvm3.odiso.net [10.3.94.12]) by bastionodiso.odiso.net (Postfix) with ESMTP id 8A7A68B5B; Wed, 17 May 2023 09:02:47 +0200 (CEST) Received: by kvmformation3.odiso.net (Postfix, from userid 0) id 80966D4D70; Wed, 17 May 2023 09:02:47 +0200 (CEST) From: Alexandre Derumier To: pve-devel@lists.proxmox.com Date: Wed, 17 May 2023 09:02:43 +0200 Message-Id: <20230517070246.660939-1-aderumier@odiso.com> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.017 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 HEADER_FROM_DIFFERENT_DOMAINS 0.25 From and EnvelopeFrom 2nd level mail domains are different 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 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 T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [cpuconfig.pm] Subject: [pve-devel] [PATCH-SERIES qemu/qemu-server/manager 0/1] add and set x86-64-v2 as default model for new vms 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: Wed, 17 May 2023 07:03:28 -0000 Hi, we used kvm64 as default cpumodel since the begin of proxmox. (basically, it's like a pentium4 cpu flags). New distros like rhel9 are compiled to use more modern cpu flags. (and windows already use new flags since year, and we already add some extra cpu flags) " In 2020, AMD, Intel, Red Hat, and SUSE worked together to define three microarchitecture levels on top of the historical x86-64 baseline: * x86-64: original x86_64 baseline instruction set * x86-64-v2: vector instructions up to Streaming SIMD Extensions 4.2 (SSE4.2) and Supplemental Streaming SIMD Extensions 3 (SSSE3), the POPCNT instruction, and CMPXCHG16B * x86-64-v3: vector instructions up to AVX2, MOVBE, and additional bit-manipulation instructions. * x86-64-v4: vector instructions from some of the AVX-512 variants. " (x86-64 is kvm64/qemu64 cpu model). This patch series add new models (patch was found on qemu mailing, but never appplied). "x86-64-abiX" : (as vX are reserved in qemu for revision versioning) https://lore.kernel.org/all/20210526144038.278899-1-berrange@redhat.com/T/ In addition to theses model, I have enabled aes too. I think it's really important, because a lot of users use default values and have bad performance with ssl and other crypto stuffs. This was discussed on the qemu mailing " Crypto accelerator caveats ========================== Similarly I'm not a huge fan of leaving out the "aes" instruction for accelerated crypto, as missing "aes" is also one of the key factors in making qemu64 a bad choice. If we include 'aes' in x86-64-abi2, then we loose support for Nehalem hosts. If we include 'aes' in x86-64-abi3 then we further loose support for Dhyana hosts (an EPYC derived CPU). " Nahelemn is a 2008 cpu, so I think it's ok, we are in 2013 ;) (and user can disable aes flag in gui too) That mean than the minimum compatible cpu for v2 is Intel Westmere (2010) and Amd Bulldozer (2011). This patch series add new models, and set x86-64-abi2 model as default in pve-manager wizard only. (to not break current vm, where kvm64 is the default when cputype is not defined in configuration) The patch serie is for proxmox8/qemu8. (qemu patch need to be reordered, I'm waiting than Fiona qemu 8.0 patches are applied first) pve-qemu: Alexandre Derumier (1): patch: add 0001-add-cpu-models-x86-64-abi.patch .../pve/0001-add-cpu-models-x86-64-abi.patch | 272 ++++++++++++++++++ debian/patches/series | 1 + 2 files changed, 273 insertions(+) create mode 100644 debian/patches/pve/0001-add-cpu-models-x86-64-abi.patch qemu-server: Alexandre Derumier (1): cpuconfig: add new x86-64-abi models PVE/QemuServer/CPUConfig.pm | 4 ++++ 1 file changed, 4 insertions(+) pve-manager: Alexandre Derumier (1): qemu: processor : set x86-64-abi2 as default cputype for create wizard www/manager6/qemu/OSDefaults.js | 1 + www/manager6/qemu/ProcessorEdit.js | 13 +++++++++++++ 2 files changed, 14 insertions(+) -- 2.30.2