From mboxrd@z Thu Jan 1 00:00:00 1970 From: Don Slutz Subject: Re: kexec and kdump on Xen?? Date: Fri, 18 Apr 2014 08:50:16 -0400 Message-ID: <53511F88.4040002@terremark.com> References: <20140414081126.GA1632@router-fw-old.local.net-space.pl> <20140414132632.GA6173@router-fw-old.local.net-space.pl> <20140416111005.GA6251@router-fw-old.local.net-space.pl> <534FA3DB.3070103@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit 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: "Zhang, Yang Z" , Andrew Cooper Cc: "david.vrabel@citrix.com" , Daniel Kiper , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 04/17/14 21: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. 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? > Verizon is using the new 4.4 way to do kdump. So far all Xen/dom0 crashes have produced dumps. This is using an unchanged kernel 3.8.11-100.fc17.x86_64. -Don Slutz >> ~Andrew >> >> [1] We are aware of one hardware specific bug whereby the crash kernel >> fails to set up a timer interrupt. Investigating it is on my todo list. > > Best regards, > Yang > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel