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-devel] [PATCH] Fix xm dump-core for clustering systems

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH] Fix xm dump-core for clustering systems
From: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date: Fri, 04 Apr 2008 10:23:25 +0900
Delivery-date: Thu, 03 Apr 2008 18:24:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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

When a hang-up of a guest OS in a clustering system is occurred, I'd 
like to do fail-over to another in the clustering system, and collect 
a core dump of the guest OS by xm dump-core command with crash option. 
Then I'd like to destroy the guest domain after collecting the core 
dump of the guest OS. 
However, a processing of xm dump-core command destroys the guest domain 
after unpausing the guest domain. For the unpause, the guest OS might 
access disks after fail-over. 

I'd like to remove the possibility by this patch.  The patch gives 
higher priority to domain destructions by crash option than domain 

Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>

Best regards,

Attachment: xm_dumpcore.patch
Description: Binary data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] Fix xm dump-core for clustering systems, Masaki Kanno <=