similar to: total_memory incorrect

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, Earlier this week I installed a test server with CentOS 5.6 with Virtualization enabled during the installer. Today I installed another server using the same method (they are identical servers). I just did a yum update and I found something curious. Both servers have a different kernel. Server 1 is at 9.1 version and server 2 at 5.1. How can this be? How to I get the latest version on

You need to add dom0_mem=XXXm to xen or scale back the memory of domain0 with using "xm mem-set <DomId> <Mem>" command. Your domain0 used up almost all physical mem. >total_memory : 1023 >free_memory : 62 Thanks Yunfeng >-----Original Message----- >From: xen-devel-bounces@lists.xensource.com

Has anyone been able to boot a fully virtualized (Intel VT) 32bit guest on XEN32 unstable? I''m trying to setup a nightly test environment for this configuration and XEN32 nosmp hangs when launching a 32bit guest, and XEN32 smp gets a double fault launching a 32bit guest. It happens pretty early as the SDL window doesn''t come up. I tried with apic, pae, and acpi all on

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

I must be missing something obvious. I have a large domU guest: dom0# cat /etc/xen/turing name = "turing" uuid = "8d3383a0-f0ae-f0b1-215d-c2e04115e9fe" maxmem = 40000 memory = 40000 vcpus = 12 bootloader = "/usr/bin/pygrub" kernel = "/var/lib/xen/boot_kernel.nrTJko" ramdisk = "/var/lib/xen/boot_ramdisk.y6Gcn9" extra = "ro

Hi, Curiously, it''s worth noting that Xeon Processor 5100 series are not in the list of HVM Compatible Processors : http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors Patrick ----- Message d''origine ---- De : Mohamed Zohny <mohamad.zohny@gmail.com> À : xen-users <xen-users@lists.xensource.com> Envoyé le : Mercredi, 8 Novembre 2006, 9h17mn 08s Objet :

Hi all, got this every time: Error: Device 5632 (vbd) could not be connected. Backend device not found. didn''t have any problem in b95 Any idea? thanks Philip xm info host : snv release : 5.11 version : snv_97 machine : i86pc nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1

Hi all, I have a Debian Lenny domU running on an Etch dom0 (xm info output below). It seems that the domU network falls asleep after some time. After some activity, either trying to do something like a ping or dig from within the domU or enough client attempts to connect to a samba share, it comes back up. That wouldn''t be terrible, except that the delays in reconnecting to the samba

Hi all, I'm trying to run Windows Server 2008 x86_64 on XEN, but I have a problem... The instalation works fine, but at the first reboot after instalation I get an "Stop 0x0000007E" error. Please, can you help me with this problem? My *processor*: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz My *xm info*: xm info host : vs01.lan.specto.com.br release :

I want to give my clients access to their Xen domU consoles using VNC. This works great using vfb device configured as type=vnc. However I have 2 problems: * I can't figure out how I can add a vfb device to a running domain without restarting it (I have 100+ domU's I want to enable this on, and want to avoid restarting them all if possible) * Related, I can't figure out how I can

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:

Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1

Is serial port "passthrough" possible for the version of xen that ships with centos 5.2? I've disabled the xen hypervisor serial console, and can see the serial port in dom0. I've masked out the 8250, 8250_pnp and serial_core modules on dom0 and rebooted. xm create domain fails with the error that exactly 4 arguments are required and only 3 were given. Steps I followed: 1) I

Hello , I use Centos 5.4 , with the redhat version of xen . I need for some guest to change the hardware for the network . So in my xen config i add the model option in the vif line . When the guest boot , i had the right emulation , but after a reboot , the guest loose the configuration . Someone can confirm the bug in centos 5.5 ? Have someone a patch ? Extract of my config : builder

I am trying to install Windows 2003 Server as a xen guest and I am having a problem. After the guest is booted from CD-ROM i partition disk OK, and while system is trying to copy files needed for the installation, it cannot read some files from CD-ROM (starting with wow32.dll etc.). I have tried also to copy installation disk onto local disk and load it from .iso file, but the same problem

Hello: As you can see from xm info below, we have almost 200GB of memory in our server running CentOS 5.2. But, we can't seem to allocate all the memory. For some reason, the total memory that can be allocated maxes out at 188.4 GB. None of the VMs has hit its own max-mem limit. Even when we set one of the VM's memory so the total is above 188.4 GB, its memory allocation stops when the

Hi all, We''ve been using Xen 3.0.3-1 on Debian Etch for around 2 years now using standard Xen bridging. Over the past few months, we''ve experienced the periodic disappearance of VIF macs from the FDB of the bridge. It seems to happen at random, primarily with domUs that typically receive less network traffic. When the VIF stops responding, the mac address for it still shows up