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


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

To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Patch][RFC] Support "xm dump" (is Re: [Xen-devel] Re: [Patch]Enable "sysrq c" handler for domU coredump)
From: "Graham, Simon" <Simon.Graham@xxxxxxxxxxx>
Date: Thu, 3 Aug 2006 10:45:05 -0400
Delivery-date: Thu, 03 Aug 2006 07:45:36 -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
Thread-index: Aca2/NJZtwZj2yUmQMiUq9G8AmHiqwADOfvA
Thread-topic: [Patch][RFC] Support "xm dump" (is Re: [Xen-devel] Re: [Patch]Enable "sysrq c" handler for domU coredump)
Two things:

1. I'm not convinced 'xm crash' is needed - 'xm destroy' will do this
(and if you want
   a dump, do 'xm dump' followed by 'xm destroy')

2. I don't see the point of the --noreboot option on 'xm dump' -- I
think this command
   should simply live-dump the specified domain - as above you can use
other commands
   to cause the domain to restart afterwards.

3. There's no need to pause the domain to dump it - I actually wrote a
little utility
   to live dump a guest (based on xenconsoled and attached) and it seems
to work
   quite nicely! This could easily be morphed into the 'xm dump' command
- it just
   didn't occur to me at the time!


> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Akio Takebe
> Sent: Thursday, August 03, 2006 8:57 AM
> To: Tristan Gingold; John Levon; Keir Fraser
> Cc: Muli Ben-Yehuda; Horms; Akio Takebe; xen-devel; Kouya Shimura
> Subject: Re: [Patch][RFC] Support "xm dump" (is Re: [Xen-devel] Re:
> [Patch]Enable "sysrq c" handler for domU coredump)
> 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

Attachment: xendump.c
Description: xendump.c

Xen-devel mailing list