Re: [PATCH 0/2] Report block jobs more wisely

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Sep 05, 2016 at 01:48:21PM +0200, Michal Privoznik wrote:
> There's been a discussion recently (even here on the list [1])
> that Nova is sometimes unable to fetch block job stats properly.
> Basically, we may report job.cur == job.end == 0 in some cases
> tricking Nova into thinking job is done when in fact it hasn't
> even started yet.
> 
> Michal Privoznik (2):
>   qemuDomainGetBlockJobInfo: Move info translation into separate func
>   virDomainGetBlockJobInfo: Fix corner case when qemu reports no info
> 
>  src/libvirt-domain.c   |  7 ++++++
>  src/qemu/qemu_driver.c | 58 ++++++++++++++++++++++++++++++++++++--------------
>  2 files changed, 49 insertions(+), 16 deletions(-)

I've tested the obvious case and reported it in this thread:

    http://www.redhat.com/archives/libvir-list/2016-September/msg00042.html

FWIW:

    Tested-by: Kashyap Chamarthy <kchamart@xxxxxxxxxx>


-- 
/kashyap

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list



[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]