On Mon, 01/16 13:26, Fam Zheng wrote:
> On Mon, 01/16 10:38, liujing wrote:
> > Dears,
> >
> > We would like to know if this patch will be pulled
> >
> > into upstream or what else we need to do for it?
> >
> > Because for upstream, the qemu-iotests case 055 still failed.
>
> Kevin, would you l
On Mon, 01/16 10:38, liujing wrote:
> Dears,
>
> We would like to know if this patch will be pulled
>
> into upstream or what else we need to do for it?
>
> Because for upstream, the qemu-iotests case 055 still failed.
Kevin, would you like to take this or should I do it?
Fam
>
> Thanks.
>
Dears,
We would like to know if this patch will be pulled
into upstream or what else we need to do for it?
Because for upstream, the qemu-iotests case 055 still failed.
Thanks.
Jing
On 12/16/2016 01:20 PM, QingFeng Hao wrote:
The problem was triggered by qemu-iotests case 055. It failed wh
The problem was triggered by qemu-iotests case 055. It failed when it
was comparing the compressed vmdk image with original test.img.
The cause is that buf_len in vmdk_write_extent wasn't converted to
little-endian before it was stored to disk. But later vmdk_read_extent
read it and converted it f
