[Pkg-libvirt-maintainers] Bug#878203: AA breaks libvirt when running with kernel 4.13

[Guido Günther]

Hi,
On Wed, Oct 11, 2017 at 02:10:01AM +0200, Michael Biebl wrote:
> Package: apparmor
> Version: 2.11.0-11
> Severity: serious
> 
> After the kernel upgrade from 4.12 to 4.13 my KVM/libvirt instances
> failed to start:
> Okt 10 19:24:44 pluto libvirtd[673]: 2017-10-10 17:24:44.404+0000: 797: error : virProcessRunInMountNamespace:1159 : internal error: child reported: Kernel does not provide mount namespace: Permission denied
> 
> Disabling AppArmor made libvirt work again.
> There seems to be an incompatibility between the 4.13 kernel and
> AppArmor. Please reassign if you think this is a bug in the kernel.
> 
> I've decided to mark this as RC, as breaking KVM is a rather severe
> regression which needs to be fixed for buster.
> 
> A quick internet search turns up
> https://forums.opensuse.org/showthread.php/527394-KVM-guest-will-not-start-with-latest-version-of-kernel
> and following that
> https://www.redhat.com/archives/libvir-list/2017-September/msg00546.html

I can't reproduce this here with 4.13.0-1-amd64 and
libvirt-daemon-system 3.8.0-3.
 -- Guido