From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <f.ebner@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 379BF9DDB7 for <pve-devel@lists.proxmox.com>; Tue, 6 Jun 2023 11:15:07 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 1A03F3224F for <pve-devel@lists.proxmox.com>; Tue, 6 Jun 2023 11:15:07 +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>; Tue, 6 Jun 2023 11:15:06 +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 5346848C62; Tue, 6 Jun 2023 11:15:06 +0200 (CEST) Message-ID: <5136f9b7-af74-df84-0fc4-c2bc08970ef9@proxmox.com> Date: Tue, 6 Jun 2023 11:15:05 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Content-Language: en-US To: Eneko Lacunza <elacunza@binovo.es>, Proxmox VE development discussion <pve-devel@lists.proxmox.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> <fa3565e5-3a9c-9348-f291-554a0e0d6628@binovo.es> From: Fiona Ebner <f.ebner@proxmox.com> In-Reply-To: <fa3565e5-3a9c-9348-f291-554a0e0d6628@binovo.es> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.001 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.094 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 - 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: Tue, 06 Jun 2023 09:15:07 -0000 Am 05.06.23 um 17:20 schrieb Eneko Lacunza: > Hi, > > I'm sorry I could only test for Ryzen 1700, 2600X and 5950X - our 3700X > is offline, pending some upgrades. I hope it will be back again in some > days. > > Tested installation of Debian 11.1.0 ISO with GUI installer upto first > boot to GUI login to installed system: > > > El 1/6/23 a las 18:00, Fiona Ebner escribió: >>> qm set <ID> -args '-cpu >>> kvm64,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+sep,+lahf_lm,+popcnt,+sse4.1,+sse4.2,+ssse3' > > This was good for all 1700, 2600X and 5950X. > >> 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"' > This was good for 1700, but I suspect it may hang later, will check > tomorrow. > > 2600X: install was good, but after booting to GUI login screen, it froze > with ~50% CPU use. A reset booted well, no hang for now. > 5950X hung during installation, no CPU use. Reset + reinstall worked OK > > 3 VMs are left running in login screen to check tomorrow. > Thank you for testing! This is consistent with what Aaron and I experienced. So there is an issue with basing the CPU off Nehalem (in combination with the kvm_pv_unhalt flag), but basing off kvm64 seems to work just fine :) If you'd like to further test, please use qm set <ID> -args '-cpu qemu64,+aes,enforce,+kvm_pv_eoi,+kvm_pv_unhalt,+pni,+popcnt,+sse4.1,+sse4.2,+ssse3' as that's the default proposed in the latest version. Best Regards, Fiona