** Changed in: qemu (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: qemu (Ubuntu Disco)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
** Changed in: qemu (Ubuntu Disco)
Status: In Progress => Won't Fix
--
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 notifi
** Changed in: qemu (Ubuntu Bionic)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu Disco)
Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)
** Changed in: qemu (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: qe
This bug was fixed in the package qemu - 1:4.0+dfsg-0ubuntu6
---
qemu (1:4.0+dfsg-0ubuntu6) eoan; urgency=medium
* d/p/ubuntu/lp-1841066-*: fix detection of arch_capability flags
(LP: #1841066)
-- Christian Ehrhardt Mon, 26 Aug
2019 12:08:04 +0200
** Changed in: qemu (Ubunt
The qemu changes have to go along the libvirt uploads that are at least
in consideration for bug 1828495. They are not strictly dependent (none
breaks without the other) but the full function of security mitigation
usability can only be achieved with both.
** Also affects: qemu (Ubuntu Disco)
I
** Changed in: qemu (Ubuntu)
Status: Triaged => In Progress
--
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
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/371796
--
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 cap
Test PPA [1] confirmed to work in Eoan.
Will propose an MP for those qemu changes.
[1]: https://launchpad.net/~paelzer/+archive/ubuntu/experimental-eoan-
archcap-detection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
qemu head (4.2 dev) - works
v4.1.0 - works
v4.0.0 - fails (well we know it is post 4.0 code so that is fine).
That called for a bisect:
BAD = once the feature is detected:
git bisect start
# bad: [9e06029aea3b2eca1d5261352e695edc1e7d7b8b] Update version for v4.1.0
release
git bisect bad 9e06029a
Related libvirt changes:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=0d254bce
https://libvirt.org/git/?p=libvirt.git;a=commit;h=8eb4a89f
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841066
Tit
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 chang
That identified:
506174bf8219dc6d56d2b1f7e66e8cf39157466f is the first bad commit
commit 506174bf8219dc6d56d2b1f7e66e8cf39157466f
Author: Eduardo Habkost
Date: Mon Apr 22 20:47:42 2019 -0300
i386: "unavailable-features" QOM property
Add a "unavailable-features" QOM property to X86C
On the "same" libvirt code I can detect the features just right by copying in
an upstream build of recent qemu.
So either this actually misses qemu changes to fully work OR libvirt needs code
to better work with "older" qemu.
--
You received this bug notification because you are a member of Ubu
13 matches
Mail list logo
