FYI after some debugging I was chatting with libvirt upstream and setting up a new storage context inside virt-aa-helper really won't work architecturally.
But I've found as part of the same discussion that there is a chance we can move the profile load a bit back until after qemuProcessPrepareDomainStorage has translated the paths and modify virDomainDiskSourceFormat to render the translated paths.
There are some constraints and I've sent a mail to Jdstrand about this to clarify before I write code for this.
FYI after some debugging I was chatting with libvirt upstream and setting up a new storage context inside virt-aa-helper really won't work architecturally.
But I've found as part of the same discussion that there is a chance we can move the profile load a bit back until after qemuProcessPrep areDomainStorag e has translated the paths and modify virDomainDiskSo urceFormat to render the translated paths.
There are some constraints and I've sent a mail to Jdstrand about this to clarify before I write code for this.