Thanks for the test of the new kernel Markus!
I have respun the qemu build (the old one was outdated by a massive stable update - too bad this wasn't part of 4.2.1 already) with the patches we had before applied on top. Further I have reviewed the suggested libvirt changes and added a build of that. There is another AMD SVM change which makes sense in the same context and a few more. All those are in libvirt >=6.5 and therefore already in Groovy. But in the past it turned out useful for users to get all those changes as long as they are easy to backport and not conflicting (e.g. once we had a rework there). I agree with the "Distinguish" patch and have seen that in the wild. The drawback for this kind of patches usually was that migrations from new-to-old might fail specifying features unknown to the other peer, but that is ok as it can be safely considered required to update the target before migration as well (reverse migrations always work best-effort but never are guaranteed). That would overall be this list for libvirt: 5d6059f8 cpu_map: Distinguish Cascadelake-Server from Skylake-Server 59558518 cpu_map: Introduce ARM cpu models 12eb0c94 cpu_map: Add pschange-mc-no bit in IA32_ARCH_CAPABILITIES MSR 3944f685 cpu_map: Add Cooperlake x86 CPU model 1c425857 cpu_map: Distribute x86_Cooperlake.xml df69263c cpu_map: Request test files update when adding x86 features 6ea3bb19 cpu_map: Add missing x86 features in 0x7 CPUID leaf 892b7c70 cpu_map: Add missing x86 features in 0x80000008 CPUID leaf 96a39aad cpu_map: Add missing AMD SVM features The PPA [1] still is the same and now contains: - qemu 1:4.2-3ubuntu6.7~ppa1 - libvirt 6.0.0-0ubuntu8.5~ppa1 @Markus: - If you could give those builds a try on your system, that would be helpful to see if we can/should go on this way? - Further if you would not mind upstreaming your x86_EPYC-Rome.xml change (CC me please) that would be great? Adding types matching what qemu already added should be fine and it would be great to have that added upstream before continuing (we also need this in groovy before a Focal SRU). Or as an alternative if from your tests you think the libvirt build as provided in the PPA is enough (without the Rome name but with the features) as-is then we can go with that. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4161 [2]: branch for libvirt "bug-1887490-new-cpu-handling" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887490 Title: Add/Backport EPYC-v3 and EPYC-Rome CPU model Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Focal: Incomplete Status in linux source package in Focal: Fix Committed Status in qemu source package in Focal: Incomplete Bug description: Qemu in focal has already support for most (except amd-stibp) flags of this model. Please backport the following patches: https://github.com/qemu/qemu/commit/a16e8dbc043720abcb37fc7dca313e720b4e0f0c https://github.com/qemu/qemu/commit/143c30d4d346831a09e59e9af45afdca0331e819 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1887490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
