From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <a.lauterer@proxmox.com> 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 F02699D23E for <pve-devel@lists.proxmox.com>; Fri, 2 Jun 2023 14:41:50 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id CA6092A7E2 for <pve-devel@lists.proxmox.com>; Fri, 2 Jun 2023 14:41:20 +0200 (CEST) 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 <pve-devel@lists.proxmox.com>; Fri, 2 Jun 2023 14:41:19 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id EE40148494; Fri, 2 Jun 2023 14:41:18 +0200 (CEST) Message-ID: <34e130a8-e3c0-8dc7-dd72-51d22a670f4a@proxmox.com> Date: Fri, 2 Jun 2023 14:41:18 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.1 Content-Language: en-US To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>, Fiona Ebner <f.ebner@proxmox.com>, Eneko Lacunza <elacunza@binovo.es>, "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>, "aderumier@odiso.com" <aderumier@odiso.com> References: <20230522102528.186955-1-aderumier@odiso.com> <4d8191f2-4954-1e4f-a40c-51544289b2ce@proxmox.com> <036ad8c33f6af74da89eb8b9c24c1c6cda8fc938.camel@groupe-cyllene.com> <8277a27b-a70f-b731-69f7-fc9ae69b2da2@binovo.es> <5a05ae07-7002-8e3a-1e11-bd5269d58e4f@proxmox.com> From: Aaron Lauterer <a.lauterer@proxmox.com> In-Reply-To: <5a05ae07-7002-8e3a-1e11-bd5269d58e4f@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.042 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 NICE_REPLY_A -0.1 Looks like a legit reply (A) 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 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com] Subject: Re: [pve-devel] [PATCH-SERIES v3 qemu-server/manager/common] add and set x86-64-v2 as default model for new vms and detect best cpumodel X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Fri, 02 Jun 2023 12:41:51 -0000 For the record, I tested on: AMD Ryzen 9 7900X 12-Core Processor AMD EPYC 7302P 16-Core Processor (Rome) AMD EPYC 7313 16-Core Processor (Milan) VMs were all with 2 or 4 cores, q35 and UEFI boot. >> qm set <ID> -args '-cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+sep,+lahf_lm,+popcnt,+sse4.1,+sse4.2,+ssse3' all VMs installed nicely without a problem >> qm set <ID> -args '-cpu Nehalem,enforce,+aes,-svm,-vmx,+kvm_pv_eoi,+kvm_pv_unhalt,vendor="GenuineIntel"' VMs got stuck during the Debian installer at some point, some were able to switch to another TTY, but I don't think that is deterministic. On the Ryzen 7900X machine, I even saw a crash and kernel trace once when starting the installer. It didn't show up again after a reset and cold boot of the VM :-/ On 6/1/23 18:00, Fiona Ebner wrote: > Am 01.06.23 um 14:02 schrieb Eneko Lacunza: >> Hi, >> >> We have Ryzen 1700, 2600X, 3700 and 5950X machines here, I can test on >> them if that helps (please detail tests to perform). >> >> Thanks >> > > Hi, > thank you for the offer. It would be interesting to see if you have any > issues with the following: > >> qm set <ID> -args '-cpu kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+sep,+lahf_lm,+popcnt,+sse4.1,+sse4.2,+ssse3' > > If you like you can also test > >> qm set <ID> -args '-cpu Nehalem,enforce,+aes,-svm,-vmx,+kvm_pv_eoi,+kvm_pv_unhalt,vendor="GenuineIntel"' > > After testing use > >> qm set <ID> --delete args > > to get rid of the modification again. > > Make sure to stop/start the VM fresh after each modification. > > As for what to test, installing Debian 11 would be nice just for > comparison, but other than that, just do what you like, shouldn't really > matter too much :) > > Best Regards, > Fiona > > > _______________________________________________ > pve-devel mailing list > pve-devel@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel > >