WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Hard 6 Meg limit on shared pages

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Hard 6 Meg limit on shared pages
From: James Pendergrass <James.Pendergrass@xxxxxxxxxx>
Date: Fri, 3 Nov 2006 12:19:28 -0500
Delivery-date: Fri, 03 Nov 2006 09:20:16 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I've been doing some stress testing on how much memory a domain can share (after a HD and a NIC front end). It seems that no matter what I set ORDER_GRANT_FRAMES (in xen/include/ asm/grant_table.h) and NR_GRANT_FRAMES (in linux-2.6-xen/include/xen/gnttab.h) to, attempting to share 6 megabytes or more from any one domain causes really terrible errors which very quickly corrupt the virtual hard disk (I have tried allocating up to 32 pages for the grant table and the problems persist).

A sample of the error messages generated by the kernel:
EXT2-fs error (device hda1): ext2_get_inode: unable to read inode block - inode=346073, block=688192
end_request: I/O error, dev hda1, sector 5737616
end_request: I/O error, dev hda1, sector 5505536
end_request: I/O error, dev hda1, sector 0
EXT2-fs error (device hda1): ext2_get_inode: unable to read inode block - inode=346073, block=688192
end_request: I/O error, dev hda1, sector 5737616
end_request: I/O error, dev hda1, sector 5505536
end_request: I/O error, dev hda1, sector 0
EXT2-fs error (device hda1): ext2_get_inode: unable to read inode block - inode=346073, block=688192

(sorry I can't get the first error message generated, it scrolls by too quickly and my terminals buffer fills up)

I've tried this on xen-3.0-testing.hg (3.0.2-3), and xen-unstable trees with the same results.

I have not managed to find any reason why this should be happening.
Is this a known issue?
Is there any additional information I can provide that would help track this down?

Thanks
-aaron

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

<Prev in Thread] Current Thread [Next in Thread>