From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: kvm memory leak (Was Re: vhost-net patches) Date: Thu, 29 Oct 2009 14:50:10 +0200 Message-ID: <4AE98F82.9060304@redhat.com> References: <20091023110438.GA20229@redhat.com> <1256310168.4443.2.camel@localhost.localdomain> <1256310765.4443.4.camel@localhost.localdomain> <1256315020.4443.12.camel@localhost.localdomain> <20091026200513.GA26623@redhat.com> <1256592889.10142.8.camel@localhost.localdomain> <20091027064302.GB26914@redhat.com> <1256654819.4753.6.camel@localhost.localdomain> <20091027152753.GA4622@redhat.com> <1256661378.6745.2.camel@localhost.localdomain> <20091028164618.GA29235@redhat.com> <4AE988B8.30007@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Shirley Ma , Sridhar Samudrala , Shirley Ma , David Stevens , kvm@vger.kernel.org, sri@linux.vnet.ibm.com, mashirle@linux.vnet.ibm.com To: "Michael S. Tsirkin" Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45939 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751566AbZJ2MuK (ORCPT ); Thu, 29 Oct 2009 08:50:10 -0400 In-Reply-To: <4AE988B8.30007@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 10/29/2009 02:21 PM, Avi Kivity wrote: > On 10/28/2009 06:46 PM, Michael S. Tsirkin wrote: >> On Tue, Oct 27, 2009 at 09:36:18AM -0700, Shirley Ma wrote: >>> Hello Michael, >>> >>> On Tue, 2009-10-27 at 17:27 +0200, Michael S. Tsirkin wrote: >>>> Possibly GFP_ATOMIC allocations in vring_add_indirect are failing? >>>> Is there a chance you are tight on guest memory for some reason? >>>> with vhost, virtio does currently consume a bit more memory than >>>> with userspace backend. >>> I did see memory leak on host every time after exiting guest. I don't >>> know where. Do you see it? >> I don't see a leak specific to vhost. However, even without vhost, >> starting up guest increases kmalloc-128 counter in /proc/slabinfo >> and this fails to go down when qemu is killed. >> >> Anyone else seeing this? > > I'm seeing it, but starting a new guest seems to reclaim this memory. > I'll enable debug and see what's the cause. > kmemleak doesn't see any kvm memory leaks. -- error compiling committee.c: too many arguments to function