Hello, I will go ahead with the following approach:
Please let me know what you think,
* Noble:
- Creation of 2 machine types: pc-i440fx-noble-v2, pc-q32-noble-v2
- Point the machine type "ubuntu" to pc-i440fx-noble-v2 instead of
pc-i440fx-noble
- Backport of the arch_caps fix (available in qemu 10.1)
target/i386: do not expose ARCH_CAPABILITIES on AMD CPU
(https://github.com/qemu/qemu/commit/d3a24134e37d57abd3e7445842cda2717f49e96d)
and only enable it for pc-i440fx-noble-v2, pc-q32-noble-v2
* Plucky:
- Creation of 4 machine types: pc-i440fx-plucky-v2, pc-q32-plucky-v2,
pc-i440fx-noble-v2, pc-q32-noble-v2
- Point the machine type "ubuntu" to pc-i440fx-plucky-v2 instead of
pc-i440fx-plucky
- Backport of the arch_caps fix (available in qemu 10.1)
target/i386: do not expose ARCH_CAPABILITIES on AMD CPU
(https://github.com/qemu/qemu/commit/d3a24134e37d57abd3e7445842cda2717f49e96d)
and only enable it for the new *-v2 types.
* Questing/ Resolute (qemu >= 10.1 - original problem fixed):
- Creation of 4 machine types: pc-i440fx-plucky-v2, pc-q32-plucky-v2,
pc-i440fx-noble-v2, pc-q32-noble-v2
- Gate the fix for the new *-v2 types
* Jammy
We will try to backport the fix to Jammy as well, if successful, we will
include Jammy into the solution and create needed jammy machine types and
propagate them to later releases.
--
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
