similar to: [PATCH 2/2] xm info (2)

This patch makes "xm info" show information on xen version, compile info, number of socket/core, etc... In order to do that, it extends physinfo hypercall to return number of socket, adds few functions to libxc and extends python wrapper correspondingly. Here is the output of new "xm info": -- system : Linux host : ubuntu xen_release

So that we can easily figure out whether or not we are running a debug build of Xen (e.g., via `xl dmesg''). Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com> --- Changes from v1: * moved the #ifndef-ery around variable definition; * repositioned the "debug=%c" outside of the ''compiled-by'' section. diff --git a/xen/drivers/char/console.c

During build of xen testing, there''s a minor warning that could get corrected: -- begin -- make[2]: Entering directory `/usr/local/src/xen/xen-2.0-testing.bk/xen'' tail: `-1'' option is obsolete; use `-n 1'' since this will be removed in the future -- end -- My xen/Makefile has: -- begin -- @LANG=C echo \#define XEN_COMPILER \"`$(CC) $(CFLAGS) -v

Hello xen-devel, I am using xen 4.2.1 and have tried the following with kernel 3.0.0 and 3.2.1. I am trying to invoke the HVMOP_flush_tlbs hypercall but have been unsuccessful. I am basing my call on the functions in in xc_misc.c, trying to guess what is meant by "@arg must be null" in the comment where HVMOP_flush_tlbs is defined. What is the correct way to invoke this

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

My domains dont see any traffic until you try to connect out from within the domain. Tried this several times and it was consistent. I have no firewall either. running each domain on different cpu probably doesn''t help, although Im no network expert. Here is some info. ================ [root@a root]# xm info system : Linux host : a.b.com release

# HG changeset patch # User john.levon@sun.com # Date 1161090225 25200 # Node ID 6db63d9288cbe0e80069080352a8a6257dad8118 # Parent afeef751f9dafa771726bcfb00b29a10b0baeabd Build fix for Solaris sed. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/xen/Rules.mk b/xen/Rules.mk --- a/xen/Rules.mk +++ b/xen/Rules.mk @@ -24,9 +24,11 @@ override COMPILE_SUBARCH := $(XEN_COMPIL

Hi Jeff, I have a single-CPU system with P4 HTT-enabled processor (7.1-RELEASE-p3), kernel compiled with SCHED_ULE. Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE-p3 #0:

Hi, I had a problem trying to migrate domains, in trying to locate it I noticed that saving domains doesn''t work either, which I believe explains why the receiving xfrd doesn''t actually receive anything. So here it goes... xenone:/tmp# xm list Name Id Mem(MB) CPU State Time(s) Console Domain-0 0 123 0 r---- 900.6 sky 9

Last year we had a discussion[1] about how the hypercall ABI unfortunately contains fields that change width between 32- and 64-bit builds. This is a huge problem as we come up on the python management stack for ppc64, since the distributions ship 32-bit python. A 32-bit python/libxc cannot currently manage a 64-bit hypervisor. I had a patch but was unable to test it, and some other things were

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding

Hi there! I was wondering what the general opinion on autotoolizing xen is? I am volunteering to do so, if there is interest in updating the build system to use autoconf, automake and/or libtool. Is one configure script for all of xen enough or do you want to be able to configure all/some tools separately? I know that Anthony is no fan of libtool... are there more reservations about some