aboutsummaryrefslogtreecommitdiffstats
path: root/docs/README.xen-bugtool
diff options
context:
space:
mode:
authoremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>2005-11-28 12:20:33 +0000
committeremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>2005-11-28 12:20:33 +0000
commit951828c692ea34d6b850e5d06ca7e67851948752 (patch)
tree7f6a237de8815cea7dd48ac790c15193041e0efe /docs/README.xen-bugtool
parentdad18c78cb52afe5428abf5403725118a285e641 (diff)
downloadxen-951828c692ea34d6b850e5d06ca7e67851948752.tar.gz
xen-951828c692ea34d6b850e5d06ca7e67851948752.tar.bz2
xen-951828c692ea34d6b850e5d06ca7e67851948752.zip
Added README.xen-bugtool.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
Diffstat (limited to 'docs/README.xen-bugtool')
-rw-r--r--docs/README.xen-bugtool16
1 files changed, 16 insertions, 0 deletions
diff --git a/docs/README.xen-bugtool b/docs/README.xen-bugtool
new file mode 100644
index 0000000000..a7e95ef4ce
--- /dev/null
+++ b/docs/README.xen-bugtool
@@ -0,0 +1,16 @@
+xen-bugtool
+===========
+
+The xen-bugtool command line application will collate the Xen dmesg output,
+details of the hardware configuration of your machine, information about the
+build of Xen that you are using, plus, if you allow it, various logs.
+
+The information collated can either be posted to a Xen Bugzilla bug (this bug
+must already exist in the system, and you must be a registered user there), or
+it can be saved as a .tar.bz2 for sending or archiving.
+
+The collated logs may contain private information, and if you are at all
+worried about that, you should not use this tool, or you should explicitly
+exclude those logs from the archive.
+
+xen-bugtool is wholly interactive, so simply run it, and answer the questions.