why the libvirtd profile was not parsed. Libvirtd itself is confined and it's supporting utilities (libvirtd//qemu_bridge_helper, virt-aa-helper) are confined too, as stated in my comment #3 (which corrects #2 - it was poorly worded, because it was unclear whether libvirt means both libvirt-* profiled or also libvirtd - I meant just
http://bugzilla.opensuse.org/show_bug.cgi?id=1125841 http://bugzilla.opensuse.org/show_bug.cgi?id=1125841#c10 --- Comment #10 from Martin Kalivoda <supercoolemail@seznam.cz> --- (In reply to James Fehlig from comment #9) libvirt-*). To make it clear: - libvirtd is confined - apparmor works fine otherwise - failure in clean install can be triggered by explicitly setting security_driver to apparmor, nothing more is necessary.
I don't see any problems on my Tumbleweed KVM host Do you have updated Tumbleweed with libvirt 5 and did you explicitly set security_driver to apparmor in /etc/libvirt/qemu.conf ?
-- You are receiving this mail because: You are on the CC list for the bug.