I had this issue today after upgrading from trusty->wily (yes I know not technically supported). Notably I was running the lts-wily kernel on trusty, and I had a cached profile.
So I am wondering if this combination results in the cache needing regeneration but not being triggered for regeneration? I fixed the issue with: apparmor_parser --purge-cache apparmor_parser -R /etc/apparmor.d/usr.sbin.libvirtd apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd systemctl restart libvirt-bin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386465 Title: apparmor profile prevents libvirtd from creating a socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1386465/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
