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: [Xen-devel] [PATCH][XEN]xm dump command add on

To: Ken Hironaka <hironaka.ken@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][XEN]xm dump command add on
From: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
Date: Mon, 14 Aug 2006 08:28:15 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 14 Aug 2006 05:28:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1155542639.4397.3.camel@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <1155542639.4397.3.camel@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
can we call this "xm core" or "xm crash"?
"dump" has so many meanings, I had plans to use it for "register" and "memory" dump, tho I think even those should have better names.
On Aug 14, 2006, at 4:03 AM, Ken Hironaka wrote:

This adds the xm dump command to xend.
The command outputs the memory contents of the specified domU to a
coredump file.
This will fail if tried on dom0.
The interface is as follows:

xm dump [-L][-C] <domID> [output path]

-L Live dump:By default, xm dump does an xm pause, unpause before and
after taking the dump, respectively. This option disables the
pause/unpause and simply takes the dump.

-C crash dump: This executes an xm destroy after the dump file is
The output path is optional, and if it is not specified, the path will
/var/xen/dump/<domU name>.<domU ID>.core

This command uses the existant dumpCore(), which has been used for
coredump when a domU crashed.
In this patch, the xc_domain_dumpcore_via_callback() in xc_core.c of
libxc is also modified. Previously, the
xc_domain_dumpcore_via_callback() did not respond to error when
copy_from_domain_page() failed. In other words, the dump core remained
silent even if mapping the domain memory failed and its page could not
be copied. When this happened, erroneous data had been dumped to the
file without the user realizing it. Now, it has been modified so that if
copy_from_domain_page fails, this fact is recorded in the logfile.
However even in such cases, the dumping will continue as before.

Signed-off-by: Ken Hironaka <hironaka.ken@xxxxxxxxxxxxxxxx>

http://lists.xensource.com/archives/html/xen-devel/2006-08/ msg00181.html http://lists.xensource.com/archives/html/xen-devel/2006-08/ msg00259.html http://lists.xensource.com/archives/html/xen-devel/2006-08/ msg00483.html
Xen-devel mailing list

Xen-devel mailing list