similar to: [PATCH] unifying error message of migrate and sysrq

These xm info, top, dmesg and log requre no parameter. But log''s error message differs from other 3 command''s error messages, when parameter is given. # xm log 1 Error: ''xm log'' requires 0 argument. log Print the xend log Other 3 commands ignore parameter. I think it might be better symmetricalize. Signed-off-by: Yoshinori

This patch fixes error(help) messages in main.py and shutdown.py. 1.change the maximun number of argument for xm_reboot 2.unify error message for xm_shutdown Signed-off-by: Yoshinori Katase <y_katase@soft.fujitsu.com> Best Regards, Yoshinori Katase diff -r 1e1107e3d894 tools/python/xen/xm/main.py --- a/tools/python/xen/xm/main.py Wed Jan 11 19:14:27 2006 +++

Hi, Xm list and xm vcpu-list show wrong DomID(name). Under this situation, # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 512 1 r----- 1064.6 test1 13 64 1 r----- 83879.7 # xm list 1 13 Error: Domain ''1'' not found when running ''xm list'' # xm list

Hi, In the case of linux, crash_kexec() is occured by "sysrq c". In the case of DomainU on xen, Help is occured by "sysrq c" now. So The way of dumping DomainU''s memory manualy is nothing. I fix this issue by the following way. 1. Panic is occured by "sysrq c" on both Domain0 and DomainU. 2. On DomainU, coredump is generated in /var/xen/dump (on Domain0).

To make Btrfs code more robust, several return value checks where memory allocation can fail are introduced. I use BUG_ON where I don''t know how to handle the error properly, which increases the number of using the notorious BUG_ON, though. Signed-off-by: Yoshinori Sano <yoshinori.sano@gmail.com> --- fs/btrfs/compression.c | 6 ++++++ fs/btrfs/extent-tree.c | 2 ++

To make Btrfs code more robust, several return value checks where memory allocation can fail are introduced. I use BUG_ON where I don''t know how to handle the error properly, which increases the number of using the notorious BUG_ON, though. Signed-off-by: Yoshinori Sano <yoshinori.sano@gmail.com> --- fs/btrfs/compression.c | 6 ++++++ fs/btrfs/extent-tree.c | 4 ++++

Add new commands to manage SR-IOV device. Signed-off-by: Yu Zhao <yu.zhao@intel.com> diff -r b642e39d96cf tools/python/xen/util/pci.py --- a/tools/python/xen/util/pci.py Thu Sep 25 17:41:29 2008 +0100 +++ b/tools/python/xen/util/pci.py Sat Sep 27 01:08:05 2008 -0400 @@ -17,7 +17,7 @@ PROC_PCI_PATH = ''/proc/bus/pci/devices'' PROC_PCI_NUM_RESOURCES = 7

This cset: changeset: 11473:0008fca70351 date: Thu Sep 14 08:19:38 2006 +0100 description: xm dump command add on xm dump-core [-L|--live][-C| --crash] <domID> [output path] Didn''t actually implement anything. Worse, it looks like we don''t even pause the domain, so it''s always live (not good). What''s going on? regards john

Two things: 1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this (and if you want a dump, do ''xm dump'' followed by ''xm destroy'') 2. I don''t see the point of the --noreboot option on ''xm dump'' -- I think this command should simply live-dump the specified domain - as

> Hi, Simon > > >Two things: > > > >1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this > >(and if you want > > a dump, do ''xm dump'' followed by ''xm destroy'') > > > What do you mean? > I think we cannot dump with "xm destroy" now. >

We apologize for multiple receipts. -------------------------------------------------------------------------------- Eighth Real-Time Linux Workshop October 12-15, 2006 Lanzhou University - SISE Tianshui South Road 222 Lanzhou, Gansu 730000

This patch -Displays[1] current parameters for running domains ala xm list -Allow users to set[2] one or more parameters[3] without having to provide values for parameters they do not wish to change -Adds additional testing of sched-sedf via new xm-test testcases. With this patch applied, test 02_sedf_period_lower_neg.py exposes a bug[4]. I''ll follow up this email with a patch for

I am using CentOS 5.6 as a KVM host. My guests are running CentOS 5.6 with the only console being a virtual serial console. The guests are configured so magic-sysreq can be used to debug kernel issues. However, in order to send magic-sysrq from a serial port, I need to send a break. How does one send a break on the virtual console serial port provided by KVM/libvirt to guests? Thanks,

Hi all, Are there equivalent xe subcommands to ''xm sysrq'' and ''xm dump-core''? I looked up xe''s help message and hidden subcommands in source code but cannot find. -- Regards Yu Zhiguo _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I have a KVM guest running on CentOS 5.5 that is in a bad state. I would like to dump the kernel information using magic-sysrq commands, but I cannot figure out how to send a break on the virtaul serial port provided by "virsh console". The guest is a standard install that will respond if I can send a break on the virtual serial port. Is it possible to send a break on the virtual

Hi, I tried to test a wrong operation on purpose again. When I tried xm sysrq command to a inactive managed domain, I saw the following error message. The error message did not have a message text behind "Error:". And I found an AssertionError message in xend.log. # xm list PVdomain.1 Name ID Mem VCPUs State Time(s) PVdomain.1

Hello, Without using XM, is it safe to write the letter corresponding to the desired sysrq to xenstore in /local/domain/domid/control/sysrq ? Does anything else have to happen? I am working on some backup utilities that utilize the lvm2 library (liblvm2cmd) , libxenctrl and libxenstore. The program will issue a sysrq S to a guest, pause it, take a snapshot then unpause it (all very quickly). An

I am having trouble sending sysrq commands over USB serial, and I'm not sure what else to check. I have two identical machines, each with usb-to-serial adapters, joined by a null modem adapter. One runs an agetty, the other minicom. I can log in over the agetty as a user and it works as expected, until I try to send a sysrq. To send a break in minicom, I type [Ctrl]+[a] then [f]. Then I

Hi, is there some way to trigger sysrq from the serial console in xenlinux? With native linux it works by sending a break + sysrq letter, in xenlinux it doesn''t work that way though ... cheers, Gerd -- panic("it works"); /* avoid being flooded with debug messages */ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Package: asterisk Version: 1.6.2.0~dfsg~rc1-1 See below for issue: On Wed, 21 Oct 2009, Justin Piszcz wrote: > > > On Tue, 20 Oct 2009, Justin Piszcz wrote: > > >> >> >> On Tue, 20 Oct 2009, Dave Chinner wrote: >> >>> On Mon, Oct 19, 2009 at 06:18:58AM -0400, Justin Piszcz wrote: >>>> On Mon, 19 Oct 2009, Dave Chinner wrote: