From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "david.vrabel@citrix.com" <david.vrabel@citrix.com>,
Daniel Kiper <dkiper@net-space.pl>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: kexec and kdump on Xen??
Date: Fri, 18 Apr 2014 17:26:05 +0100 [thread overview]
Message-ID: <5351521D.8070804@citrix.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AA97F6F@SHSMSX104.ccr.corp.intel.com>
On 18/04/14 02:45, Zhang, Yang Z wrote:
> Andrew Cooper wrote on 2014-04-17:
>> On 17/04/14 02:19, Zhang, Yang Z wrote:
>> As for real examples, XenServer unconditionally sets up a native
>> crash kernel and does use it in the case of a Xen/dom0 crash. It does
>> work reliably and repeatedly[1] and is routinely tested.
> I think XenServer uses the old approach to do the kexec.
Older versions of XenServer did. While investigating an issue, David
discovered quite how broken^W fragile it was and reimplemented the Xen
side, which is the code present in Xen 4.4
We then backported the Xen side fixes to XenServer 6.2, which otherwise
uses Xen 4.1.5 and 2.6.32-classic dom0.
Since doing so, I am not aware of a single customer crash report which
has arrived without proper set of crash logs, taken from the crash
environment.
> What I am trying is the new kexec/kdump feature which enabled in Xen4.4.
> One question, I remember kexec support is missing in 2.6.32-pvops kernel. If XenServer works well, do you know where can I find the patch to enable it for 2.6.32 kernel?
It is, but that is the point. The new Xen 4.4 code bypasses the dom0
kernel entirely, and /sbin/kexec uses a libxc interface for loading the
hypervisor crash/load images.
~Andrew
next prev parent reply other threads:[~2014-04-18 16:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 3:38 kexec and kdump on Xen? Zhang, Yang Z
2014-04-14 8:11 ` kexec and kdump on Xen?? Daniel Kiper
2014-04-14 8:15 ` Zhang, Yang Z
2014-04-14 13:26 ` Daniel Kiper
2014-04-15 2:13 ` Zhang, Yang Z
2014-04-16 11:10 ` Daniel Kiper
2014-04-17 1:19 ` Zhang, Yang Z
2014-04-17 9:50 ` Andrew Cooper
2014-04-18 1:45 ` Zhang, Yang Z
2014-04-18 12:50 ` Don Slutz
2014-04-18 16:26 ` Andrew Cooper [this message]
2014-04-17 10:01 ` David Vrabel
2014-04-22 10:14 ` David Vrabel
2014-04-15 6:57 ` Zhang, Yang Z
2014-04-14 9:51 ` kexec and kdump on Xen? David Vrabel
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=5351521D.8070804@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=dkiper@net-space.pl \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).