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
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
