I'm not sure if upstream likes that virt-aa-helper now needs to talk to the socket, but they can suggest otherwise if they don't. I now have something that calls the lookup correctly. It then fails to find the pool: libvirt: Storage Driver error : Storage pool not found: no storage pool with matching name 'internal'
While at the sametime $ ./tools/virsh pool-info internal Name: internal UUID: 9bdda23f-3410-4a2c-9f93-850308d19445 State: running Going on here tmrw -- 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 ZFS storage pools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1677398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
