ia64/xen-unstable

view docs/README.xen-bugtool @ 15852:7dba4441bf92

xend: Fix error message for xm trigger command.

When I tested xm trigger command with a wrong argument, I saw the
following error message.

# xm trigger vm1 xyz
Error: __init__() takes exactly 2 arguments (3 given)
Usage: xm trigger <Domain> <nmi|reset|init> [<VCPU>]

Send a trigger to a domain.

This patch fixes the error message as follows.

# xm trigger vm1 xyz
Error: Invalid trigger: xyz
Usage: xm trigger <Domain> <nmi|reset|init> [<VCPU>]

Send a trigger to a domain.

The type of "TRIGGER_TYPE" is dictionary. domain_send_trigger()
refers to the keys of "TRIGGER_TYPE" without using keys() currently.
This patch adds keys() there.

Signed-off-by: Masaki Kanno <kanno.masaki@jp.fujitsu.com>
author kfraser@localhost.localdomain
date Fri Sep 07 11:24:28 2007 +0100 (2007-09-07)
parents d5368f7fda5d
children
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.