From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nathan March Subject: Re: Bug in Xen 4.1.0: Xen leaks tapdisk2 processes Date: Fri, 06 May 2011 16:25:29 -0700 Message-ID: <4DC48369.7090204@gt.net> 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> <4DC43D91.3030809@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4DC43D91.3030809@novell.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: Jim Fehlig Cc: Ian Campbell , "xen-devel@lists.xensource.com" , Andreas Kinzler , Daniel Stodden List-Id: xen-devel@lists.xenproject.org On 5/6/2011 11:27 AM, Jim Fehlig wrote: >> >>> 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. > In that case, I can confirm that I'm using xend: xen1 ~ # virsh version Compiled against library: libvir 0.9.0 Using library: libvir 0.9.0 Using API: Xen 3.0.1 Running hypervisor: Xen 4.1.0 - Nathan