Let me explain, Hector did an analysis and backporting it there would
need way more internal code infrastructure patches on top which IOHO
increase the risk too much that an SRU should go with. Hence the won't
fix - but that was an accident as there are many related issues (cpu /
fetaure detection) around this (msr loading).
To be clear, having it load the msr should be an easy backport, but the
code that would use the MSR info for extended things like the VMX
details is not there in jammy.
Let me set this back to in progress and put the pure loading of the MSR
in action. But do not expect the deeper "after load the many other
things it could detect from the MSR" also to jammy. That means it will
help some but not all related cases. But this bug here is only about the
MSR load and how it might also help the TSX detection (which we need to
recheck to be true to truly SRU this)
Sorry for the back and forth in regard to the state - Hector will have a
deeper look, and if we didn't miss something that should be fine to now
also get to Jammy.
** Changed in: libvirt (Ubuntu Jammy)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106791
Title:
Emerald Rapids cannot be used as Sapphire Rapids on Ubuntu due to TSX
features
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/2106791/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
