XML is taken via virDomainDefFormat from the contexts `virDomainDefPtr def` That is passed to virt-aa-helper as stdin.
These calls are from the same stack. In my example having the same object for the VM.
vm=0x7f92240444b0 which carries def=0x7f92380e9190 nto both calls and therby the same XML context it starts with (our issue).
qemuDomainSnapshotCreateDiskActive -> 2*qemuDomainSnapshotCreateSingleDiskActive
Since virt-aa-helper is external it doesn't know state, libvirt needs to pass that state from the labeling calls somehow.
XML is taken via virDomainDefFormat from the contexts `virDomainDefPtr def`
That is passed to virt-aa-helper as stdin.
These calls are from the same stack.
In my example having the same object for the VM.
vm=0x7f92240444b0 which carries def=0x7f92380e9190 nto both calls and therby the same XML context it starts with (our issue).
qemuDomainSnaps hotCreateDiskAc tive pshotCreateSing leDiskActive
-> 2*qemuDomainSna
Since virt-aa-helper is external it doesn't know state, libvirt needs to pass that state from the labeling calls somehow.