[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] CoW works on Windows guest?


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • 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=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>


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.

--
Mats

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.