similar to: Bug#406863: xenmon.py isn't in the execution search path

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

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

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

Cycling around many CPUs in XenMon''s curses mode can get cumbersome. This trivial patch adds bindings to move to the previous CPU. The next/previous binding seems more natural to me than the earlier cycle binding, but we can keep them all for now. # HG changeset patch # Node ID 146b5c76086c07fad61bea7ccf60f2f4fd66abbd # Parent 7dd31dbf16e75f0f70e0f9c44b2bb2b5fc6eecf1 Add next/previous

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

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

Hi, This patch removes the magic number "31" for readability. The number "31" means the idle domain ID. In detail: - display the idle domain ID with "Idle" instead of "31" - write to the file "log-idle.log" instead of "log-dom31.log". Signed-off-by: KUWAMURA Shin''ya <kuwa@jp.fujitsu.com> Thanks, -- KUWAMURA

Hi, I have installed Xen 3.3.1 with Ubuntu 8.04 as dom0 and fedora9 (from jailtime.org) as Dom1. I have more instances of the same fedora9 with separate config files running as other guest domains. But these guest domains dont have any program / application running. So, xm list shows that they are in blocked state as no activity is happening. I wrote a shell script that counts upto large numbers

Hi, I have installed Xen 3.3.1 with Ubuntu 8.04 as dom0 and fedora9 (from jailtime.org) as Dom1. I have more instances of the same fedora9 with separate config files running as other guest domains. But these guest domains dont have any program / application running. So, xm list shows that they are in blocked state as no activity is happening. I wrote a shell script that counts upto large numbers

Hi list, I''m working on monitoring CPUs usage per domU, I/O.... using xenmon parsing its output and finally polling the results with cacti. Any advices? If all works OK I will post my work to the list. Thanks, Marc _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

In XenMon''s file appending mode, a lot of times I''ll get a strange first data point, e.g., the cpu% for dom0 will be 99.9 but the rest of the readings will be 19-21 which are sane for the run. I''ve been throwing the data point out, but was curious about it. Is it unavoidable? Thanks, Tim _______________________________________________ Xen-devel mailing list

# HG changeset patch # User john.levon@sun.com # Date 1155596263 -3600 # Node ID dc12f0942649ee27ff2aec3e3d9c2d99746b9e58 # Parent 09bc238664cb7b6d0f960f5e135ac80a75b342f1 Remove another external-to-libxc user of xc_dom0_op(). Signed-off-by: John Levon <john.levon@sun.com> diff -r 09bc238664cb -r dc12f0942649 tools/xenmon/xenbaked.c --- a/tools/xenmon/xenbaked.c Mon Aug 14 15:40:36 2006

This patch modifies the physinfo hcall to export NUMA CPU and Memory topology information. The new physinfo hcall is integrated into libxc and xend (xm info specifically). Included in this patch is a minor tweak to xm-test''s xm info testcase. The new fields in xm info are: nr_nodes : 4 mem_chunks : node0:0x0000000000000000-0x0000000190000000

Hi, I am using Xenmon to measure performance of Credit and SEDF schedulers. But as you know, the metrics displayed by xenmon keep refreshing on the screen. When I tried redirecting the xenmon output, I am seeing the attached file. Is there any better way to record results which I can use to draw graphs? Please guide.. Thank you Warm Regards Ananth

Hi, I am using Xenmon to measure performance of Credit and SEDF schedulers. But as you know, the metrics displayed by xenmon keep refreshing on the screen. When I tried redirecting the xenmon output, I am seeing the attached file. Is there any better way to record results which I can use to draw graphs? Please guide.. Thank you Warm Regards Ananth

Hi, All This is a patch for xentrace.c. This routine checks the trace buffer is initialized or not. If not, the trace buffer is initialized by using this patch. This is avoiding following message. ERROR: Failure to get trace buffer pointer from Xen (22 = Invalid argument) This routine is based on the specification of the trace buffer control function trace.c/tb_control(). The function checks

Hi all, I installed SLES 10.0b3 with XEN on some test-systems and created a SLES 10.0b3-image for use with domU''s. The installation and booting of this domU was no problem, but on some systems the host dom0 restarts if I generate some IP-traffic from the guest. This happens on an old AMD Athlon 1,3GHz, an old Intel P3 and an Intel desktop with P4 HT/VT/EM64T but not on an Intel

Hi, All! This is a patch which needs discussion. Currently xc_tbuf_enable assumed tb_init_done = 0. But Sometimes already on For example(xenmon.py(xenbaked) and xentrace). These two programs assues tb_init_done =0 at start time. Currently xenbaked care the problem by setting tb_init_done=0 at exit time. But xentrace does not care the problem. Then error occured!(Cannot see the trace

Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26 > reassign 406863 xen-common Bug#406863: xenmon.py isn't in the execution search path Bug reassigned from package `xen-utils-3.0.3-1' to `xen-common'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug