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/
Home Products Support Community News


Re: [Xen-devel] hanging tapdisk2 processes and improper udev rules

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] hanging tapdisk2 processes and improper udev rules
From: Andreas Olsowski <andreas.olsowski@xxxxxxxxxxx>
Date: Fri, 22 Jul 2011 16:28:11 +0200
Delivery-date: Fri, 22 Jul 2011 07:29:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1311343663.12772.74.camel@xxxxxxxxxxxxxxxxxxxxxx>
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: <4E294068.2030700@xxxxxxxxxxx> <1311326922.12772.14.camel@xxxxxxxxxxxxxxxxxxxxxx> <4E2960B6.5000902@xxxxxxxxxxx> <1311343663.12772.74.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110626 Icedove/3.1.11
My expertise with C is barely existant, but i took a look at

and changed your
libxl__device_destroy_tapdisk(gc, be_path);
libxl__device_destroy_tapdisk(&gc, be_path);

as i have seen some&gc on other lines of code.

That looks right. I think this is just a difference between current
xen-unstable and xen-4.1 (due to 23045:c426a7140c99 FWIW).
What do you mean looks right, the compilation errors or my shot-in-the-dark adjustment?

Uh. That really shouldn't happen :-/ In fact baring a bug in the host OS
itself I'm not sure how ps can ever get into that state...
I had this happen before on two occasions (one of them using xm to create a guest, whereas xl worked fine) and Sébastien Riccio wrote in this thread, that he encountered it too.
If this one returns during "normal operation", ill write some more.

It's possible that it relies on something in xen-unstable that I'm not
aware of. Would it be possible for you to try and repro this issue with
xen-unstable.hg and this patch?
Yes, i can and will do that.
Probably later this evening (4PM here now), but definitely this weekend.
I will reply to this thread with the results.

Andreas Olsowski
Leuphana Universität Lüneburg
Rechen- und Medienzentrum
Scharnhorststraße 1, C7.015
21335 Lüneburg

Tel: ++49 4131 677 1309

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Xen-devel mailing list