From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Fehlig Subject: Re: Bug in Xen 4.1.0: Xen leaks tapdisk2 processes Date: Fri, 06 May 2011 12:27:29 -0600 Message-ID: <4DC43D91.3030809@novell.com> References: <4D9305C2.5020900@hfp.de> <4DBB13E2.9030103@gt.net> <1304438166.18845.129.camel@zakaz.uk.xensource.com> <4DC038FA.3070305@gt.net> <1304588710.26692.76.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1304588710.26692.76.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , Nathan March , Andreas Kinzler , Daniel Stodden List-Id: xen-devel@lists.xenproject.org Ian Campbell wrote: > On Tue, 2011-05-03 at 18:18 +0100, Nathan March wrote: > >> On 5/3/2011 8:56 AM, Ian Campbell wrote: >> >>> On Fri, 2011-04-29 at 20:39 +0100, Nathan March wrote: >>> >>>>>>> in Xen 4.1.0 using "tap2:aio:/dev/sdaX" Xen leaks tapdisk2 processes. >>>>>>> After running some VMs and terminating them, only dom0 running, "ps >>>>>>> aux" shows: >>>>>>> >>>>> I can definitely confirm this, on a machine with 2 active VMs: >>>>> >>> I'm assuming this is xl specific and that xend isn't behaving this way >>> too, is that correct? >>> >> That's a good question, I'm not really sure. I'm doing all the vm >> creation/migration/shutdown using libvirt 0.9.0 rc1 and just connecting >> with xen:/// to the local xend. I thought xl was just a userspace >> replacement for xm and the backend functionality was the same? >> libvirt 0.9.0 was released. In fact, 0.9.1 is now out. > > xl is a complete standalone toolstack, including the backend > functionality. > > >> I don't have a spare server to test the patch with at the moment, but I >> can try this out later this week. >> > > If you are running xm/xend rather than xl then it won't help. > > But I'm not sure how one tells with libvrit which you are running, I'd > expect that if xend were running it would be used by default. Jim? > If xend is running, libvirt will use it. If not, it will attempt to use libxenlight. 'virsh version' will tell which xen backend you are using. E.g. if xend is running: xen33: # virsh version Compiled against library: libvir 0.9.0 Using library: libvir 0.9.0 Using API: Xen 3.0.1 If xend is not running: xen33: # virsh version Compiled against library: libvir 0.9.0 Using library: libvir 0.9.0 Using API: xenlight 0.9.0 Looks like I need to put libxenlight's version in there instead of libvirt's version, but 'Xen' vs. 'xenlight' will tell which libvirt backend is being used. Regards, Jim