similar to: [PATCH] Fix error(help) messages in main.py and shutdown.py

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 unifys error messag of migrate and sysrq. Signed-off-by: Yoshinori Katase <y_katase@soft.fujitsu.com> Best Regards, Yoshinori Katase diff -r bfcdf4099d23 tools/python/xen/xm/migrate.py --- a/tools/python/xen/xm/migrate.py Thu Jan 12 13:27:55 2006 +++ b/tools/python/xen/xm/migrate.py Fri Jan 13 15:26:14 2006 @@ -56,8 +56,8 @@ if opts.vals.help: opts.usage()

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

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

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 ++++

Hi, this is my first post and contribution to Btrfs. I wrote a documentation on how to debug Btrfs with GDB on UML(User Mode Linux). https://btrfs.wiki.kernel.org/index.php/Debugging_Btrfs_with_GDB This document might be little bit boring for Btrfs hackers, but for beginners who want to join Btrfs development, it is worth reading, I think. (BTW, I''m a beginner, too :D) Thank you. --

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 ++

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

On Tue, 2002-04-30 at 15:12, Yoshinori K. Okuji wrote: > > Jean-Jacques pointed out a bug in GRUB and I've fixed it right now. So > the current CVS version should work with memdisk. Could you try? > > Thanks, > Okuji hi, okuji. that works great! thanks very much for your help. it might be worth mentioning memdisk in the documentation because i'm sure others would find

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 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

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).

flight 17325 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17325/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 9 guest-start fail REGR. vs. 12557 test-amd64-i386-xl-credit2 15 guest-stop fail REGR. vs. 12557 test-amd64-i386-xl 15 guest-stop

flight 17454 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17454/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-qemut-rhel6hvm-amd 7 redhat-install fail

flight 17612 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17612/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as allowable (not blocking): test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail

flight 17901 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17901/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-intel 4 xen-install fail REGR. vs. 12557 test-amd64-i386-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-pv 4

flight 17916 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/17916/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-pv 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl 4 xen-install fail REGR. vs. 12557 test-amd64-amd64-xl-win7-amd64 4

flight 18150 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18150/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18181 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18181/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as

flight 18805 linux-linus real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/18805/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12557 test-amd64-i386-pair 17 guest-migrate/src_host/dst_host fail REGR. vs. 12557 Regressions which are regarded as