search for: xm_info

Displaying 6 results from an estimated 6 matches for "xm_info".

Did you mean: x_info
2005 Dec 26
1
[PATCH] symmetricalization of system info command xm info, top, dmesg and log
...ujitsu.com> Best Regards, Yoshinori Katase diff -r 829517be689f tools/python/xen/xm/main.py --- a/tools/python/xen/xm/main.py Fri Dec 23 15:42:46 2005 +++ b/tools/python/xen/xm/main.py Mon Dec 26 10:16:56 2005 @@ -625,6 +625,8 @@ server.xend_domain_cpu_sedf_set(dom, *v) def xm_info(args): + arg_check(args, "info", 0) + from xen.xend.XendClient import server info = server.xend_node() @@ -645,9 +647,12 @@ def xm_top(args): + arg_check(args, "top", 0) + os.execvp(''xentop'', [''xentop'']) def xm_dmesg...
2010 Dec 15
6
about Fedora13 Xen 4 Tutorial
Hi This is my first question.. (sorry for my poor english.. ) Is this right way to ask something about installing xen, build kernel ...etc using mailing list?? I want know "How or Where can I ask something & How can I get your smart answers" I have followed this tutorial " http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial" exactly on my Core 2 Dou. after config the
2010 Dec 15
6
about Fedora13 Xen 4 Tutorial
Hi This is my first question.. (sorry for my poor english.. ) Is this right way to ask something about installing xen, build kernel ...etc using mailing list?? I want know "How or Where can I ask something & How can I get your smart answers" I have followed this tutorial " http://wiki.xen.org/xenwiki/Fedora13Xen4Tutorial" exactly on my Core 2 Dou. after config the
2007 Oct 19
4
[PATCH] nr_cpus calculation problem due to incorrect sockets_per_node
Testing on an 8-node 128-way NUMA machine has exposed a problem with Xen''s nr_cpus calculation. In this case, since Xen cuts off recognized CPUs at 32, the machine appears to have 16 CPUs on the first and second nodes and none on the remaining nodes. Given this asymmetry, the calculation of sockets_per_node (which is later used to calculate nr_cpus) is incorrect:
2006 Mar 07
8
[PATCH] xm,xend: flesh out xm sched-sedf
...= server.xend_domain_cpu_sedf_set(d[''dom''], *v) + if int(rv) != 0: + err("Failed to set sedf parameters (rv=%d)."%(rv)) + + # not setting values, display info + else: + print_sedf(sedf_info) + def xm_info(args): arg_check(args, "info", 0) diff -r f14e12b3327a tools/xm-test/tests/sedf/Makefile.am --- a/tools/xm-test/tests/sedf/Makefile.am Tue Mar 7 23:09:23 2006 +++ b/tools/xm-test/tests/sedf/Makefile.am Tue Mar 7 17:18:16 2006 @@ -1,7 +1,9 @@ SUBDIRS = -TESTS = 01_sedf_multi_po...
2006 Aug 01
18
[Patch] Enable "sysrq c" handler for domU coredump
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).