Hi Alan and Nobuto, we are indeed working on the overall context of all of these again. Some have been slow rolling, some have been needing deeper analysis. But Hector, Lukas and myself have been after them.
Let me summarize a bit for the ease of consumption, but the work will continue in those individual bugs that Nobuto already referenced, The MPX case (bug 2106812) is up for SRU processing already. The TSX case (bug 2106791) went a few extra rounds and might have some resolution in code (load the msr to detect better in many cases) but also need some documentation (when and when not to rely on those names) as outcome. There is even more of the same style with granite rapids mis-detecting registers (bug 2083293). If you wonder what doc might be needed - despite all these efforts to make it as smooth as possible, the continued and repeated lessons learned is that the guest type is just "$name +/- features" and that one should not insist too much on $name to match anything. That is the outcome of every time this came up and even more clear in the recent clarification with upstream https://lists.libvirt.org/archives/list/[email protected]/thread/EZBLO5CIGC3FTI5J72WNVAKWPSNQFLCY/ Therefore some component of the resolution might to make it more clear in upstream docs, an dthen in the Ubuntu Server guide as well plus referencing to it. From here on, please follow the referenced individual related bugs instead of this older one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1978064 Title: [Libvirt] IceLake CPU model not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1978064/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
