From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julian Chesterfield <julian@xensource.com>
Subject: Re: COW in Xen
Date: Tue, 06 Mar 2007 10:18:06 +0000
Message-ID: <45ED3FDE.7070207@xensource.com>
References: <E1HOJ6k-0004Jk-8f@host-192-168-0-1-bcn-london>	<7986CEFCE5C2954A88BEE2CAB6FAB374019EA9BC@SAUSEXMB2.amd.com>
	<45ED3A37.5010604@rrze.uni-erlangen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45ED3A37.5010604@rrze.uni-erlangen.de>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Marcel Ritter <Marcel.Ritter@rrze.uni-erlangen.de>
Cc: markryde@gmail.com, xen-devel@lists.xensource.com, "Rendon,
	Curtis" <Curtis.Rendon@amd.com>
List-Id: xen-devel@lists.xenproject.org

Marcel Ritter wrote:

>Rendon, Curtis schrieb:
>  
>
>>Hello,
>>
>>I had posted this question in Xen-user mailing list three 
>>days ago and I did not
>>get a single answer. On a second thought, maybe xen-devel is more
>>appropriate so
>>I am trying again in the hope that I will receive an answer:
>>
>>Does anybody have an experience (good or bad) with using
>>COW (Copy-On-Write) storage in Xen ?
>>  
>>
>>I've been using qcow images generated by qemu-img for Linux and
>>MSWIndows HVM guests, and I've been getting good results. The image
>>files are much smaller that the equivalently sized raw images.
>>
>>I simply create them (via gemi-img create -f qcom 10G) and use the
>>disk=['file:...'] line in my guest configuration files.
>>  
>>    
>>
>If I got Mark right, it's not the image type qcow itself, he's
>interested in,
>but the COW (Copy-on-write) feature. Some time ago I tried to get
>COW working with qcow images, without success. So I guess the name
>is missleading, and (in Xen) there's no COW based on qcow.
>  
>
Not true. CoW functionality is supported in the current blktap driver. 
If you create a qcow disk on the host using qcow-create with a backing 
filename argument (can be either a raw image or block device) the driver 
opens the backing file for reading-only and directs all writes to the 
qcow child image.

- Julian