After having slept on that for a night I consider that not a good way.
The current lifecycle of virt-aa-helper just doesn't match to create a local 
virConnectPtr context, yet OTOH without one we can't translate the pool as the 
code that spawns the guest would.

Before I implement some useless code to be nack'ed for its misconception
I readed out to the libvirt devel mailing list outlining these issues
and hope that feedback from there unblocks me.

Going on with another virt-aa-helper bug until the discussion resolved.

[1]: https://www.redhat.com/archives/libvir-
list/2017-September/msg00557.html

** Changed in: libvirt (Ubuntu)
       Status: In Progress => Triaged

-- 
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

Reply via email to