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/
Home Products Support Community News


[Xen-users] Xen: DomU Core Dump

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Xen: DomU Core Dump
From: aravindr <aravind.r@xxxxxxx>
Date: Mon, 24 May 2010 12:45:14 +0530
Delivery-date: Tue, 01 Jun 2010 09:26:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20090715 Thunderbird/3.0b3
Hello All,

I have a Linux (redhat) DomU(HVM) running on Xen-3.3.1 (on a CentOS Dom0).

In the config file for this DomU, I have configured

and started the DomU.

Inside the DomU I do a
echo 'c' > /proc/sysrq-trigger
and the DomU crashes with a kernel panic. But there is no coredump generated nor is the DomU restarted!
I have modified in /etc/xen/xend-config.sxp enable-dump to yes and restarted xend.

Since DomU is getting started properly shows that Xend has recognized the option but it does not dump core
when the DomU crashes. So is there something I am missing or is this broken ?

I did some digging in xen-users listings and found the below bug that says Fully Virtualized guests cannot communicate a panic to Xen and hence
there is no core generated by Xen for the crashed DomU.

So I tried the same " with a PVM(Linux redhat). And here also xen was not able to generate a core dump when the PVM kernel panicked.

I also wrote a small module which calls BUG() and panicks the kernel but same results, Xen is not able to determine that DomU has crashed.
Any thoughts, ideas?
So if anyone knows what I am missing here please point me in the right direction. Any help is greatly thanked :)

Best of Regards,

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xen: DomU Core Dump, aravindr <=