xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Nathan March <nathan@gt.net>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Andreas Kinzler <ml-xen-devel@hfp.de>
Subject: Re: Bug in Xen 4.1.0: Xen leaks tapdisk2 processes
Date: Tue, 03 May 2011 10:18:50 -0700	[thread overview]
Message-ID: <4DC038FA.3070305@gt.net> (raw)
In-Reply-To: <1304438166.18845.129.camel@zakaz.uk.xensource.com>


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?

I don't have a spare server to test the patch with at the moment, but I
can try this out later this week.

- Nathan

  reply	other threads:[~2011-05-03 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 10:28 Bug in Xen 4.1.0: Xen leaks tapdisk2 processes Andreas Kinzler
2011-04-29 19:39 ` Nathan March
2011-05-03 15:56   ` Ian Campbell
2011-05-03 17:18     ` Nathan March [this message]
2011-05-05  9:45       ` Ian Campbell
2011-05-06 18:27         ` Jim Fehlig
2011-05-06 23:25           ` Nathan March
2011-05-09  8:23             ` Ian Campbell
2011-05-10 19:17               ` Daniel Stodden
2011-05-11  8:43                 ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DC038FA.3070305@gt.net \
    --to=nathan@gt.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=ml-xen-devel@hfp.de \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).