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] Supporting large dump files

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Supporting large dump files
From: "Graham, Simon" <Simon.Graham@xxxxxxxxxxx>
Date: Wed, 7 Feb 2007 14:20:47 -0500
Delivery-date: Wed, 07 Feb 2007 11:20:26 -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
Thread-index: AcdK7RJJtPl94GRpSEKdn1e/9IomtA==
Thread-topic: Supporting large dump files
This may have come up before but I can't find it - with the default
build of Xen, libxc is built in a way that does not support large files
- this is a problem currently when attempting to dump domains larger
than 2GB - the dump eventually fails with:

[root@teller diag]# xm dump-core penn1
Dumping core of domain: penn1 ...
Error: Failed to dump core: (27, 'File too large')

My (admittedly limited) knowledge of this area leads me to the need to
define _FILE_OFFSET_BITS as 64; is there any issue with turning this on
for the tools/libxc build? Is there any other #define that should be
used instead of or in addition to this one?

Simon

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

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