On 01/27/2015 12:48 PM, Eric Blake wrote:
> On 01/19/2015 03:01 PM, John Ferlan wrote:
>>
>
> Revisiting, now that the release is done.
>
>>
>> On 01/12/2015 05:54 PM, Eric Blake wrote:
>>> At least with live block commit, it is possible to have a block
>>> job that reports 0 status: namely, wh
On 01/19/2015 03:01 PM, John Ferlan wrote:
>
Revisiting, now that the release is done.
>
> On 01/12/2015 05:54 PM, Eric Blake wrote:
>> At least with live block commit, it is possible to have a block
>> job that reports 0 status: namely, when the active image contains
>> no sectors that differ
On 01/12/2015 05:54 PM, Eric Blake wrote:
> At least with live block commit, it is possible to have a block
> job that reports 0 status: namely, when the active image contains
> no sectors that differ from the backing image it is being committed
> into [1]. I'm not sure if that represents a qemu
At least with live block commit, it is possible to have a block
job that reports 0 status: namely, when the active image contains
no sectors that differ from the backing image it is being committed
into [1]. I'm not sure if that represents a qemu bug, but it leads
to weird virsh output where 'virs
