And this makes sense, when porting the libvirt part we have seen it relies on
unavailable-features, but I'd back then thought that would be via
query-cpu-definitions.
But obviously (as libvirt will use QOM) it needs it here.
So our qemu in Eoan (and our arch_capability backports) lack this change
(and maybe some context) to make qemu able to talk with libvirt about
the arch-capability features correctly.
I'm going to try identifying what we need in Eoan on top on what we
have.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Triaged
** Changed in: qemu (Ubuntu)
Importance: Undecided => High
** Changed in: qemu (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
** Changed in: libvirt (Ubuntu)
Status: Triaged => Invalid
** Changed in: libvirt (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841066
Title:
ARCH_CAPABILITIES guest capability detection
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1841066/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
