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] hanging tapdisk2 processes and improper udev rules

To: Ian Campbell <Ian.Campbell@xxxxxxxxxx>, "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 13:36:22 +0200
Cc:
Delivery-date: Fri, 22 Jul 2011 04:37:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1311326922.12772.14.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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110626 Icedove/3.1.11

On 07/22/2011 11:28 AM, Ian Campbell wrote:

This is because udev and forward/backward compatibility are strangers
passing in the night. I presume if you make the recommended change to
SYMLINK+= instead of NAME= in your udev script this goes away?
You assume correctly.

I posted a patch to fix this "libxl: attempt to cleanup tapdisk
processes on disk backend destroy" a couple of times, most recently at
http://marc.info/?l=xen-devel&m=131066210526755 but it hasn't been
applied yet. Can you try it?

I tried it:

make -j7 tools:
...
libxl_device.c: In function ‘libxl__device_destroy’:
libxl_device.c:253: error: incompatible type for argument 1 of ‘libxl__device_destroy_tapdisk’ libxl_internal.h:321: note: expected ‘struct libxl__gc *’ but argument is of type ‘libxl__gc’ libxl_device.c:274: error: incompatible type for argument 1 of ‘libxl__device_destroy_tapdisk’ libxl_internal.h:321: note: expected ‘struct libxl__gc *’ but argument is of type ‘libxl__gc’

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.

And it compiled.

I then created a guest, shut it down.
First it kept beeing in a -ps--- state, i wanted to take a look at the runing processes with "ps auxww" but the ps process hung itself.
I could no longer run "ps" successfully after this point.
syslog showed:
ul 22 13:00:07 xenturio1 xl: tap-err:tap_ctl_read_message: failure reading message Jul 22 13:00:07 xenturio1 xl: tap-err:tap_ctl_send_and_receive: failed to receive 'unknown' message

Either my hack to get your code to compile was no good or your patch has some unforseen side effects.



I have now rebooted the server.


As i went on to check if multipath had any effect on it i added
devnode "^td" to the blacklist.

Now when i xl create a vm it only boots up to a certain point and then does nothing. If that certain point were to be the login prompt everything would be fine, but it isnt:
http://pastebin.com/Lmie6KwY

This is how it should look like:

http://pastebin.com/CsgYypbk

I will try to backtrace my steps and see what i did do to break my system.

In the meantime i have other systems i can test stuff on.



-with best regards


--
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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel