** Tags added: kernel-daily-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails with failure to open mount namespace
To manage notifications about this bug go to:
https:/
Ubuntu 18.10 (Cosmic Cuttlefish) has reached end of life, so this bug
will not be fixed for that specific release.
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails with failure to open mount namespace
To manage notifications about this bug go to:
https://bugs.launch
** Changed in: libvirt (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails with failure to open mount namespace
To manage noti
This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.5
---
libvirt (4.0.0-1ubuntu8.5) bionic; urgency=medium
* d/p/ubuntu-aa/lp-1788603-fix-ptrace-rules-with-kernel-4.18.patch:
avoid issues with newer kernels >=4.18 (LP: #1788603)
* d/p/ubuntu/lp-1789659-don-t-check-for-
** Bug watch added: Debian Bug tracker #908341
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908341
** Also affects: libvirt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908341
Importance: Unknown
Status: Unknown
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
Started a guest with Bionic and Kernel 4.18 - working due to the updated
apparmor profile.
We already had general regression tests on the identical PPA content, not
redoing the same.
Setting verified.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-do
Hello Thadeu, or anyone else affected,
Accepted libvirt into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/4.0.0-1ubuntu8.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Had another set of regression tests as I bundled another fix.
All good still.
Pushing for the SRU teams consideration ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails
Ok, glibc was unblocked and we can take a look at pushing this for
Bionic as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails with failure to open mount namespace
To
This bug was fixed in the package libvirt - 4.6.0-2ubuntu3
---
libvirt (4.6.0-2ubuntu3) cosmic; urgency=medium
* d/p/ubuntu-aa/lp-1788603-fix-ptrace-rules-with-kernel-4.18.patch:
avoid issues with newer kernels >=4.18 (LP: #1788603)
-- Christian Ehrhardt Mon, 27 Aug
2018 10:
PPA for the Bionic SRU at
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3386
Note: This not only waits for Cosmic to complete, but also for the former SRU
to complete as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
FYI cosmic is slightly stalled by glibc migration, other than that it
looks good to me at the moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails with failure to open
** Description changed:
+ [Impact]
+
+ * Libvirt will no more be able to start guests with newer kernels
+(>=4.18)
+
+ * We brought a fix upstream that we want to backport to potentially
+affected releases (B+C)
+
+ [Test Case]
+
+ Note: This can but does not have to be tested in n
Tested against Kernel 4.18 from mainline builds:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18/linux-image-unsigned-4.18.0-041800-generic_4.18.0-041800.201808122131_amd64.deb
For the latter SRU I summarized the testing procedure:
Note: This can but does not have to be tested in nested virtu
Tested from PPA, also passed through some more checks and all look fine
- but that was expected given the change being "just" opening up
apparmor a little bit.
Uploading to Cosmic ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Prepared in PPA: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3381
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails with failure to open mount namespace
To
Upstream accepted:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=8741b9435108b1f0d87670e44e1ed75f806b7791
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails with failure
Tested, confirmed wrapped in a libvirt upstream patch and submitted at
https://www.redhat.com/archives/libvir-list/2018-August/msg01532.html
Lets give the people a few days to read and ack as well then we can push
it to cosmic.
It came to my mind that due to HWE-Kernels we eventually also want th
ago 23 14:40:18 calabresa audit[5997]: AVC apparmor="DENIED" operation="ptrace"
profile="/usr/sbin/libvirtd" pid=5997 comm="libvirtd" requested_mask="read"
denied_mask="read" peer="unconfined"
ago 22 18:00:12 calabresa audit[4409]: AVC apparmor="DENIED" operation="ptrace"
profile="/usr/sbin/libv
So, investigated this into an apparmor difference between 4.17 and 4.18.
This is due to commit 338d0be437ef10e247a35aed83dbab182cf406a2
("apparmor: fix ptrace read check").
libvirtd here is using only trace, and not read. The patch below for
libvirtd apparmor policy fixes it for me.
--- /etc/appa
22 matches
Mail list logo
