From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Xen-users] (xen) Possible bug: Memory squeeze in netback driver. Date: Wed, 07 Jun 2006 15:43:08 -0500 Message-ID: <44873A5C.8050700@us.ibm.com> References: <200606062047.44746.erik@hensema.net> <4485F70E.4020602@us.ibm.com> <200606071752.26963.erik@hensema.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200606071752.26963.erik@hensema.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Erik Hensema Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Erik Hensema wrote: > On Tuesday 06 June 2006 23:43, Anthony Liguori wrote: > >> This is a rather curious path in the code involving rate limiting >> that I'm not all that familiar with. Does it help is you create >> the domains with a large maxmem than memory? For instance: >> >> maxmem = 512 >> memory = 256 >> > > Yes, it does seem to help. I've recreated almost all domains with 16 > MB 'headroom', now I can create domains up until the point I run out > of loop devices ;-) (6 domU's running ATM) > I'll reboot tonight (or shutdown all domains and reload the loop > module) and try to start more domains. > I suspected it would but I was hoping it wouldn't. Do this mean that the netback driver needs to be able to increase it's reservation? If so, should we be enforcing (in the tools) that memory < maxmem? Any thoughts Keir? Regards, Anthony Liguori