From mboxrd@z Thu Jan 1 00:00:00 1970 From: Horms Subject: Re: [Patch] Enable "sysrq c" handler for domU coredump Date: Tue, 1 Aug 2006 12:48:24 +0900 Message-ID: <20060801034824.GD13414@verge.net.au> References: <4DC6B5182D2981takebe_akio@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4DC6B5182D2981takebe_akio@jp.fujitsu.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Akio Takebe Cc: xen-devel , Kouya Shimura List-Id: xen-devel@lists.xenproject.org On Tue, Aug 01, 2006 at 12:11:26PM +0900, Akio Takebe wrote: Content-Description: Mail message body > Hi, > > In the case of linux, crash_kexec() is occured by "sysrq c". > In the case of DomainU on xen, Help is occured by "sysrq c" now. > So The way of dumping DomainU's memory manualy is nothing. > > I fix this issue by the following way. > 1. Panic is occured by "sysrq c" on both Domain0 and DomainU. > 2. On DomainU, coredump is generated in /var/xen/dump (on Domain0). > On Domain0, crash_kexec() is called by panic() if implemented. > > I tested the below. > 1. vi /etc/xen/xend-config.sxp > (enabel-dump yes) > 2. xm create -c domU > echo 1 >/proc/sys/kernel/sysrq (on domU) > 3. xm sysrq domU c (on dom0) > 4. ls -lh /var/xen/dump > > Signed-off-by: Akio Takebe > Signed-off-by: Kouya Shimura That seems fine to me. Though there was some resistance to a patch I sent which adds a panic option to xen-console, which is the hypervisor equivalent of sysrq. Also, is this option really Xen specific. It seems it might be just as useful in regular Linux. -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/