From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Introducing the Xen Crashdump Analyser
Date: Wed, 20 Feb 2013 22:45:32 +0000
Message-ID: <5125520C.30500@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Xen-devel List <xen-devel@lists.xen.org>
List-Id: xen-devel@lists.xenproject.org

Hello,

About a year ago, I started writing a tool to analyse /proc/vmcore in
the case of Xen crash (given a kdump environment) and provide a report. 
The plan has always been to try and upstream it, and the main barrier
has been a lack of time on my part.

It was first released in XenServer 6.1 and has subsequently been
backported to some older versions, but I hereby formally present it to
the Xen community for comment.

Please read http://xenbits.xen.org/people/andrewcoop/ which contains
links to the source and instructions for use, as well as an example
report from a bug I am currently investigating (Scheduler race condition).

I would appreciate any feedback/queries/questions/suggestions.

Thanks,

~Andrew