similar to: [XCP] Strange bug this avaible memory for guests

Hello, I am just installing XCP 0.1.1 on a server with 24GB RAM Normally XCP is a 64 bits version but * *uname -a* Linux node012 2.6.27.42-0.1.1.xs0.1.1.737.1065xen #1 SMP Fri Jan 15 16:20:16 EST 2010 i686 i686 i386 GNU/Linux (not a x86_64 version !!!!) * *cat /proc/meminfo* MemTotal: 746496 kB MemFree: 384332 kB Buffers:

Hi All I have downloaded the opensource xapi source code. I am not sure what the functins of the follow modules: 1 block_device_io 2 datamodel 3 xiu (I am puzzled by the name "xiu") 4 stats 5 rpc-light 6 rss 7 xb (I think the xapi needs not to talk to xenbus directly) 8 xsrpc (why it writes some "rpc" keys to path of "domain/<domid>" in the

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

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:

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

Hello XCI developers, I have a HP6930, downloaded xenclient from the git. And by following the instruction in HOWTO, I could get xenclient boot up fine. I try then to start a guest using xenvm.readme as template and nothing shows on the screen for the guest, although xenops shows 2 doms running. Can you point me to how to start a guest. And also, is the tree downloaded from git enough to arrive

Hi Debian Xen Maintainers! Thank you for the former work. The 3.0 Version of Xen works flawlessly. When can I exspect the 3.1 version in say experimental ? Please give me a roadmap ? Best Regards Volker -- ==================================================== inqbus it-consulting +49 ( 341 ) 5643800 Dr. Volker Jaenisch http://www.inqbus.de Herlo?sohnstr. 12 0 4 1

hi?? Someone knows why i get this error after install cyrus-sasl from the source and how to solve it: /usr/lib/libsasl2.so.2: no version information available (required by /usr/lib/libldap_r.so.2) thanks?

hi, --> i have 8cores cpu. but my xenserver is using only one cpu, how to make use of all cpu cores --> machine is having 16G ram but domain0 is having very less memory. is there any way to increase memory for domain0 [root@xenserver-DZONGRI ~]# cat /proc/meminfo MemTotal: 574464 kB MemFree: 111776 kB Buffers: 9500 kB Cached: 117320 kB SwapCached: 100

Hey! I am following the steps at http://wiki.xenproject.org/wiki/XCP_Beginners_Guide for creating a VM. I''ve setup my test VM with 1GiB min/max memory. I''ve assigned 2GiB of memory to dom0 (http://wiki.xen.org/wiki/Xen_Best_Practices) . My box has 12GB of physical memory and runs Ubuntu 13.04. When I do "xe vm-start", I get the following: The server failed to handle

Hello All, I was curious to know when would updates to VM Metrics - "*Last shutdown since*" be available in a new XAPI rpm. Any ETA for this ? -- With Regards, Hussain. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Please CC as I''m not subscribed to valgrind-developers. Under Xen the toolstack is responsible for managing the domains in the system, e.g. creating, destroying, and otherwise manipulating them. To do this it uses a number of ioctls on the /proc/xen/privcmd device. Most of these (the MMAPBATCH ones) simply set things up such that a subsequenct mmap call will map the desired guest

Source: xen-api Version: 1.3.2-15 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130529 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/?PKGBUILDDIR?' > omake phase1 > omake: Symbol `FamErrlist' has different size

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

a, libxl_event.h is included in libxl.h. So, the former one also need to be installed. b, define __XEN_TOOLS__ in libxl.h: the head file "xen/sysctl.h" need check this macro. It is the same way used by the xen libxc public headers(tools/libxc/xenctrl.h and tools/libxc/xenctrlosdep.h). Signed-off-by: Bamvor Jian Zhang <bjzhang@suse.com> diff -r 87218bd367be

Hi Tim, > Do you have any new insights on the problem with reappearing mail using dovecot replication + pop3? > > It's driving me mad. I'm running dovecot 2.2.34 (874deae) on OpenBSD and it looks like I have the same problem as you have. unfortunately there has been no response, I'm stuck with 2.2.33.2 for the time being. I can only suspect it has something to do with

Hi all I have CentOS Linux release 7.0.1406, libvirt 1.2.7 installed. Just after create and start inside LXC container present cgroups. Example for memory: [root@ce7-t1 /]# ls -la /sys/fs/cgroup/memory/ total 0 drwxr-xr-x 2 root root 0 Sep 15 17:14 . drwxr-xr-x 12 root root 280 Sep 15 17:14 .. -rw-r--r-- 1 root root 0 Sep 15 17:14 cgroup.clone_children --w--w--w- 1 root root 0 Sep 15

Package: xcp-xapi Version: 1.3.2-6 Severity: normal Tags: upstream vbd plug to PV domain cause following error: The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: the device disappeared from xenstore (frontend (domid=4 | kind=vbd | devid=51760); backend (domid=0 | kind=vbd | devid=51760)) (same error

Returns free memory size per node in "xm info". This info can help users who want to bind their guest domain in one node of their NUMA machines thought set CPU affinity. I also write IA64 part support which I would send to XEN-IA64 mail-list. Thanks. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com