From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper 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 Message-ID: <54416ED7.2030106@citrix.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0927122144558778149==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: =?UTF-8?B?0JPRgNC40LPQvtGA0LjQuSDQn9GC0LDRiNC60L4=?= , Xen List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0927122144558778149== Content-Type: multipart/alternative; boundary="------------040006070705000305090505" This is a multi-part message in MIME format. --------------040006070705000305090505 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Length: 1033 Content-Transfer-Encoding: quoted-printable On 17/10/2014 19:17, =D0=93=D1=80=D0=B8=D0=B3=D0=BE=D1=80=D0=B8=D0=B9 =D0=9F=D1=82=D0=B0=D1=88=D0=BA=D0=BE wrote: > > So the questions are: > > 1. How can I make crash dumps of the hypervisor and the dom0=3F 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=3F > 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 --------------040006070705000305090505 Content-Type: text/html; charset=UTF-8 Content-Length: 1975 Content-Transfer-Encoding: quoted-printable On 17/10/2014 19:17, =D0=93=D1=80=D0=B8=D0=B3=D0=BE=D1=80=D0=B8=D0=B9 =D0=9F=D1=82=D0=B0=D1=88=D0=BA=D0=BE wrote:

So the questions are:

1. How can I make crash dumps of the hypervisor and the dom0=3F

Kexec of domains inside themselves is not supported.=C2=A0 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.=C2=A0 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=C2=A0 and running `kexek` manually ought to do the right thing.


2. How am I supposed to diagnose the thing that causes such dom0 freezes=3F
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.=C2=A0 use CTRL-a three times.

~Andrew --------------040006070705000305090505-- --===============0927122144558778149== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============0927122144558778149==--