Comment 7 for bug 637544

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.