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-users

Re: [Xen-users] tap:aio not working...

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] tap:aio not working...
From: jim burns <jim_burn@xxxxxxxxxxxxx>
Date: Fri, 9 May 2008 22:13:20 -0400
Delivery-date: Fri, 09 May 2008 19:13:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <48184F99.87A6.0099.1@xxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <48184F99.87A6.0099.1@xxxxxxxxx> (sfid-20080501_110004_856725_E1EF3B5C)
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.9
On Wednesday April 30 2008 12:53:13 pm Nick Couchman wrote:
> Have also located and attached the xen-hotplug.log file.  I'm trying to
> figure out how to interpret it, but if anyone sees anything obvious...

This part of the output is curious:

+ p=aio:/xenstore/xenvol1/Projects/disk0
++ xenstore_read backend/vbd/0/51952/mode
+++ xenstore-read backend/vbd/0/51952/mode
++ local v=w
++ '[' w '!=' '' ']'
++ echo w
+ mode=w
+ case $t in
+ '[' -x /etc/xen/scripts/block-tap ']'           <-------------------------??
+++ export 
PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:.
+++ 
PATH=/sbin:/bin:/usr/bin:/usr/sbin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:.
+++ export LANG=POSIX
+++ LANG=POSIX
++++ set
++++ grep '^LC_'
++++ cut -d= -f1
+++ unset
+++ trap sigerr ERR
+++ log debug remove XENBUS_PATH=backend/vbd/0/51952

The marked line tests if block-tap is executable, and then suddenly jumps to 
another script, which is doing a remove.

1) Is block-tap indeed marked as executable? My SuSE 10.3 system doesn't even 
have a block-tap, so I'm not sure what package that comes from. What is the 
output of 'rpm -q --whatprovides /etc/xen/scripts/block-tap'? If you don't 
have it either, try 'yum install /etc/xen/scripts/block-tap'.

2) Can you verify what script the rest of the output after the flagged line is 
coming from?

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