@Felipe, with your feedback, I can now give you an accurate explanation,
1) on Jammy, we backported the capability to detect SapphireRapids-noTSX some time ago, we realized that that does not work and requires additional fix that consists of loading the MSR module, we are discussing with libvirt upstream on fixing this : https://lists.libvirt.org/archives/list/[email protected]/thread/5WYDTKXASM4Y7ZT4VW7ADXDVBRISK6VD/ 2) This LP bug has been reported originally because the backport to Jammy for SapphireRapids-noTSX has not been properly propagated to following series (Noble, ...) but after discussion with upstream, we decide to not fix the issue for Noble onwards (that is why it put this bug to Won't Fix). The argument from upstream is that we shoud not expect the CPU model name to match exactly the host CPU, we should represent the Host CPU as CPU model +/- features. However, if there is any strong valid reason to go back on this decision, we can discuss about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2084102 Title: Sapphire rapids not recognized by virsh capabilities To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/2084102/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
