[libvirt-users] trouble after upgrading from 3.0.0 to 3.1.0

Michael Ströder michael at stroeder.com
Tue Mar 14 16:03:11 UTC 2017

Michal Privoznik wrote:
> On 03/14/2017 10:51 AM, Michael Ströder wrote:
>> HI!
>> After the last OS update (openSUSE Tumbleweed) with libvirt being updated from 3.0.0 to
>> 3.1.0 starting the VMs (qemu-kvm) does not work anymore:
>> error: internal error: child reported: Kernel does not provide mount namespace:
>> Permission denied
> Hey, this is definitely a libvirt bug. Since 3.1.0 libvirt spawns each
> qemu in its own mount namespace so that it can have private /dev mount.
> I've heard that there are some issues with AppArmor - is that what are
> you using?

Hmm, yes. I was using AppArmor. Disabling it helped. I will point the author of the
AppArmor profiles in this direction.

> Meanwhile, you can disable namespaces by setting:
>   namespaces=[]
> in qemu.conf.

Only setting this did not help.

Ciao, Michael.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3829 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20170314/e468852b/attachment.p7s>

More information about the libvirt-users mailing list