Hi Martin, first of all sorry and I totally understand that this can be annoying if you face it and wonder why it fails. I think you bring a nice thought to the case that wasn't very present so far.
> I don't understand why after 8 years this still fails in a way ... The short and honest answer is because it never became a priority enough to find time for it. Not for the community handling of libvirt and libvirt in Ubuntu nor for a business POV to libvirt based products and offerings from Canonical. > ... that leaves users totally clueless. I think this is the important bit. While the investment to codify a solution for it properly, handling what always feels like infinite special cases ... there is a much smaller investment indeed just making it a bit more clear why it can't work. And maybe hint at the possible workarounds like the custom apparmor rules that an admin can deploy which makes them usable. I still have no time to immediately have myself or someone work on it, but this approach puts it much more in reach. Thank you for the idea and let me break this out into a case on its own. => bug 2097406 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677398 Title: Apparmor prevents using storage pools and hostdev networks To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1677398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
