Ken Hironaka
2006-Aug-16 08:24 UTC
[Xen-devel] [PATCH][XEN]xm dump command add on (TAKE 2)
This is a TAKE 2 to the xm dump-core command to xend. Changes: -the command name is now xm dump-core instead of xm dump -the command takes long options --live, and --crash. -with pause dump, the message that the domain will be paused has been taken out -when an interrupt is received during execution, the command will automatically unpause the domain in question. The below is basically the same info as before. ----------------------------------------------------------------- The command outputs the memory contents of the specified domU to a coredump file. This will fail if tried on dom0. The specification is as follows: xm dump-core [-L|--live][-C| --crash] <domID> [output path] -L| --live 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 crash dump: This executes an xm destroy after the dump file is complete. The output path is optional, and if it is not specified, the path will be /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> Reference 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 http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00742.html http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00831.html _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel