This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] blktap: qcow2 image format support

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] blktap: qcow2 image format support
From: Kevin Wolf <kwolf@xxxxxxx>
Date: Thu, 21 Feb 2008 10:28:42 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 21 Feb 2008 01:20:25 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3E2ED8C.1430F%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C3E2ED8C.1430F%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20060911)
Keir Fraser schrieb:
> Is qcow2 so different from qcow1 that it really needs its own backend
> driver?

That's a good question. I am not really familiar with the qcow code but
I think I saw quite some differences. If you put enough effort on it,
you could probably get a single driver for both, but I can't really
estimate if it was a sensible thing to do.

The main reason why I did it this way is that it is the way qemu has
done it, so I just had to take and adapt their code. I'm not sure if it
is a good idea to diverge too much from the qemu code base.


Xen-devel mailing list