similar to: [PATCH] xenmon: remove magic number "31" (the idle domain)

Hi, This patch adds the argument check of "--ms_per_sample=" option. For "--ms_per_sample=", a negative value should be invalid. e.g. % xenmon.py -n --ms_per_sample=-1 usage: xenmon.py [options] xenmon.py: error: option --ms_per_sample: invalid negative value: ''-1'' Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> -- KUWAMURA

Hi, I made a patch for GPT support. As you see, this patch uses ad-hoc approach. If you give me an advice, it would be appreciated Signed-off-by: Shinya Kuwamura <kuwa@jp.fujitsu.com> Signed-off-by: Tomohiro Takahashi <takatom@jp.fujitsu.com> Thanks, Tomohiro Takahashi. diff -r 1bde28f762a6 -r 8e08fd1ffa24 tools/pygrub/src/pygrub --- a/tools/pygrub/src/pygrub Mon Apr 09 13:40:25

Hi, If `hda'' is used in a domain config file and domain-0 has /dev/hda, creating the domain failed by TypeError: File "//usr/lib/python/xen/xend/server/blkif.py", line 84, in getDeviceDetails (device_path, devid) = blkif.blkdev_name_to_number(dev) TypeError: unpack non-sequence Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> -- KUWAMURA

Hi, I read about RPC interface for xenmon in this presentation: www.xensource.com/files/xs0106_xenmon_brief.pdf Has such interface been implemented yet by anyone? Thanks, -- Jayesh ------------------------------------------------------------------------ Everything you can imagine is real _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Once Xen calculates nr_nodes properly, all nr_cpu calculations based on nr_nodes * sockets_per_node * cores_per_socket * threads_per_core are broken. The easy fix is to replace those calculations with a new field, nr_cpus in physinfo which is calculated by num_online_cpus(). This patch does so and attempts to change all users over to nr_cpus field in physinfo. This patch touches

Attached is the second release of XenMon, which is a unique performance monitoring tool for Xen. Instead of using hypervisor calls to get domain information, we use the xentrace facility to provide fine-grained monitoring of various metrics (see README below). We have written up a small case study that demonstrates the usefulness of the tool and the metrics that it reports. This will be

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-2 For some reason, xenmon.py is not in the search path - maybe an issue of the wrapper used by the xen Debian packages seems to be only a link to the wrapper is missing the program exists in the package xen-utils-3.0.3-0-2 and the follwoing make it work: ln -s ../lib/xen-common/bin/xen-utils-wrapper /usr/sbin/xenmon.py ln -s

flight 8091 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8091/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-intel 12 guest-localmigrate/x10 fail REGR. vs. 8071 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-xl-pcipt-intel 9

flight 5856 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5856/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-xcpkern-i386-rhel6hvm-amd 5 xen-boot fail REGR. vs. 5691 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-win 16

flight 8111 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8111/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-rhel6hvm-amd 12 guest-localmigrate/x10 fail in 8104 REGR. vs. 8020 Tests which are failing intermittently (not blocking): test-amd64-i386-rhel6hvm-amd 11 guest-localmigrate.2 fail pass in 8104

flight 12413 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12413/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 4 xen-build fail REGR. vs. 12202 build-amd64-pvops 4 kernel-build fail REGR. vs. 12202 build-amd64-oldkern 4

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:

Dear list, as my Xen3 server is finaly becomming ready for production I was wondering if anyone has written a xen usage monitoring/logging tool? Something like xm top, but with continuose logging to a (rr)database. Or a munin plugin? I can''t remember seeing anything simmilar on the list. BTW: where does xm top get the NETTX(k) and NETRX(k) from? For a munin plugin I''d

Hi, This patch fixes the following error: File "usr/lib/python2.4/site-packages/xen/xend/XendNode.py", line 974, in xenschedinfo sched_id = self.xc.sched_id_get() Error: (13, ''Permission denied'') Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> -- KUWAMURA Shin''ya _______________________________________________ Xen-devel mailing

Hi, 20827:fad80160c001 cannot be compiled on ia64: xentrace.c:647: error: ''PAGE_SIZE'' undeclared (first use in this function) This patch fixes it. Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Best regards, -- KUWAMURA Shin''ya _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, VT-i domains have two memory holes: VGA I/O (under 1MB) and MMIO (3GB-4GB). This patch calculates the correct memory size with them. # This is based on xen-unstable 10936:a0b3cf802d99. Original patch by Zhang xiantao <xiantao.zhang@intel.com> Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Best regards, -- KUWAMURA Shin''ya

Hi, The staging tree 19185:1eb6afcad849 cannot be compiled on ia64: vtd.c: In function `alloc_pgtable_maddr'': vtd.c:60: error: too few arguments to function `iommu_flush_cache_page'' The attached patch fixes it. Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Best regards, -- KUWAMURA Shin''ya

Package: xen-utils-3.0.3-1 Version: 3.0.3-0-3 Severity: grave Tags: security Justification: user security hole Xen versions 3.x, and 3.1 contain a tool for processing Xen trace buffer information. This tool uses the static file /tmp/xenq-shm insecurely allowing a local user to truncate any local file when xenbaked or xenmon.py are invoked by root. Sample session: # setup. skx

When running ./configure, I get the following error message: checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts

Hi, Can someone clarify for me the numbers that show up in Xenmon? Specifically, I''m curious about the "domain31" entry which always shows up. It looks like this represents the free resources. Also, does anyone know what would happen if more than 30 domain0''s were started (or more likely, I did enough migrations to raise the next domain ID to above 30)? Thanks for