From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [patch] crashkernel allocation failure #2
Date: Tue, 26 Jun 2007 08:54:50 +0200
Message-ID: <4680B83A.2060201@redhat.com>
References: <C2A5C753.11472%keir@xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C2A5C753.11472%keir@xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir@xensource.com>
Cc: Xen Development Mailing List <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Keir Fraser wrote:
> On 22/6/07 10:46, "Gerd Hoffmann" <kraxel@redhat.com> wrote:
> 
>> A side effect of the second change is that you can specify just
>> "crashkernel=64m" and have it moved to the right place just above the
>> xen heap automagically.
> 
> Does this really work in practice (i.e., is the crashkernel relocatable)?

Patches floating around for quite some time, i386 is mainline already. 
Not fully sure about x86_64, but I think it they are merged too.  So any 
recent mainline kernel as crash kernel should do (and a separate crash 
kernel isn't needed too).

Also with the default xenheap size the crashkernel ends up at @16m, 
which is a common location for pre-relocation crash kernels, so it 
should work with older kernels just fine too.  Of course you still have 
the option to explicitly specify the location ...

cheers,
   Gerd