[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

Fiona Ebner f.ebner at proxmox.com
Tue Jun 6 11:15:05 CEST 2023

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

as that's the default proposed in the latest version.

Best Regards,

More information about the pve-devel mailing list