From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: kdump with xen-unstable on efi machine
Date: Wed, 26 Nov 2014 12:41:30 +0000
Message-ID: <5475CA7A.7050200@citrix.com>
References: <5475C466.6010605@suse.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <5475C466.6010605@suse.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Juergen Gross <jgross@suse.com>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 26/11/14 12:15, Juergen Gross wrote:
> Hi,
>
> I tried to enable kdump on my test-machine with actual xen-unstable
> booting via EFI.
>
> The kdump kernel is not being loaded.
>
> I'm seeing the memory being reserved:
>
> (XEN) EFI RAM map:
> (XEN)  0000000000000000 - 00000000000a0000 (usable)
> (XEN)  0000000000100000 - 000000004bc00000 (usable)
> (XEN)  000000004bc00000 - 000000005bc00000 (reserved)
> (XEN)  000000005bc00000 - 000000005bfec000 (usable)
> (XEN)  000000005bfec000 - 000000005c000000 (ACPI NVS)
> (XEN)  000000005c000000 - 000000006a429000 (usable)
> (XEN)  000000006a429000 - 000000006a42c000 (reserved)
> (XEN)  000000006a42c000 - 000000006a7a2000 (usable)
> (XEN)  000000006a7a2000 - 000000006a7a8000 (reserved)
> (XEN)  000000006a7a8000 - 000000006a987000 (usable)
> (XEN)  000000006a987000 - 000000006a98d000 (reserved)
> (XEN)  000000006a98d000 - 000000006aa63000 (usable)
> (XEN)  000000006aa63000 - 000000006aa73000 (reserved)
> (XEN)  000000006aa73000 - 000000006ac60000 (usable)
> (XEN)  000000006ac60000 - 000000006ac61000 (reserved)
> (XEN)  000000006ac61000 - 000000006ac9b000 (ACPI data)
> (XEN)  000000006ac9b000 - 000000006acac000 (reserved)
> (XEN)  000000006acac000 - 000000006acad000 (usable)
> (XEN)  000000006acad000 - 000000006acae000 (reserved)
> (XEN)  000000006acae000 - 000000007189c000 (usable)
> (XEN)  000000007189c000 - 0000000071946000 (reserved)
> (XEN)  0000000071946000 - 0000000072d76000 (ACPI NVS)
> (XEN)  0000000072d76000 - 0000000072db2000 (ACPI data)
> (XEN)  0000000072db2000 - 0000000072edc000 (usable)
> (XEN)  0000000080000000 - 0000000090000000 (reserved)
> (XEN)  0000000100000000 - 0000002080000000 (usable)
> (XEN) Kdump: 256MB (262144kB) at 0x206dff4000
>
> I'd expect this area being visible in the efi or e820 map presented to
> dom0, but I can't see anything:

This is expected.  The dom0 kernel now has nothing at all do with
loading crash kernel.  Loading happens via hypercalls straight from the
kexec utility.

You need kexec-tools 2.0.4 (I think) or later, compiled with Xen
support, but it should JustWork.

~Andrew