WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Bug in Xen 4.1.0: Xen leaks tapdisk2 processes

To: Jim Fehlig <jfehlig@xxxxxxxxxx>
Subject: Re: [Xen-devel] Bug in Xen 4.1.0: Xen leaks tapdisk2 processes
From: Nathan March <nathan@xxxxxx>
Date: Fri, 06 May 2011 16:25:29 -0700
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Andreas Kinzler <ml-xen-devel@xxxxxx>, Daniel Stodden <Daniel.Stodden@xxxxxxxxxx>
Delivery-date: Fri, 06 May 2011 16:27:15 -0700
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=gt.net; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mail; bh=1p54GKFskE/X Am9MH/6dvuG90qA=; b=tyoOvCn96O76XYAXcVmgX1BFJEcXBm4YfUk9qFC4qjYW qWeTEUOxS0yTKM7iABHeTfIgZgBDUCd2QJmR0cgYaCE7kJRH4Nea/fqGJ9cgAqwK GBXQj68KETCHxSDyzcPWUl69bxZ3Ac60SLnsbRknLi4em1W9cChFf1gLUB4gNL8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gt.net; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mail; b=BJvWmi /vFwlNZj44PFJA60FgI5fEnv7m82FQvU7QBzQmL8Z1LMqxpoSfc1YITmUy1JAfor tKsaZz3CbgNRDkgyywhQsNsiAvfS8JpDJT83bhSqBMXmsNOAx25QgH8f41W5+PQC +CC1g0+bidcPzLEYecOqKYFEuogMp17c4iz9A=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DC43D91.3030809@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D9305C2.5020900@xxxxxx> <4DBB13E2.9030103@xxxxxx> <1304438166.18845.129.camel@xxxxxxxxxxxxxxxxxxxxxx> <4DC038FA.3070305@xxxxxx> <1304588710.26692.76.camel@xxxxxxxxxxxxxxxxxxxxxx> <4DC43D91.3030809@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9

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

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel