search for: free_memori

Hello, I have some dom0 which have 8GB RAM, but when I look with xm list, it just shows me 6GB, I need to setup some new VM, each with 1GB, so I should have with 3VM still 5GB free, but im only seeing 3GB. Can I just create 2 new VM with each 1GB and still have 3GB for the dom0? #xm top xentop - 11:31:17 Xen 3.1.0-53.1.14.el5 4 domains: 1 running, 3 blocked, 0 paused, 0 crashed, 0 dying, 0

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

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

Hello list, I have two differents installation Xen Hypervisor on two identical physical server, on the same switch : The problem is on my new server (Xen 4.0.1 with pvops kernel 2.6.32.24), I have bad performance on bandwidth I have test with a files copy and "iperf". Result iperf average: Transfert Bandwidth XEN-A -> Windows

Hey all, just compiled xen 3.4.2 and linux 2.6.31.12. I followed the instructions on the Xen wiki to get the install running. my issue here is that in my grub memnu config i set dom0_mem=512M when i login to the dom0 and i do a free -m i get that the system only has 432 under the total section. booting into the stock debian kernel 2.6.26-2-amd64 kernel gives me 8192 free memory for i did

Hello. I recently tried installing NetBSD-5 on xen-4.0.1-rc5, which resulted in no network (xennet0 can''t get IPs per dhclient and has no connectivity if set by hand). Tried it with netBSD-5.1-RC3-1 i386 PAE & amd64, netBSD-5.0 and even 4, all with the same result. On a older xen version (3.3.1) networking works fine, so I assume it''s a xen bug, and not a netBSD-kernel

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

Hi Guys, Now I am using Xen-4.0.0. I need to attach CDROM from ISO files to vitual machines when they are running. The VMs contain RHEL4.6, Windows Server 2003 32bit and Windows Server 2006 64bit. The disk configuration of the VMs is: disk = [ ''tap:vhd:/guest/SS_test/vhd/hmi-100130.vhd,hda,w''] (1) When I attach a CDROM to RHEL4.6 VM with the command: virsh

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 everyone, i just updated from 4.2.1 to 4.2.2. If i try to fire up my win2k8 domU with a pci device attached, the dom0 machine hardcrashes. my system log (idrac) shows the following: CPU 2 has an internal error (IERR). A bus fatal error was detected on a component at bus 0 device 0 function 0. CPU 1 machine check detected. and plenty of other entries. The machine hardresets then. If i

Hi Ian (and all), I recently came across a bug in xl autoballooning in Xen 4.2.2 that I found mentioned way back in May 2012. In a nutshell, I tried to create a new DomU with 1024M of memory. The Dom0 had 3100M free: # xl info | grep memory total_memory : 20479 free_memory : 3100 The guest template is very simple: # cat /etc/xen/template.vm name =

Hello. We have a number of Xen 3.4.2. boxes which have constant iowaits at around 10% with spikes up to 100% when accessing data over NFS. We have been unable to nail down the issue. Any advice? System info: release : 2.6.18-194.3.1.el5xen version : #1 SMP Thu May 13 13:49:53 EDT 2010 machine : x86_64 nr_cpus : 16 nr_nodes

Hello, I am not sure if this is the correct Mailing list for the issue I have. I have a new system with 18GB of Physical memory on the system. I loaded CentOS 6.4. But when I boot into Dom0, I only see (xm info) 2GB of total memory? I set 1GB for Dom0, but I am not sure why the hypervisor does not see all the memory. [root at barbaro images]# xm info host :

Hi All, Debian squeeze, Xen 4.0, 2.6.32-5 I successfully installed opensolaris, but when trying to convert to pygrub it just hangs. root@vhost2:/var/log/xen# xm create /etc/xen/opensolaris.cfg -c Using config file "/etc/xen/opensolaris.cfg". root@vhost2:/etc/xen# xm list Name ID Mem VCPUs State Time(s) Domain-0

hi, thanks for your response. i cleaned that above one and installed in this following steps: * sudo apt-get install gcc make pkg-config libxml2-dev libgnutils-dev libdevmapper-dev libcurl4-gnutls-dev python-dev libpciaccess-dev libxen-dev libnl-dev * ./configure = --prefix=/usr --localstatedir=/var --sysconfdir=/etc --with-xen=yes --with-libxl=yes * make * make install now i am getting the

Hi, This is slightly OT as xen is not officially supported in EL6. But maybe someone else is running it on centos6 as well and could help me out here: I have problems allocating a static amount of memory for my xen dom0. It seems to reduce when new domUs are created, even though I *think* ballooning is disabled. Can someone advise me what I'm doing wrong? I have xen-4.1.1-3 installed from

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

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