Thanks for the report and hi Kim o/, I have not gone down the route of checking the actual windows installs, the report looks of good quality to me. But the referred change is a known suspect - one we have been part of identifying and resolving the regressions it causes.
The bug report mentions "Fixed in 10.0.4, though the fixed caused a regression that was fixed in 10.0.6" but in detail that means - the change was a breaking one making it impossible to save/restore or migrate across these updates or versions. Therefore 10.0.6 is just as affected as it was. In 10.1 the change landed to fix this was: d3a24134e37 target/i386: do not expose ARCH_CAPABILITIES on AMD CPU The details of the related regression can be seen in https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2121787 (long story of its own). The subsequent fixup for that regression made it into the not yet released 10.2 6529f31e0dc target/i386: add compatibility property for pdcm feature e9efa4a7716 target/i386: add compatibility property for arch_capabilities Since then it also made it into - upstream 10.1.2 - And since we caught it in time for questing it was in 1:10.1.0+ds-5ubuntu2 on release Thereby questing onward are fixed of the original issue fixed by Paulo and of the related regression we contributed. But the bug report here implies that we might want/need d3a24134e37 target/i386: do not expose ARCH_CAPABILITIES on AMD CPU backported. Yet without thinking more deeply into it I can not yet see a way how to backport this without also regressing all save/restore/migration again. The regression fix was to make the new code know that the old code still did it the old way - this is now asking to change the old behavior which would split the past into two different behaving yet indistinguishable modes. That is the reason why 10.0.4 had it but 10.0.6 reverted it again (as in not added the follow up fixes). Thereby upstream 10.0.x and all other pre 10.1.2/10.2 are affected still. Maybe there is a way to change behavior only where it was formerly broken? But qemu would and should not know about the guest workload - so how would it know. Just introducing the code change will affect all guests on AMD not just those with the not so tolerant Windows 11 24H2 - and that means we might negatively affect a wider userbase than we fix. From far away this sounds like best case adding a switch that allows opt-in for the fix, but that then needs to be used to be any help. Either way, it is complex and it is definetly needing more time and it is competing with general updates and many other fixes for capacity - hence it will not be super-fast. ** Changed in: qemu (Ubuntu) Status: New => Confirmed ** Changed in: qemu (Ubuntu) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Also affects: qemu (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Questing) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Resolute) Importance: Medium Assignee: Hector CAO (hectorcao) Status: Confirmed ** Also affects: qemu (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu Resolute) Status: Confirmed => Fix Released ** Changed in: qemu (Ubuntu Resolute) Assignee: Hector CAO (hectorcao) => (unassigned) ** Changed in: qemu (Ubuntu Plucky) Status: New => Confirmed ** Changed in: qemu (Ubuntu Questing) Status: New => Fix Released ** Changed in: qemu (Ubuntu Jammy) Status: New => Confirmed ** Changed in: qemu (Ubuntu Noble) Status: New => Confirmed ** Changed in: qemu (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu Plucky) Importance: Undecided => Wishlist ** Changed in: qemu (Ubuntu Noble) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: qemu (Ubuntu Questing) Importance: Undecided => Medium ** Changed in: qemu (Ubuntu Jammy) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2131822 Title: Known Windows 11 KVM Issue AMD KMODE Exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2131822/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
