All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Григорий Пташко" <grigory.ptashko@gmail.com>
Cc: Xen <xen-devel@lists.xen.org>
Subject: Re: kexec+kdump troubles on xen 4.5-unstable, centos 7, x86_64 (need to get a crash dump)
Date: Sun, 19 Oct 2014 12:30:28 +0100	[thread overview]
Message-ID: <5443A0D4.8070304@citrix.com> (raw)
In-Reply-To: <CAN=nNsiu_OezrzMCvn9cphFpfcZ8kvOQaz5wO1Mm6ybB5VFCXg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2063 bytes --]

On 19/10/2014 10:51, Григорий Пташко wrote:
>
>
> 2014-10-17 23:32 GMT+04:00 Andrew Cooper <andrew.cooper3@citrix.com
> <mailto:andrew.cooper3@citrix.com>>:
>
>     On 17/10/2014 19:17, Григорий Пташко wrote:
>>
>>     So the questions are:
>>
>>     1. How can I make crash dumps of the hypervisor and the dom0?
>
>     Kexec of domains inside themselves is not supported.  Effort is
>     being made to make it work, but there are some architectural
>     challenges.
>
>     The correct method is method 2, by providing a crash region in Xen
>     for dom0 to load into.  I suspect your problem is that systemd
>     doesn't understand that it is running in dom0, and is attempting
>     to load a normal crash kernel.
>
>     An up-to-date kexec-tools  and running `kexek` manually ought to
>     do the right thing.
>
>
> OK. I've tried it again. Here's my cmdline:
>
> APPEND xen.gz console=com1 com1=115200,8n1 crashkernel=256M iommu=1
> --- bzImage ignore_loglevel serial console=ttyS1,115200n8 ...

ttyS1 is the second serial console, not the first.  Xen should be using
com2 not com1 on the command line.

Linux should be configured to use hvc0 which will then be muxed by Xen
onto the serial.

This should now get you the Xen console ring on the serial as well.

>
> Here's what I see in dom0:
>
> [root@kvmxen-centos7-test1-nb admin]# xl dmesg | grep crash
> (XEN) Command line: console=com1 com1=115200,8n1 crashkernel=256M iommu=1
>
> [root@kvmxen-centos7-test1-nb admin]# kexec -p /boot/bzImage 
> Memory for crashkernel is not reserved
> Please reserve memory by passing "crashkernel=X@Y" parameter to the kernel
> Then try loading kdump kernel
>
> Here's the kexec's version (I built it from source rpm):
>
> [root@kvmxen-centos7-test1-nb admin]# kexec --version
> kexec-tools 2.0.4 released 17 October 2014

I don't know when that date is from, but kexec-tools 2.0.4 is much older
than that.  You want 2.0.5 or newer, which contains the Xen support.

~Andrew

[-- Attachment #1.2: Type: text/html, Size: 4587 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2014-10-19 11:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 18:17 kexec+kdump troubles on xen 4.5-unstable, centos 7, x86_64 (need to get a crash dump) Григорий Пташко
2014-10-17 19:32 ` Andrew Cooper
2014-10-19  9:51   ` Григорий Пташко
2014-10-19 11:30     ` Andrew Cooper [this message]

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=5443A0D4.8070304@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=grigory.ptashko@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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.