view docs/README.xen-bugtool @ 8697:11ed48af31d7

Ever since patchset 8648 (xen-unstable.hg) all my configuration files
fail with the following:

Error: Device 768 (vbd) could not be connected. Hotplug scripts not working.

(Since my HVM tree follows xen-unstable.hg closely, it breaks too).

The following patch undoes a small part of Ke Yu's patch and fixes the

However, I'm having trouble understanding what this part did in the
original patch. Was there a subtle change in the disk variable format
that I missed?

Signed-Off-By: Leendert van Doorn <leendert@watson.ibm.com>
author kaf24@firebug.cl.cam.ac.uk
date Sun Jan 29 10:52:43 2006 +0100 (2006-01-29)
parents d5368f7fda5d
line source
1 xen-bugtool
2 ===========
4 The xen-bugtool command line application will collate the Xen dmesg output,
5 details of the hardware configuration of your machine, information about the
6 build of Xen that you are using, plus, if you allow it, various logs.
8 The information collated can either be posted to a Xen Bugzilla bug (this bug
9 must already exist in the system, and you must be a registered user there), or
10 it can be saved as a .tar.bz2 for sending or archiving.
12 The collated logs may contain private information, and if you are at all
13 worried about that, you should not use this tool, or you should explicitly
14 exclude those logs from the archive.
16 xen-bugtool is wholly interactive, so simply run it, and answer the questions.