--On 12 December 2011 10:48:43 +0100 Kevin Wolf wrote:
I was testing on:
amb@alex-test:~$ qemu-img --version
qemu-img version 0.12.3, Copyright (c) 2004-2008 Fabrice Bellard
That's the problem. It should work since 0.13.
Thanks
--
Alex Bligh
Am 11.12.2011 11:45, schrieb Alex Bligh:
>
>
> --On 8 December 2011 13:40:57 +0100 Kevin Wolf wrote:
>
>>> qemu-img convert appears to support block devices as input, but not
>>> as output. That is irritating, as when using qemu-img convert to
>>> convert qcow to raw on a block partition, an in
--On 8 December 2011 13:40:57 +0100 Kevin Wolf wrote:
qemu-img convert appears to support block devices as input, but not
as output. That is irritating, as when using qemu-img convert to
convert qcow to raw on a block partition, an intermediate file has
to be used, which slows things down and
Am 06.12.2011 17:20, schrieb Alex Bligh:
> qemu-img convert appears to support block devices as input, but not
> as output. That is irritating, as when using qemu-img convert to
> convert qcow to raw on a block partition, an intermediate file has
> to be used, which slows things down and pointlessl
--On 6 December 2011 19:42:26 +0100 Christoph Hellwig wrote:
Is it therefore worth skipping the ftruncate() if the block device
is large enough, and at least attempting to proceed further? Something
like the following (not-even compile tested) patch?
It probably should share the code with r
On Tue, Dec 06, 2011 at 04:20:56PM +, Alex Bligh wrote:
> qemu-img convert appears to support block devices as input, but not
> as output. That is irritating, as when using qemu-img convert to
> convert qcow to raw on a block partition, an intermediate file has
> to be used, which slows things
qemu-img convert appears to support block devices as input, but not
as output. That is irritating, as when using qemu-img convert to
convert qcow to raw on a block partition, an intermediate file has
to be used, which slows things down and pointlessly uses disk space.
The problem is that ftruncat
