virt-aa-helper has done this for as long as I can remember. /lib4 is not an FHS compliant location to store volatile data like VMs, which is what virt-aa-helper is trying to enforce (ie, if someone is trying to also restrict libvirtd itself, then virt-aa-helper has to be careful to not allow someone with libvirtd qemu:///system access to various files which could be used to escalate privileges.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/799997 Title: error happen when using virsh to start a vm " internal error cannot generate AppArmor profile" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/799997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
