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 this in
Bionic.
So lets add a task right away to not forget.
** Also affects: libvirt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: libvirt (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788603
Title:
libvirt fails with failure to open mount namespace
Status in libvirt package in Ubuntu:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in libvirt source package in Bionic:
Confirmed
Status in linux source package in Bionic:
New
Status in libvirt source package in Cosmic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
$ virsh start cosmic-i386
error: Failed to start domain cosmic-i386
error: internal error: child reported: Kernel does not provide mount
namespace: Permission denied
Happens with 4.18 only, 4.17 is fine.
27013 openat(AT_FDCWD, "/proc/27012/ns/mnt", O_RDONLY) = -1 EACCES
(Permission denied)
Opening a self or parent mount namespace works fine as tested with cat
/proc/self/ns/mnt and cat /proc/self/$$/mnt. Still investigating.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1788603/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
