Re: [libvirt] [PATCH v4 12/20] wip: backup: Parse and output backup XML

2019-02-28 Thread John Ferlan
[...] >> >> Ahh... so this is where it's referenced... I recall this from RNG... > > Which also raises the question of whether the RNG has to call it out, if > the only thing using it is internal code, or if the user will ever see > it. We have the interesting problem of outputting some

Re: [libvirt] [PATCH v4 12/20] wip: backup: Parse and output backup XML

2019-02-25 Thread Eric Blake
On 2/12/19 12:08 PM, John Ferlan wrote: > > > On 2/6/19 2:18 PM, Eric Blake wrote: >> Accept XML describing a generic block job, and output it again >> as needed. At the moment, it has some qemu-specific hacks, such >> as storing internal XML for a node name, that might be cleaner >> once

Re: [libvirt] [PATCH v4 12/20] wip: backup: Parse and output backup XML

2019-02-12 Thread John Ferlan
On 2/6/19 2:18 PM, Eric Blake wrote: > Accept XML describing a generic block job, and output it again > as needed. At the moment, it has some qemu-specific hacks, such > as storing internal XML for a node name, that might be cleaner > once full-tree node-name support goes in. > > Still not

[libvirt] [PATCH v4 12/20] wip: backup: Parse and output backup XML

2019-02-06 Thread Eric Blake
Accept XML describing a generic block job, and output it again as needed. At the moment, it has some qemu-specific hacks, such as storing internal XML for a node name, that might be cleaner once full-tree node-name support goes in. Still not done: decent tests Signed-off-by: Eric Blake ---