From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: Supporting large dump files Date: Wed, 7 Feb 2007 19:31:41 +0000 Message-ID: <20070207193141.GB10502@redhat.com> References: <342BAC0A5467384983B586A6B0B3767104A69E56@EXNA.corp.stratus.com> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <342BAC0A5467384983B586A6B0B3767104A69E56@EXNA.corp.stratus.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Graham, Simon" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Wed, Feb 07, 2007 at 02:20:47PM -0500, Graham, Simon wrote: > 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? What version of Xen are you using ? I submitted a patch to have this fixed many months ago, and I'm pretty sure it was incorporated in Xen 3.0.4 Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|