similar to: hang on restore in 3.3.1

Displaying 20 results from an estimated 1000 matches similar to: "hang on restore in 3.3.1"

2007 Feb 26
4
[PATCH][xentrace][HVM] introduce HVM tracing to unify SVM and VMX tracing
Hello, this patch introduces HVM tracing: one tracing class for both, SVM and VMX. It adds several new trace events. So we can differentiate between them in the xentrace formats file and format each event''s data items appropriately. With this patch the xentrace_format output is much more informative. The previous simple tracing in SVM and VMX is completely replaced. Unfortunately I
2007 Jul 27
2
how to use xentrace and xentrace_format
2008 Oct 22
24
Problems with enabling hypervisor C and P-state control
Hi, Is there any documentation on enabling hypervisor support for both C and P-state control? On xen-unstable and linux-2.6.18-xen.hg, if I enable cpuidle=1 on the xen command line and then run xenpm, I will get output for C-states (shown below) but it complains that "Xen cpufreq is not enabled!" cpu id : 0 total C-states : 2 idle time(ms) : 73264 C0
2007 Apr 05
2
Does xentrace write into buffers by default?
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
2006 Aug 18
2
[PATCH] xentrace event mask for memory management class
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
2009 Jan 07
4
xentrace and MSR_READ/MSR_WRITE
I am trying to learn some more about the way windows does TPR writes, and tried xentrace for the first time. I did ''xentrace --time-interval=5 xentrace.out'' to capture some data, and then ran it through ''xentrace_format'' using the supplied example defs file. I can see some PF_XEN entries with virt=0xFFFE0080 (address of TPR), but I want to know the value being
2010 May 03
1
xentrace
Hi, I've made some SAP benchmarks on my Xen system and discovered a huge difference in the performance of a "xened" SAP system compared to a native SAP system. Hence, I tried to figure out what might cause this 'overhead' and run a xentrace (listining to all events). Xentrace produced 24gb data and I converted it to 27gb human-readable data. After I gathered the
2011 Nov 16
1
Problem correlating TSC read from domU with Xentrace's TSC
Hi, I am trying to correlating performance issue in guest VM with the scheduling trace from Xentrace. User-mode application in guest VM periodically dump APIC ID and RDTSC into trace. I also start Xentrace in Dom0 during the same period. However, I notice that range of TSC values report both trace is completely disjointed. TSC values from Xentrace is always greater than what guest VM see, even
2006 Jul 31
1
[PATCH 5/6] xen, tools: calculate nr_cpus via num_online_cpus
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
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 Apr 15
1
xentrace failure...
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
2006 Jun 01
1
[PATCH] Make xentrace hypercall a bit more sane
xentrace, setsize and the hypervisor don''t seem to be on the same page. If tracing is not enabled, the hypercall will only allow TBUF_SET_SIZE and TBUF_ENABLE. However, set_size calls TBUF_GET_INFO, and xentrace wants to call TBUF_SET_EVT_MASK and TBUF_SET_CPU_MASK before calling TBUF_ENABLE. I don''t see any reason not to call SET_*_MASK and GET_INFO if tracing is not enabled.
2007 Jan 16
1
Bug#407143: Missing xentrace man page
Package: xen-utils-common Version: 3.0.3-0-2 Severity: minor xentrace(8) is missing and it seems there's one around: http://www.die.net/doc/linux/man/man8/xentrace.8.html -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash
2013 Aug 16
3
Bug#688308: installing some additional docs
tags 688308 +patch thanks A lot of /docs/ is pretty low-level and not all that interesting to be installed by the packages. However some of it is, and in particular some is referenced from the manpages. I've cherry-picked the bits which I think are most interesting in that context. Patch below. 8<--------------- commit 7f8ac283e684b7c713d52ed845cab0704a97abab Author: Ian Campbell <ijc
2006 Sep 29
4
[PATCH 4/6] xen: export NUMA topology in physinfo hcall
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
2013 Dec 03
7
[PATCH] xen: arm: Fixing ttbcr (TCR_EL1 for AArch64) size.
This patch fixes size of ttbcr register (TCR_EL1 in case of AArch64) and it''s programming considering size in case of context switch. Currently ttbcr is defined as 32b register but for AArch64 TCR_EL1 size is 64b. Signed-off-by: Anup Patel <anup.patel@linaro.org> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org> --- xen/arch/arm/domain.c | 8
2008 Aug 21
0
[PATCH]fix a little problem in formats file of xentrace
This patch (attached) fixes a small problem in xentrace_format. Signed-off-by: Yang Xiaowei <xiaowei.yang@intel.com> Zhou Ting <ting.g.zhou@intel.com> --- diff -r 0df3bf8aac1e tools/xentrace/formats --- a/tools/xentrace/formats Mon Jun 16 16:35:17 2008 +0100 +++ b/tools/xentrace/formats Thu Aug 21 17:36:03 2008 +0800 @@ -23,8 +23,8 @@ 0x00081001 CPU%(cpu)d
2011 Aug 03
9
Live VM migration
I have two hosts as Xen Server named host A and host B in the same network. A VM is created on Host A. Host A and B have a shared storage using NFS. While doing migration from host A to host B, how can I see the memory pages being migrated. If I run a small continuous program on the VM residing on host A, will the migration complete first or the sript running will complete first? How can I see
2011 Nov 03
3
[PATCH 0 of 2 RESEND] tools: add two new compile flags and perform checks on user defined folders.
Added two new sets of compile flags, and pass them to the check scripts, so libraries and includes are searched there also. Resend this patches because they suffered some modifications and where scattered along the mailing list. Please review, thanks Roger. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
2013 Aug 16
0
Bug#688308: Bug#688308: installing some additional docs
tags 407143 +patch thanks On Fri, 2013-08-16 at 14:42 +0100, Ian Campbell wrote: > tags 688308 +patch > thanks > > A lot of /docs/ is pretty low-level and not all that interesting to be > installed by the packages. However some of it is, and in particular some > is referenced from the manpages. I've cherry-picked the bits which I > think are most interesting in that