http://bugzilla.opensuse.org/show_bug.cgi?id=1045158
http://bugzilla.opensuse.org/show_bug.cgi?id=1045158#c1
Christian Boltz
Once I stopped apparmor with systemctl stop apparmor.service, virtual machines can be started fine. If I start apparmor afterwards, I can stop and start virtual machines correctly, but if I do: systemctl restart libvirtd with apparmor running, then I can't run virtual machines anymore.
That's easy to explain - by stopping AppArmor, you remove the confinement from running processes, and "rcapparmor start" isn't able to (re-)confine running processes (unless you restart those processes). That's why AppArmor gets in your way again after restarting libvirtd. -- You are receiving this mail because: You are on the CC list for the bug.