Re: [libvirt] [PATCH 2/2] virDomainGetBlockJobInfo: Fix corner case when qemu reports no info

On 09/13/2016 06:02 AM, Michal Privoznik wrote: >> So, just to make it crystal clear, is this what you're saying? >> >> ready | initial C/R |fudged C/R > > Oh, This should have been C/E instead of C/R. Current/End. 'e' and 'r' > keys are just too close to each other :-) > >> ------+-------------+---------- >> < 0 | 0/0 | 0/0 >> = 0 | 0/0 | 0/1 >> > 0 | 0/0 | 1/1 Yes, I think that's the best. Then we have documented to apps higher in the stack that if they see 0/0, it is because qemu is too old to give us a definitive answer; in all other cases, we have fudged data so that higher layers don't have to worry about 0/0.