similar to: Disable memory balloon in dom0

Hi, during some experiments with many guests I get crashing Dom0s because of too less memory. Actually the OOM killer goes ''round and kills random things, preferably qemu-dm''s ;-) The box in question has 128GB of memory, I start with dom0_mem=8192M (or 16384M, doesn''t matter). I also used "dom0_mem=8192M,min:1536M", but that didn''t make any

We have some test servers running SLES11SP1 and we''ve updated to the latest kernel from Novell: 2.6.32.13-0.5-xen Since running the updates on these servers our xen ballooning parameters are not working. Because of memory problems in the past we set dom0 to 2048 meg of ram in grub and set the following parameters in /etc/xen/xend-config.sxp: (dom0-min-mem 2048) (enable-dom0-ballooning

Hi, I have encountered an apparently benign error on two systems where the dom0 kernel log is flooded with messages like: [52482.163855] System RAM resource [mem 0x1b8000000-0x1bfffffff] cannot be added [52482.163860] xen_balloon: reserve_additional_memory: add_memory() failed: -17 The first line is from drivers/xen/xen-balloon.c, the second from mm/memory_hotplug.c The trigger for the

Hi guys, First of all, sorry for my poor english. This is my first message at this list. I''m using Xen on several machines since last November. Right now I''m having a specific problems with 2 servers: both are losing the network on dom0 but all guest systems are still running fine. Looking at those dom0 logs I''ve discovered that sometimes linux kernel OOM-Killer

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

Hi! i notice a serious regression with 3.5 as Dom0 kernel (3.4 was rock stable): 1st: only the GPU PCI Passthrough works, the PCI USB Controller is not recognized within the DomU (HVM Win7 64) Dom0 cmdline is: ro root=LABEL=dom0root xen-pciback.hide=(08:00.0)(08:00.1)(00:1d.0)(00:1d.1)(00:1d.2)(00:1d.7) security=apparmor noirqdebug nouveau.msi=1 Only 8:00.0 and 8:00.1 get passed through

Hi All Back in August there was a report of these errors popping up in dmesg, and as far as I can tell it's still unresolved even in the latest kernel. System RAM resource [mem 0xc8000000-0xcfffffff] cannot be added xen_balloon: reserve_additional_memory: add_memory() failed: -17 On this example its running 3.10.20-11.el6.centos.alt.x86_64 To replicate this just disable Dom0 memory

# HG changeset patch # User Ian Campbell <ijc@hellion.org.uk> # Date 1354011148 0 # Node ID 3174dc24e3efb0c5b964c244dbfb0218a03a38cf # Parent 541b0e1a36c86db5df04988dd4ade5430776a7f2 xl: xl.conf(5): correct advice re autoballooning vs. dom0_mem. The advice was backwards, you should really disable autoballoon if you use dom0_mem. Also add a reference to the command-line docs.

Hi all, This is my first post to the list, I hope someone out there can help! I am running xen 3.0.3, with CentOS 5.2 based Dom0 (kernel-xen-2.6.18-92.1.22.el5) Recently I have noticed some complete system lockups on a few different servers. Neither Dom0 or any of the guests respond to pings, connecting a keyboard and monitor to the system only shows a blank screen. Nothing is written to logs

Hello, I work in a hosting company, we have tens of Xen dom0 running just fine, but unfortunately we do have a few that get out of control. Reported behaviour : - dom0 uses more and more memory - no process can be found using that memory - at some point, oom killer kicks in, and kills everything, until even ssh the box becomes hard - when there is really no more process to kill, it crashes

From: David Vrabel <david.vrabel@citrix.com> autoballoon=1 is not recommened if dom0_mem was used to reduce the amount of dom0 memory. Instead of requiring users to change xl.conf if they do this, extend the autoballoon option with a new choice: "auto". With autoballoon="auto", autoballooning will be disabled if dom0_mem was used on the Xen command line. For

Hello, I recently swapped some components, and rebuilt my system. Changes to the configuration: - Wheezy Beta 1 > Wheezy Beta 2 - Kernel 3.4.9 > Kernel 3.4.11 I have tested the new Xen 4.2 stable, and Xen unstable revision 25777, both are giving me the same error so I do not believe it is related to a change in Xen. The first attempt to pass a PCI device after booting the system

Years ago when i first started using xen i specified a dom0_mem=xxx in grub. I no longer do this, what i do now is set the dom0_min-mem setting in xend-config.sxp to 1024. I also have a few scripts that run at boot and one of them does a `xm mem-set 0 1024`. after that a xm list 0 shows dom0 allocated 1024 Ram. The problem comes on teh system when i run free or free -m, free shows dom0

Hi, we have a couple of nodes based on CentOS 6 and Xen4CentOS. Unfortunately some of these nodes keep crashing frequenly. We use the latest versions: # uname -r 3.10.43-11.el6.centos.alt.x86_64 # xm info host : vserver20 release : 3.10.43-11.el6.centos.alt.x86_64 version : #1 SMP Mon Jun 16 14:22:02 UTC 2014 machine : x86_64

Hi all. We just put a relative large server in operation (for our measures ;-) ), a 4x Dual Core / Intel with 16GB Ram and a 3ware 9550SX SATA-RAID with 4 drives. Operating system for the Dom0 is an up-to-date gentoo linux. Everything runs really fine, there are 4 Domu''s running, 1x gentoo and 2x debian and 1x Windows Server 2003. DomU''s are running blazing fast in normal

All, I''ve got one Xen server running CentOS 5, with 3 CentOS virtual machines on it. I have what I hope is a simple question: I''d like to backup the virtual machines. I don''t care about anything but the ability to restore a couple of files and be able to be back up and running quickly. At some point I''ll have a spare server ready to migrate running Xen

Hello Everyone, We have noticed that one of our servers xen Dom0 is restarting idiopathically. Atleast, we are not able to analyze the cause. I have checked the logs but couldn''t find anything relating to it. Are there any tools such as kdump (which doesn''t seem to work on xenified kernels) for catching the kernel crash snapshot. Regards, Sree Harsha Totakura Member, Open

Hi all, I'm having issue with my Centos 5.1 /Xen installation. I'm having some dom0 running 2.6.18-53.1.6.el5xen (x86_64). On the dom0 where the load is high (more than 70% of total system memory consumed by dom0 and domU) we have a lot of "memory squeeze ". The result is that the domU seems to be blocked (no network/no disk acces/ etc....). Looking for a solution in xen

I''ve installed Xen Hypervisor 3.0.3 (CentOS 5.7, i386) inside Virtualbox 4.1.16 (Mageia 1, i686) and have noticed that Dom0 is consuming 85% of the memory allocated to the VM (1GB) so I''d like to reduce this as much as possible in order to make more room for one or two VM''s. Is there a minimum amount of vRAM that can/should be allocated to Dom0 (using the dom0_mem boot

I''m getting the error: xend (12, ''Cannot allocate memory'') From the command line after the Dom-0 goes through a period of heavy memory usage. I don''t have any hard numbers on how to duplicate it, but I''ll give you the steps I''ve gone through to duplicate the problem. First, some information about my setup. It''s a new setup, and has