From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Xen host crash Date: Fri, 30 Aug 2013 10:51:26 +0100 Message-ID: <52206B1E.5050307@citrix.com> References: <521F75E9.7060006@citrix.com> <521F7E98.3060706@citrix.com> <521F9DEE.60805@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3840715381970632075==" 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: Rushikesh Jadhav <2rushikeshj@gmail.com> Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org --===============3840715381970632075== Content-Type: multipart/alternative; boundary="------------070801070000030708050809" --------------070801070000030708050809 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit On 29/08/13 20:46, Rushikesh Jadhav wrote: > > > >> >> >> >> Having said that, you are using Xen 3.4 which is ages out of >> date, and in fact, probably using XenServer 5.6SP2 (so >> shouldn't be using xen-devel anyway). >> >> >> It is quite an old yet stable host with trusted guests. I wanted >> more information about Xen stack traces and whats the best way to >> read them hence sent on the list. >> >> Current crash did not generate a core dump, hence I tried >> crashdump analyzer from xenbits.xen.org >> on other core dumps but that fails with >> >> INFO Elf CORE crash file: /tmp/core.kdump.1405 >> ERROR Unexpected class 1 >> ERROR Failed to parse the crash file >> >> in xen-crashdump-analyser.log. > > There is a reason I threw kdump away and wrote the crashdump > analyser; It would crash all over the place. That crash file is > from the kdump utility, not from Xen. The crashdump analyser will > not be able to parse it. > > > I have only one binary dump file in each crash logs /var/crash/ > as core.kdump.1405. Rest all are .log files which does not seem to be > parsed by the github tool. Is there any other file I should be > looking at ? /proc/vmcore looks to be default file for tool but its > not present. /proc/vmcore only exists at the time of the crash. Is is a pseudo file which refers to the crashed memory of Xen at the time. It ceases to exist as soon as the soon as the server reboots. ~Andrew --------------070801070000030708050809 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
On 29/08/13 20:46, Rushikesh Jadhav wrote:

 
 

Having said that, you are using Xen 3.4 which is ages out of date, and in fact, probably using XenServer 5.6SP2 (so shouldn't be using xen-devel anyway).

It is quite an old yet stable host with trusted guests. I wanted more information about Xen stack traces and whats the best way to read them hence sent on the list.

Current crash did not generate a core dump, hence I tried crashdump analyzer from xenbits.xen.org on other core dumps but that fails with 

INFO  Elf CORE crash file: /tmp/core.kdump.1405
ERROR Unexpected class 1
ERROR Failed to parse the crash file

in xen-crashdump-analyser.log.

There is a reason I threw kdump away and wrote the crashdump analyser; It would crash all over the place.  That crash file is from the kdump utility, not from Xen.  The crashdump analyser will not be able to parse it.

I have only one binary dump file in each crash logs /var/crash/ as core.kdump.1405. Rest all are .log files which does not seem to be parsed by the github tool.  Is there any other file I should be looking at ?  /proc/vmcore looks to be default file for tool but its not present.

/proc/vmcore only exists at the time of the crash.  Is is a pseudo file which refers to the crashed memory of Xen at the time.  It ceases to exist as soon as the soon as the server reboots.

~Andrew
--------------070801070000030708050809-- --===============3840715381970632075== 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 --===============3840715381970632075==--