From mboxrd@z Thu Jan 1 00:00:00 1970 From: Zhigang Wang Subject: Re: [PATCH] Fix memory leak in xend Date: Fri, 29 Aug 2008 09:54:19 +0800 Message-ID: <48B756CB.4010308@oracle.com> References: <20080829034032.Y22061-100000@xs2.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20080829034032.Y22061-100000@xs2.xs4all.nl> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan de Konink Cc: Jim Fehlig , xen-devel List-Id: xen-devel@lists.xenproject.org Stefan de Konink wrote: > On Fri, 29 Aug 2008, Zhigang Wang wrote: > >> I also encountered this many times. I come up with a patch. >> >> Jim, please review. >> >> thanks, >> >> zhigang >> >> Stefan de Konink wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA512 >>> >>> Jim Fehlig schreef: >>>> We observed OOM kills of xend after ~20 days in openSUSE build service >>>> workers. xend reached around 2.5 G virt, 1.5G res, and 1.8G shared >>>> memory usage. Attached patch provides a plug. >>> Did you see problems after this patch? I have applied it on 3.2.1 which >>> borks about missing vm_metrics. >>> >>> >>> Stefan >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2.0.9 (GNU/Linux) >>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >>> >>> iEYEAREKAAYFAki3HhkACgkQYH1+F2Rqwn049gCeIYOm5MSf/NQfgdb9TC009wjS >>> 9l8An0PeV5xp/jYamySsSACJO1OI2Jp7 >>> =bJwS >>> -----END PGP SIGNATURE----- >>> >>> _______________________________________________ >>> Xen-devel mailing list >>> Xen-devel@lists.xensource.com >>> http://lists.xensource.com/xen-devel > > The patch you provide seems to be for the 3.3 version right? The > is_managed attribute/function, is it available for 3.2? Can anyone > backport this? > I don't think this patch can solve your VM start problem. It only gives your more accurate description of the problem you are encountering. you should check /var/log/xen/xend-debug.log to see which is the right causing of this problem. > (I think giving me a reference to a kernel that is older than 2.6.18 and > supports x86_64 + Xen 3.3 is more work ;) Xen 3.3 has the same ABI of 3.0+. you can try the latest fedora kernels. zhigang > > > Stefan >