From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: kdump with xen-unstable on efi machine
Date: Wed, 26 Nov 2014 12:41:30 +0000 [thread overview]
Message-ID: <5475CA7A.7050200@citrix.com> (raw)
In-Reply-To: <5475C466.6010605@suse.com>
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
next prev parent reply other threads:[~2014-11-26 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 12:15 kdump with xen-unstable on efi machine Juergen Gross
2014-11-26 12:41 ` Andrew Cooper [this message]
2014-11-26 14:01 ` Juergen Gross
2014-11-26 14:26 ` Andrew Cooper
2014-11-27 9:49 ` Ian Campbell
2014-11-27 11:05 ` Andrew Cooper
2014-11-27 11:32 ` Ian Campbell
2014-11-27 11:51 ` Andrew Cooper
2014-11-26 14:30 ` Konrad Rzeszutek Wilk
2014-11-26 14:49 ` Juergen Gross
2014-11-27 0:19 ` Daniel Kiper
2014-11-27 5:40 ` Juergen Gross
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=5475CA7A.7050200@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jgross@suse.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.