On Wed, Nov 21, 2012 at 02:23:57PM +0100, Kevin Wolf wrote:
> @item qed
> -Image format with support for backing files and compact image files (when
> your
> -filesystem or transport medium does not support holes). Good performance due
> -to less metadata than the more featureful qcow2 format, especially with
> -cache=writethrough or cache=directsync. Consider using qcow2 which will soon
> -have a similar optimization and is most actively developed.
> +Old QEMU image format. Left for compatibility.
> +
> +For new images, use qcow2 instead. You might want to consider using the
> +@code{lazy_refcounts=on} option to get a more QED-like behaviour.
The first sentence should be kept, it describes the general feature set
and scope of this image format. I agree that the rest of the paragraph
can be dropped.
You could insert a statement saying that qcow2 is now preferred because
it is actively developed and offers advanced features and performance as
the very first sentence.
Stefan
