Kevin Wolf kw...@redhat.com writes:
Am 13.04.2011 21:26, schrieb Prasad Joshi:
The patch only implements the basic read write support for QCOW version 1
images. Many of the QCOW features are not implmented, for example
- image creation
- snapshot
- copy-on-write
- encryption
Yay,
On Fri, Apr 15, 2011 at 9:41 AM, Markus Armbruster arm...@redhat.com wrote:
What hasn't been discussed much is the other half of Kevin's remark: why
QCOW1?
QCOW1 was simpler to implement as the first non-raw image format.
Pekka
--
To unsubscribe from this list: send the
On Fri, Apr 15, 2011 at 7:45 AM, Pekka Enberg penb...@kernel.org wrote:
On Fri, Apr 15, 2011 at 9:41 AM, Markus Armbruster arm...@redhat.com wrote:
What hasn't been discussed much is the other half of Kevin's remark: why
QCOW1?
QCOW1 was simpler to implement as the first non-raw image format.
On Fri, Apr 15, 2011 at 1:14 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
Why even use a non-raw image format? The current implementation only
does sparse files, but POSIX sparse raw files gives you the same
feature.
Because people have existing images they want to boot to?
--
To unsubscribe
On Fri, Apr 15, 2011 at 12:17 PM, Pekka Enberg penb...@kernel.org wrote:
On Fri, Apr 15, 2011 at 1:14 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
Why even use a non-raw image format? The current implementation only
does sparse files, but POSIX sparse raw files gives you the same
feature.
On Fri, Apr 15, 2011 at 3:05 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
People don't have existing QCOW1 images they want to boot from :).
They have vmdk, vhd, vdi, or qcow2. You can use qemu-img to convert
them to raw. You can use qemu-nbd if you are desperate to boot from
or inspect
