[Pkg-libvirt-maintainers] Bug#883574: Bug#883574: libvirt-daemon-system: fails to start any VM with apparmor enforced

Kjö Hansi Glaz kjo at a4nancy.net.eu.org
Tue Dec 5 17:37:00 UTC 2017


Hi,

> Please provide logging output

audit[3232]: AVC apparmor="STATUS" operation="profile_replace"
profile="unconfined" name="libvirt-3219c451-fcb5-4e6d-
kernel: audit: type=1400 audit(1512470093.378:89): apparmor="STATUS"
operation="profile_replace" profile="unconfined"
audit[3253]: AVC apparmor="DENIED" operation="mount" info="failed mntpnt
match" error=-13 profile="/usr/sbin/libvirtd
kernel: audit: type=1400 audit(1512470093.386:90): apparmor="DENIED"
operation="mount" info="failed mntpnt match" err
libvirtd[1321]: 2017-12-05 10:34:53.404+0000: 1338: error :
virCommandHandshakeWait:2718 : Child quit during startup
libvirtd[1321]: 2017-12-05 10:34:53.407+0000: 1338: error :
qemuProcessReportLogError:1885 : internal error: Process

libvirt: QEMU Driver error : internal error: Process exited prior to
exec: libvirt:  error : Fail
Error: libvirt failed to start domain

> and steps to reproduce,

>From libvirt create new virtual machine in qemu:///system

The same error happens if I start any other VM, which used to start fine
with libvirt 3.8.0

> kernel version and what else might be needed to reproduce the problem.

4.14.0-1-amd64

> Ask yourself what makes your installation different from the ones
> that work with apparmor enabled.

I'm sorry but I don't see how my libvirt/apparmor installation differs
from another sid system.

Cheers



More information about the Pkg-libvirt-maintainers mailing list