From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Григорий Пташко" <grigory.ptashko@gmail.com>,
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: Fri, 17 Oct 2014 20:32:39 +0100 [thread overview]
Message-ID: <54416ED7.2030106@citrix.com> (raw)
In-Reply-To: <CAN=nNsgW0E19D_THQjSBdFq1NVu-zjatBQ6bQkgpZRn8yS23Gg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 964 bytes --]
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.
>
> 2. How am I supposed to diagnose the thing that causes such dom0 freezes?
> I thought that if I ask on the list that my dom0 freezes, it will be a
> waste
> of time without any logs or crash dumps.. But I cannot even make them..
On the serial console, if dom0 freezes, Xen should still be usable. use
CTRL-a three times.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 1865 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-10-17 19:32 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 [this message]
2014-10-19 9:51 ` Григорий Пташко
2014-10-19 11:30 ` Andrew Cooper
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=54416ED7.2030106@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.