similar to: Doubt on XEN memory management: please clarify

hi, there is something, what i don''t understand. I have in my DomU config: memory = "128" maxmem = "1024" tsles:~ # cat /proc/xen/balloon Current allocation: 237568 kB Requested target: 237568 kB Minimum target: 237568 kB Maximum target: 1048576 kB Low-mem balloon: 804352 kB High-mem balloon: 0 kB Driver pages: 1024 kB Xen

I had temporarily started a VM, and it has allocated the memory for it. I have realised that after turning it down, the memory allocated to it, has remained reserved. Now, I need it for Dom0. So, how do I release the RAM that is reserved for VM, and make it available to Dom0? Is reboot the only option? _______________________________________________ Xen-users mailing list

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

I''m trying to configure GRUB to allocate fixed amount of dedicated memory to dom0, according to this best practices thread (http://wiki.xensource.com/xenwiki/XenBestPractices | "Xen dom0 dedicated memory and preventing dom0 memory ballooning "). When I reboot, dom0 has the fixed amount of memory as it was configured, but neither xm info shows the rest of memory available

As I understand concept of xenballooning, it allow to take memory from guest and return it to hypervisor. This allow to reduce amount of memory allocated to VM in realtime without rebooting VM. But how we can add more memory to guest VM in realtime, than was at boot time? Can we somehow make balloon inflated at start time? (F.e. VM starts with memory = 512Mb and balloon inflating to +512Mb).

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

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

Hi, we''re contemplating getting a large new server, where we will run a number of virtual servers. Are there any things we need to keep in mind in that case? Are there limitations on what a Xen system can manage? We''re talking about a 4 x Quad core CPU server with 64 GBs of RAM and a couple of terabytes of RAIDed SATA storage. -Morten (Re-sending this, as the first message

Is there any reason why I would not want to set dom0-min-mem to 0 or to what I set dom0_mem on my kernel line? Setting to 0 or setting to the same value as dom0_mem disables memory balloon correct? I cant seem to think of a reason why I would want memory ballooning. Also setting dom0-min-mem should that be done in xend-config.sxp or on the kernel command line? -- Nick Anderson

Hi, I''m just wondering is it possible, or planned for the new future, to balloon a XEN domU''s CPU cores? i.e. If I setup a domU on a Dual Quad Core machine, but only assign 2 CPU cores to it now, can I add some more later without rebooting? -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell:

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

I have xen 3.04 running on SLES10SP1. It''s working great, but I''m wondering if I have some memory issues with dom0. I have 7 domU''s, 1 is win2k, the other 6 are win2k3. I''ve had a lot of machines up and down with a reboot of dom0 in quite a while. I''m wondering if dom0 has not given up memory during the process. I added 5 win2k3 domU''s today.

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

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 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 tried for a couple of times to add an information that might help you with regard to Bug #603713 by sending mailto "603713 at bugs.debian.org" But it never appeared there - so I try to let you know how to work around that bug this way. If you decide not to take this mail into account I won't bother you any more Regards Andreas -----Urspr?ngliche Nachricht----- Von: Balg, Andreas

Hi there, my Server: Debian 4.0, XEN xen-hypervisor-3.0.3-1-i386-pae I have successfully installed and running 13 domU. I have enough free ressources for number 14. I set it up in exactly the same way like the others. Once started this dumU Nr 14, every other domU lost its network connection. If I shutdown Nr 14, everything is working finde again. Is there a maximum number of domUs per Host?

Hello, I''m struggling to handle the amount of memory that dom0 gets on some system. It''s a system with 8GB of RAM, running 2.6.38-6 with pv_ops and Xen 4.1 If I want to set the amount of memory for dom0, I get very bogus results. See here: http://pastebin.com/gRgY9ERN If I use the M notation (xl mem-set 0 4096M) the outcome is similarily unpredictable, and sometimes I get the

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

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