From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Graham, Simon" <Simon.Graham@stratus.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Supporting large dump files
Date: Wed, 7 Feb 2007 19:31:41 +0000 [thread overview]
Message-ID: <20070207193141.GB10502@redhat.com> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B3767104A69E56@EXNA.corp.stratus.com>
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 -=|
next prev parent reply other threads:[~2007-02-07 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 19:20 Supporting large dump files Graham, Simon
2007-02-07 19:31 ` Daniel P. Berrange [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-07 19:28 Ian Pratt
2007-02-07 19:41 Graham, Simon
2007-02-07 19:47 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070207193141.GB10502@redhat.com \
--to=berrange@redhat.com \
--cc=Simon.Graham@stratus.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.