similar to: [PATCH] Fix xc_tbuf_enable assumption.

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

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

Hello, I have a question about the way Xentrace takes a trace. In previous versions of Xen, I took a trace by setting the size of buffers, activating them and writing the information into a file (optional). setsize 20 tbctl 1 xentrace /tmp/xentrace.dat Now I''m using xen-unstable and I see that setsize is already integrated in xentrace command. My question is: does start/stop buffer is

I have a similar patch for this, which is generated in linux-2.6.16.33-xen/.config automatically. See attachment defbuild.patch. Pae_new_config is used to build x86_32 with PAE enabled. Ping >-----Original Message----- >From: xen-ia64-devel-bounces@lists.xensource.com [mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of Atsushi >SAKAI >Sent: 2006年12月4日 12:22 >To:

Hi, I am using xen-unstable and interested to trace the hypervisor. In previous versions, I was able to trace it by: setsize 20 tbctl 1 xentrace /tmp/xentrace.dat And these functions don''t exist in xen-unstable. xentrace --help shows that in more recent versions the buffers'' size could be determined as a parameter for xentrace. But I can not find any replacement for

Hi, It adds console_timestamps discription. Signed-off-by: Atsushi SAKAI <sakaia@jp.fujitsu.com> Anyway, Why Users'' manual version keeps Xen v3.0? Is there any reason? Thanks Atsushi SAKAI _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

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

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

This is a patch which intends for default scheduler changed in user''s manual. (from sedf to credit) Signed-off-by: Atsushi SAKAI <sakaia@jp.fujitsu.com> Request: Credit scheduler has no description on glossary of terms (user''s manual appendix C:P67) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

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

Package: xen-utils-4.1 Version: 4.1.4-4 Severity: normal User: mayhem at forallsecure.com Usertags: mayhem xenbaked crashes with exit status 139. We confirmed the crash by re-running it in a fresh debian unstable installation. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we

# 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

Hi, Xenmon does not work correctlly after xentrace changes in cs 17000. Attached patch fixes this problem. This patch modifies access to trace buffer same as tools/xentrace. Signed-off-by: Naoki Nishiguchi <nisiguti@jp.fujitsu.com> Regards, Naoki Nishiguchi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, We found a crash in xenbaked contained in the xen-utils-4.1 package. You are being contacted because your are listed as one of the maintainer of xen-utils-4.1. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will

Processing commands for control at bugs.debian.org: > reassign 745419 src:xen 4.1.4-3+deb7u1 Bug #745419 [xen-utils-4.1] xen-utils-4.1: Pygrub fails to boot from LVM LV when something installed in the volume boot record Bug reassigned from package 'xen-utils-4.1' to 'src:xen'. No longer marked as found in versions xen/4.1.4-3+deb7u1. Ignoring request to alter fixed versions of

Hello, I''ve been trying to get xenmon.py and xentrace to work, but I consistently get the following (on a couple of different machines/kernels): kibab kibab # xentrace /root/xentrace.log ERROR: Failure to get trace buffer pointer from Xen (22 = Invalid argument) Did I miss an option that has to be turned on or something? Is there some other setting that I need so that everything

>From: Keir Fraser >Sent: 2006年4月21日 14:41 > > >On 21 Apr 2006, at 02:31, Atsushi SAKAI wrote: > >> But the logical limit of the IA64 Max CPU is larger than 64. >> If someone change these values, some possibility make this error >again. >> >> To avoid this problem, I believe this check code should be exists. > >See how we solve this on x86 near

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

Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26 > reassign 447795 xen-3.0 3.0.3-0-3 Bug#447795: xen-utils-3.0.3-1: [CVE-2007-3919] xenmon.py / xenbaked insecure file accesss Bug reassigned from package `xen-utils-3.0.3-1' to `xen-3.0'. > End of message, stopping processing here. Please contact me if you

Processing commands for control at bugs.debian.org: > # Automatically generated email from bts, devscripts version 2.9.26 > found 447795 3.0.3-0-1 Bug#447795: xen-utils-3.0.3-1: [CVE-2007-3919] xenmon.py / xenbaked insecure file accesss Bug marked as found in version 3.0.3-0-1. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking