Hi, the "file not found" is a red herring - in 99% of the cases it is something in the actual generated profile that is broken. Maybe newer libvirt generates a rule now for you (which it didn't before) and the config for that element contains something (e.g. a bad name) that makes it break.
To debug we'd need the /etc/apparmor.d/libvirt/libvirt-* files after they got generated and failed loading. I think with [1] you can even modify the profile (mostly in the one with .files) and reload until you found which rule is breaking it. I'd assume something like: $ sudo apparmor_parser -r /etc/apparmor.d/libvirt/libvirt-5fb5b85a-b3ec-4e21-ad70-d663689b9fb5 AppArmor parser error for /etc/apparmor.d/libvirt/libvirt-5fb5b85a-b3ec-4e21-ad70-d663689b9fb5 in /etc/apparmor.d/libvirt/libvirt-5fb5b85a-b3ec-4e21-ad70-d663689b9fb5 at line 11: syntax error, unexpected TOK_CLOSE, expecting TOK_END_OF_RULE Iterate: vim /etc/apparmor.d/libvirt/libvirt-<UUID>.files # adapt rules sudo apparmor_parser -r /etc/apparmor.d/libvirt/libvirt-<UUID> # until this works [1]: https://help.ubuntu.com/community/AppArmor#Reload_one_profile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384532 Title: Unable to set AppArmor profile [...] no such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1384532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
