A failure of virt-aa-helper to access a file is not necessarily fatal,
as can be seen from /etc/apparmor.d/libvirt/libvirt-
ff58f570-9915-eaa8-4fa6-3cba2a827850.files -- it added it to the profile
just fine. While this certainly needs to be fixed in the AppArmor
profile (to avoid confusion), the failure to start is something else.
I've examined the kern.log and I don't see any AppArmor denials that
would cause the guest to not start.
** Changed in: libvirt (Ubuntu)
Importance: High => Low
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
--
apparmor=DENIED operation=open parent=3343
profile=/usr/lib/libvirt/virt-aa-helper
https://bugs.launchpad.net/bugs/637544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
