Thanks for your Feedback Kim! This confirms (as we've assumed before) that it is a valid case and the discussed rule will make it work for you. But far we didn't know how others could trigger it. After all we seem to have a few affected but the majority isn't. But to generally allow "network unix dgram" we'll have to make a case what use case it is needed for.
So the question is (again), what is different on your libvirt (and the rest of) installation that makes you trigger this? I've tried this - with/without upgrades and several config - it never triggered over here. So I beg your pardon and want to ask: - what else than "apt install libvirt-daemon-system" + "virsh ..." commands to spawn your guest did you do? - Is it affecting all guest, if not what makes the affected ones special? - Can you recreate the same on a new fresh system - if so what is the sequence of commands to get there? -- 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
