Hi Amit, thank you so much for jumping in! Yes I'm aware of the machine types, although to admit it always gives me a shiver as the changes there seem to always turn out to bit someone in the long run :-)
But yes, I totally agree that since we can't change the current old types (to keep them migratable) we might need to introduce new variants in the Ubuntu LTSes that need this fix. Introducing a new variable which can change the behavior of the code to behave the fixed way. And then need to maintain this type as long as we want to be able to migrate it into future releases. Ubuntu's names are like pc-i440fx-noble or pc-q35-noble and just like we've done for e.g. host physical bits where we created `...-hpb` suffixed we'd need to create something like pc-i440fx-noble-amdnoarchcap / pc-q35-noble-amdnoarchcap (and the same for all still active release prior to most recent qemu). Please feel free to tell me if I'm overlooking something or if you agree to that so far. And as you know, naming things is the hardest task for an engineer :-) If possible I'd like to try to stay the consistent with the naming. You said "... were resolved in both RHEL and upstream ...". But I can't see that anywhere. The upstream code did introduce a new qemu-X.Y with the new release - but no new backwards type, or is there a derivative type they introduced for old versions that I've missed? Also I can't see the changes to "rhel-6.2-pc" or such, but I'd assume they can't change "rhel-6.2-pc" itself either, but need a new type right? I'm not asking to share code against anyones will, but if the name of the suffix of a new type could be mentioned that would be nice? Or would you suggest to keep the name as-is but use versioned types which we haven't done for such a case yet, but I know the tech exists. This will be complex and take a while especially since a lot is up right now, but I agree to that path and Hector will have a look at that in more detail. If you have other suggestions along the way or could stay subscribed here to give a review once we came up with something, that would be great. -- 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
