@rafael - One more question about Stepping 5/6. I have formerly read your explanation that stepping 6 would be required to be able to enable arch_capabilities. And we planned to add all SRUs with stepping 6 right away and keep the Delta to consider all versions to be stepping 6.
But then I have seen [1] and in particular [2]. Overall this adds more complexity but also more ability to CPU model definitions. But in between the lines in [2] I read that arch_capabilities gets enabled by default and stepping goes back to 5. That seems to imply that enabling it on stepping 5 isn't an issue. If it does work doing the SRU that way it will ease maintenance in the future. Especially since these versioned types will make maintaining Delta in that area even more complex. And it would avoid the upgrade issue on Disco where the CascadeLake would change. Therefore I wondered if we could make the backport use stepping 5 which would allow to not carry the delta forever in >=Eoan. Could you make a PPA build as it is right now, but with stepping 5 and check if using arch_capabilities still works for you? [1]: https://www.mail-archive.com/qemu-devel@nongnu.org/msg626545.html [2]: https://www.mail-archive.com/qemu-devel@nongnu.org/msg626550.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs