On Thu, 04/18 13:02, Stefan Hajnoczi wrote:
> On Thu, Apr 18, 2013 at 12:08 PM, Fam Zheng wrote:
> > On Thu, 04/18 09:39, Stefan Hajnoczi wrote:
> >> On Thu, Apr 18, 2013 at 03:08:55PM +0800, Fam Zheng wrote:
> >> > Currently VMDK block driver fails qemu-iotest case 042 because it
> >> > refuses t
On Thu, Apr 18, 2013 at 12:08 PM, Fam Zheng wrote:
> On Thu, 04/18 09:39, Stefan Hajnoczi wrote:
>> On Thu, Apr 18, 2013 at 03:08:55PM +0800, Fam Zheng wrote:
>> > Currently VMDK block driver fails qemu-iotest case 042 because it
>> > refuses to create block with zero size (silently). Is support f
On Thu, 04/18 09:39, Stefan Hajnoczi wrote:
> On Thu, Apr 18, 2013 at 03:08:55PM +0800, Fam Zheng wrote:
> > Currently VMDK block driver fails qemu-iotest case 042 because it
> > refuses to create block with zero size (silently). Is support for zero
> > size image desired or should this case be ski
On Thu, Apr 18, 2013 at 03:08:55PM +0800, Fam Zheng wrote:
> Currently VMDK block driver fails qemu-iotest case 042 because it
> refuses to create block with zero size (silently). Is support for zero
> size image desired or should this case be skipped?
>
> $ qemu-img create -f vmdk t.vmdk 0
>
Hi,
Currently VMDK block driver fails qemu-iotest case 042 because it
refuses to create block with zero size (silently). Is support for zero
size image desired or should this case be skipped?
$ qemu-img create -f vmdk t.vmdk 0
Formatting 't.vmdk', fmt=vmdk size=0 compat6=off
qemu-img
