# Clarify how to fix it #
Your rules out of logprof are interesting.
I have compared them with the one in the package in regard to unix/dgram
rules which is what the denial is about. The only entry your example has
on top is the following:
network unix dgram,
Could you please try to:
1. revert /etc/apparmor.d/usr.sbin.libvirtd to the content delivered by the
package in 20.04
2. retry and verify the issue triggers
3. restart libvirtd (systemctl restart libvirtd)
4. retry and verify the issue triggers still
5. add this line above to /etc/apparmor.d/usr.sbin.libvirtd where the other
network rules are
6. sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.libvirtd
7. restart libvirtd (systemctl restart libvirtd)
8. retry and verify the issue triggers still (or is it fixed now?)
#3 ensures that restarting the service without a change does not by accident
resolve the issue
#6+#7 ensures that the apparmor profile with the change is reloaded and the
rule is good
Please report how that test worked for you.
Hopefully that is the one entry we need, otherwise we need to continue looking
for differences,
** Changed in: libvirt (Ubuntu Focal)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890858
Title:
AppArmor profile causes QEMU/KVM - Not Connected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890858/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
