From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick Scharrenberg Subject: Re: xen 3 dom0 eats memory - ME TOO Date: Thu, 05 Jan 2006 13:26:34 +0100 Message-ID: <43BD107A.7060100@web.de> References: <669f61d0692c197d51c11b04bb9964c6@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <669f61d0692c197d51c11b04bb9964c6@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen-devel@lists.xensource.com, James Harper List-Id: xen-devel@lists.xenproject.org Keir Fraser schrieb: >> I'll add free memory to mrtg and see what that uncovers... > > Looks like somethign allocates lots of 64-byte buffers and never frees > them. I don't currently know what is doing those allocations. It might > be worth adding tracing to kmalloc(). I changed my configuration in the following way and now no memory gets lost. I leave the physical eth0 as it is when the machine boots, create a bridge which holds all vif's of the domUs. So I have no vif for dom0 and use the physical ethernet interface directly. Turn on masquerading for eth0 like I did before. Now it works. It seems that the "virtualisazion" of the ethernet interface is responsible for the troubles. Patrick