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

Re: [Patch][RFC] Support "xm dump" (is Re: [Xen-devel] Re: [Patch] Enabl

To: Tristan Gingold <Tristan.Gingold@xxxxxxxx>, John Levon <levon@xxxxxxxxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Patch][RFC] Support "xm dump" (is Re: [Xen-devel] Re: [Patch] Enable "sysrq c" handler for domU coredump)
From: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Date: Thu, 03 Aug 2006 21:57:02 +0900
Cc: Muli Ben-Yehuda <muli@xxxxxxxxxx>, Horms <horms@xxxxxxxxxxxx>, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Kouya Shimura <kouya@xxxxxxxxxxxxxx>
Delivery-date: Thu, 03 Aug 2006 06:00:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200608031358.08031.Tristan.Gingold@xxxxxxxx>
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>
References: <20060801092622.GA28388@xxxxxxxxxxxx> <200608030809.33574.Tristan.Gingold@xxxxxxxx> <6DC6B6ED79944Atakebe_akio@xxxxxxxxxxxxxx> <200608031358.08031.Tristan.Gingold@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi, all

>>   For example panic dump option is used when domU kernel is hungup,
>>   and we want to reboot and make coredump atomatically.
>I'd prefer 'xm crash' (or 'xm panic') and 'xm dump' .
>I'd prefer 'xm dump' *not* to panic by default.  It is too dangerous.
>
OK. I also think both are necessary.
How about the following specification?

1. xm crash
   This is only for crashing a domain.
   If enable-dump is yes, we can get the domain's core after crash.
   And If we want to atomatically reboot, we should set on_crash='restart'
   in domain configuration.
   
2. xm dump
   This is for live dumping a domain.
   This implementation is:
     1. pause the domain
     2. dumping the domain
     3. unpause the domain
     4. reboot (if --noreboot option, don't reboot)
     
     I think we want to reboot when we want to dump.
     So I want to be default reboot.
     
   BTW, I think the feature to online-dump domain and 
   hypervisor is also necessary.(meaning online is "don't pause")
   
Best Regards,

Akio Takebe


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

<Prev in Thread] Current Thread [Next in Thread>