Re: hanging tapdisk2 processes and improper udev rules

[Andreas Olsowski <andreas.olsowski@leuphana.de>]

[-- Attachment #1.1: Type: text/plain, Size: 1406 bytes --]

>> My expertise with C is barely existant, but i took a look at
>> tools/libxl/libxl_device.c
>>
>> and changed your
>> libxl__device_destroy_tapdisk(gc, be_path);
>> into
>> 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 #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 6595 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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