Those extra MPs only exist in LXD containers, but other solutions might have other sub /dev/* MPs. Newer libvirt tries to preserve these into the qemu namespace, which is what breaks it now.
But when resolving the LXD specials I found that others are hit just as much. E.g. mount: devpts on /dev/console type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) triggers: profile="/usr/sbin/libvirtd" name="/run/libvirt/qemu/1-kvmguest-cosmic-norm.console" srcname="/dev/console" flags="rw, move" Essentially any mounts under /dev would have to be covered, we don't want to have a LXD only solution that tomorrow breaks on any other container and/or different LXD setup. Also hit /dev/net/tun, ... this is not LXD only at all -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786168 Title: qemu mount namespaces conflict with libvirt 4.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1786168/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
