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: "Graham, Simon" <Simon.Graham@xxxxxxxxxxx>, "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: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>
Date: Fri, 04 Aug 2006 00:24:27 +0900
Delivery-date: Thu, 03 Aug 2006 08:27:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <342BAC0A5467384983B586A6B0B3767103470F5E@xxxxxxxxxxxxxxxxxxxxx>
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: <342BAC0A5467384983B586A6B0B3767103470F5E@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi, Simon

>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')
What do you mean?
I think we cannot dump with "xm destroy" now.
"xm destory" only call the following domain_kill().
void domain_kill(struct domain *d)

    if ( test_and_set_bit(_DOMF_dying, &d->domain_flags) )


    send_guest_global_virq(dom0, VIRQ_DOM_EXC);

Will anyone add crash option in "xm destory" in the feature?

>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.
Ordinary dump features have atomatically rebooting features.
(e.g. diskdump, kdump, and so on)
So I think this is necessary.

>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!
Your xendump command is dump feature without pause.
In the case without pause, domain's memory is modified while dumping. 
I think both w/o and w pause are needed.

Best Regards,

Akio Takebe

Xen-devel mailing list