On 16/05/16 11:48, "Peter Krempa" <pkrempa(a)redhat.com> wrote:
On Mon, May 16, 2016 at 08:20:57 +0000, Dmitry Mishin wrote:
> ping
>
> On 25/04/16 14:16, "Dmitry Mishin" <dim(a)virtuozzo.com> wrote:
>
> >If one wants to monitor 'drive-backup' command progress and completion,
> >he needs a constant to recognize that. Right now, libvirt reports such
> >block jobs as 'unknown'.
Since libvirt currently doesn't support starting a block backup job
what's the motivation for doing this?
I think we should add stuff like this along with the implementation
itself since it may become apparent that something is missing what is
not clear at this point.
This is a simple define, which allows to filter this job by
ID for
third-party management
apps. What could be missed here?
Right now, there is a possibility to start this job via
virtDomainQemuMonitorCommand(),
get status via virtDomainGetBlockJobInfo(), but the problem is that in the
latter case,
job type is listed as "unknown" - and exactly this problem is solved by
this simple patch.
I'd like to know, that I track backup job, rather than something else.
Thank you,
Dmitry.
Peter