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

From: "DERUMIER, Alexandre" <alexandre.derumier@groupe-cyllene.com>
To: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>,
	"a.lauterer@proxmox.com" <a.lauterer@proxmox.com>,
	"aderumier@odiso.com" <aderumier@odiso.com>,
	"f.ebner@proxmox.com" <f.ebner@proxmox.com>,
	"elacunza@binovo.es" <elacunza@binovo.es>
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
Date: Fri, 2 Jun 2023 14:15:46 +0000	[thread overview]
Message-ID: <f18bf2411629720376515105979454fafd90686c.camel@groupe-cyllene.com> (raw)
In-Reply-To: <34e130a8-e3c0-8dc7-dd72-51d22a670f4a@proxmox.com>

Thanks Aeron.

I'll try to reproduce on my side on epyc milan. 
AMD EPYC 7543 32-Core Processor microcode patch_level=0x0a0011ce
(I just tried again with q35, but I'm still not able de reproduce)

can you share your full vmid.conf ?  (numa ?  vga ?..).

do you use debian graphical install or console install ?

host kernel version ? (I'm still testing on 5.15 / qemu 7.4)

my last patch version use qemu64 as base without specifify the vendor,
so I think it should ok, but I would like to find what happend exactly
:)

Le vendredi 02 juin 2023 à 14:41 +0200, Aaron Lauterer a écrit :
> 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,+s
> > > se4.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://antiphishing.cetsi.fr/proxy/v3?i=SGI0YVJGNmxZNE90Z2thMFYLWSxJOfIERJocpmb73Vs&r=SW5LV3JodE9QZkRVZ3JEYaKhfBhKBzRXSL89azwXC1T82d4SHYTQZhKJK2pOWOed&f=bnJjU3hQT3pQSmNQZVE3aOBk4INl-9oWq-3WY1DAs1r4EwFE_F3He2PZuXGJPKRN&u=https%3A//lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel&k=dFBm
> > 
> > 
> 