Re: [Xen-users] Ballooning on SLES11SP1

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

You need to make sure that you set the dom0_mem parameter at boot time.  
Without that parameter what you're basically doing is assigning all of your 
available RAM to your dom0, then telling dom0 that memory cannot be dynamically 
changed, but that it must be at least 2048M.  This means that there is 0 free 
memory for domUs.  So, set the dom0_mem boot parameter, and keep the parameters 
configured as you have them below in the xend-config.sxp file.  Then start some 
domUs.  You can also look at "xm info" and see the free memory parameter and 
verify that that shows the amount of memory you expect to be available for 
domUs.

-Nick

>>> On 2010/08/05 at 10:50, James Pifer <jep@xxxxxxxxxxxxxxxx> wrote: 
> 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 no)
> 
> Looks like this kernel is ignoring those parameters because I had to
> turn ballooning back on before we could start any VMs. 
> 
> I was going to open a ticket with Novell, but thought I'd ask if anyone
> has seen this? 
> 
> Maybe disabling ballooning is not the way to go anymore, anyone have
> opinions on that? We used to run out of memory a lot, even though there
> was plenty free. Disabling ballooning seemed to make things more stable
> at the time. 
> 
> Any suggestions are appreciated. 
> 
> Thanks,
> James




--------
This e-mail may contain confidential and privileged material for the sole use 
of the intended recipient.  If this email is not intended for you, or you are 
not responsible for the delivery of this message to the intended recipient, 
please note that this message may contain SEAKR Engineering (SEAKR) 
Privileged/Proprietary Information.  In such a case, you are strictly 
prohibited from downloading, photocopying, distributing or otherwise using this 
message, its contents or attachments in any way.  If you have received this 
message in error, please notify us immediately by replying to this e-mail and 
delete the message from your mailbox.  Information contained in this message 
that does not relate to the business of SEAKR is neither endorsed by nor 
attributable to SEAKR.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users