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-users] CoW works on Windows guest?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] CoW works on Windows guest?
From: "Orathai Sukwong" <kobkob@xxxxxxxxx>
Date: Fri, 29 Sep 2006 12:54:50 -0400
Delivery-date: Fri, 29 Sep 2006 09:55:30 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=DdxLr3WDqOr7WRHxbjKNmFuzAey1TE07owZ9etmmbiGN+kFlUCKzl9U3CJkNcwrHzsT8Rwzb12Ok178MwsCpWNKLJRcGPTUT1iRId9NfcwZIYwqKcbR6UBFQMYQ2XU9ML31Hy+EoNkFsrkcYQHvHBeBRKeNNa/WWoBobOIJblzA=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0B018E15AB@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <748f85310609290908v387a45b4x9707e85bacc53dcb@xxxxxxxxxxxxxx> <907625E08839C4409CE5768403633E0B018E15AB@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

It would help (a little bit) to know the value and type of i, and the declaration of the dscow struct...

uint32_t i;

struct dscow {
        struct dscow_disk_header header;

        uint64_t blocks;
        uint32_t *bitmap;
        uint32_t bitmap_count;
        uint32_t *dirty_bitmaps;
        char *base_filename;

        int fd;
       int dirty;

That's not to say that it's possible from this to determine what the correct values should be or something, but at least it would help a little bit. The fact that it fails at 2.1GB tends to indicate that it's a 2^31 byte boundary problem, which could potentially be fixed with using unsigned rather than signed integer [give you 4GB].

I've tried several scenarioes:

2048000000 bytes (2.0 GB)  works fine.
3221225472 bytes (3.2 GB) gave me seg fault.
4096000000 bytes (4.1 GB) gave me seg fault again.

Is this on a 32- or 64-bit system?

My hardware is capable of 64 bit. However, I'm running 32 bit ubuntu 6.06 Dapper.


Xen-users mailing list