similar to: [PATCH] SIGTERM and SIGINT handler to flush xentop -b outputs

Since TRC_MEM is defined as 0x000af000 in xen/include/public/trace.h, TRC_MEM = TRC_SCHED | TRC_VMX. I feel strange about this. I do not think scheduling is a part of memory management. Am I right? If not, please tell me the background TRC_MEM is defined as TRC_SCHED | TRC_VMX. If so, please apply this patch. This patch defines TRC_MEM as an independent event mask. In addition, xentrace

Hi Keir, Attached patch gets rid of the global attr variable and adds support for NetBSD. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht

Hi all, the throughput measured by netperf differs from time to time. The changeset was xen-unstable.hg C/S 11760. This is observed when I executed a netperf on DomU connecting to a netserver on Dom0 in the same box. The observed throughput was between 185Mbps to 3854Mbps. I have never seen such a difference on ia64. Regards, Hiroya _______________________________________________ Xen-devel

Fixed typos in xmexamples. Signed-off-by: Hiroya INAKOSHI <inakoshi.hiroya@jp.fujitsu.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, this patch makes Xen boot with the default dom0_mem value when the given value exceeds available memory, instead Xen panics and reboots. Administrators have a chance to correct dom0_mem (and other parameters if necessary) after Xen is up with default, seeing the warning message. Tested by booting Domain-0. Signed-off-by: Hiroya INAKOSHI <inakoshi.hiroya@jp.fujitsu.com>

This patch fixes the problem with xentop where it returns an exit code of 0 when passing it invalid options when it should return 1. The issue comes from getopt() returning ''?'' and the case from switch matching it. The solution was to remove the case ''?'' so that the default match could be triggered. Quote from `man 3 getopt` "If getopt() does not

# HG changeset patch # User john.levon@sun.com # Date 1172534164 28800 # Node ID 37fce3c0c10baee370ecc39b6a50fed8b232bd69 # Parent 4998793aa87729fbe8a582faa3a22c9ecfefe13c Fix for Solaris compile/output for VBDs in xentop. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/xenstat/xentop/xentop.c b/tools/xenstat/xentop/xentop.c --- a/tools/xenstat/xentop/xentop.c +++

Package: xen-utils-common Version: 3.0.3-0-2 Severity: wishlist Tags: patch Currently when hostnames are wider than 10 chars, the xentop output is messed up. Please add the following patch to support up to 20 chars, or better yet, allow the columns to auto size :) #! /bin/sh /usr/share/dpatch/dpatch-run ## xentop-name-width.dpatch by <apeeters@lashout.net> ## ## All lines beginning with

On my system, I''m getting SIGSEGVs in xentop because xenstat_node_domain() is returning NULL. Skip the loop if it does rather than crashing. Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r 9dda78d7af3b -r 5895ad758076 tools/xenstat/libxenstat/src/xenstat_linux.c --- a/tools/xenstat/libxenstat/src/xenstat_linux.c Tue May 18 15:38:36 2010 -0700 +++

This patch make xentop output statistics about both blkback and blktap. And, xentop also display back-end driver type in detail view mode. # HG changeset patch # User s-uchida@ap.jp.nec.com # Date 1180665749 -32400 # Node ID 1b36d6f6c7a98728382de93ee23c8c97b0b95dbd # Parent 1768a89bb87824249827d935d7803d8193bdeb05 XENTOP: Displaying blktap information. Signed-off-by: Satoshi UCHIDA

Hello to all, Does anyone know if there is an iteration option planned for xentop (similar to top) to make it easier for simple shell scripts to scrape the output? I don''t see one in tools/xenstat/xentop/xentop.c , but I''ve been meaning to play with stuff in libxenstat anyway. If its going to be added soon I''ll tinker much later than sooner. TIA :) Best, -Tim

I am running xen 3.2-1 (Debian 3.2.1-2) on Debian Lenny (2.6.26-2-xen-amd64 #1 SMP Wed Mar 10) on two identical production systems. This morning on one of the systems, xentop stopped displaying. Running xentop results in: unable to open xenstore : Connection refused Failed to initialize xenstat library xm list: Error: (9, ''Bad file descriptor'') xm dmseg: Error: Subcommand

xentop "-b" options are duplicateded(--batch and --vbds). from xen-unstable 10623 Please fix it. http://xenbits.xensource.com/xen-unstable.hg?cs=856caf975abd Thanks, Atsushi SAKAI _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Xentop encounters error in pv-ops domain0, because the VBD path in sysfs changes to "/sys/devices" Also delete the macro in xenstat_netbsd.c, because it is not used. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Best Regards, -- Dongxiao _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Just downloaded the xen-unstable and updated it using mercurial. When i try to do a make install on a Celeron D 64bit processor, i get the following error: xentop.c:291: error: `KEY_DOWN'' undeclared (first use in this function) xentop.c:294: error: `KEY_UP'' undeclared (first use in this function) xentop.c:314: error: `KEY_BACKSPACE'' undeclared (first use in this

Hi I seem to be having a little trouble with libxenstat, and was wondering if the xenstat guys might be able to help. I''ve pulled the xen-unstable.hg tree and done a somewhat clean install (ie, post-make uninstall, as well as deleting the relevant libxenstat libraries). Next, I entered the tools/xenstat/libxenstat directory and modified the Makefile so that the shared libraries would

Just moving a chunk of files from one filesysstem on xvba to another on xvdb, and was monitoring with xentop as it was taking longer than expected. The VBD_RD and VBD_WR counters were both clocking-up as expected, as was the VBD_RSECT counter, but the VBD_WSECT counter was stuck on zero, I toggled on the individual VBD device counters and these showed the same (with the RD and WR counters

Just moving a chunk of files from one filesysstem on xvba to another on xvdb, and was monitoring with xentop as it was taking longer than expected. The VBD_RD and VBD_WR counters were both clocking-up as expected, as was the VBD_RSECT counter, but the VBD_WSECT counter was stuck on zero, I toggled on the individual VBD device counters and these showed the same (with the RD and WR counters

# HG changeset patch # User john.levon@sun.com # Date 1161090130 25200 # Node ID afeef751f9dafa771726bcfb00b29a10b0baeabd # Parent 7147e57f18552bbb8d25155cc1c635315283ee31 On Solaris, GCC is configured to use Sun''s LD. Fix the build to use the correct flags, and link against libsocket where necessary. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/config/Linux.mk

When xenstat library parse /proc/net/dev, it uses strpbrk function to get pointer to device name. However, it miss capital letters in the array of valid characters so it get incorrect name in case device name starts with capital letters or even segfault if it contains only capital letters. This patch adds missing characters to strpbrk call. Signed-off-by: Miroslav Rezanina