Package: apparmor Version: 2.10-4 Severity: important Hi,
I've been trying to debug why libvirt fails to start qemu:///session
domains. Suspecting apparmor into the mix I did:
$ aa-complain /usr/sbin/libvirtd
$ virsh -c qemu:///session start sqs
error: Failed to start domain sqs
error: Failed to connect socket to '/run/user/1000/libvirt/virtlogd-sock':
Connection refused
Howver if I do:
$ aa-disable /usr/sbin/libvirtd
$ virsh -c qemu:///session start sqs
Domain sqs started
I've attached the domain XML to reproduce. Libvirt is 1.3.5~rc1 from
experimental but 1.3.4 shows this as well.
As to my understanding complain mode shouldn't have any ill effects
therefore I'm filing this as important.
Cheers,
-- Guido
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages apparmor depends on:
ii debconf [debconf-2.0] 1.5.59
ii libapparmor-perl 2.10-4
ii libc6 2.22-9
ii lsb-base 9.20160110
pn python3:any <none>
apparmor recommends no packages.
Versions of packages apparmor suggests:
pn apparmor-docs <none>
ii apparmor-profiles 2.10-4
ii apparmor-profiles-extra 1.8
ii apparmor-utils 2.10-4
-- debconf information:
apparmor/homedirs:
smoke-qemu-session.xml
Description: XML document
