This is a great analysis and insight, which in turn means we probably should configure the system to load it.
As you work on a whole set of fixes around the same topic this probably needs to go together with the right types added and so on - you know it better already :-) But for the module we might want to use: - https://www.freedesktop.org/software/systemd/man/latest/modules-load.d.html - only on the two x86 arches as that is where msr applies - something like https://sources.debian.org/src/cups-filters/1.28.17-6/debian/rules/?hl=64#L64 - but today better into the non-user dir of /usr/lib/modules-load.d/ - and for the before-boot maybe add a modprobe to postinst This should affect Debian as well (can't check their kernel config atm if it is a module) and fixing it with them has the benefit of not conflicting and making the merge more complex later, so a PR should probably best land in https://salsa.debian.org/libvirt-team/libvirt first, which would be picked up by questing and then SRUed once the other "detect my type" cases are ready as well. Until then anyone affected has a workaround with the above already. -- 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
