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
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 3410-4a2c- 9f93-850308d194 45
$ ./tools/virsh pool-info internal
Name: internal
UUID: 9bdda23f-
State: running
Going on here tmrw