WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] capturing a dom0 corefile

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] capturing a dom0 corefile
From: Don Zickus <dzickus@xxxxxxxxxx>
Date: Tue, 21 Mar 2006 10:50:41 -0500
Delivery-date: Tue, 21 Mar 2006 23:07:54 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
I was trying to look at how a corefile for dom0 could be captured by the
hypervisor when the dom0 kernel on linux panics.  

Is it difficult to start another dom0 kernel, which in turn would run the
userspace tools to collect the memory contents of the original dom0
kernel?  Or even better, can I start a backup dom0 by loading and pausing
it and upon the first dom0 panicing, unpause the backup?

I know lots of people have talked about dom0 failovers and how
straightforward they should be.  But before I started hacking away, I
wanted to understand the right direction.  

Any thoughts or suggestions would be great.

Cheers,
Don


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] capturing a dom0 corefile, Don Zickus <=