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] Hotplug scripts not working... xen/ia64 domU stoppedwork

To: "Xen Mailing List" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Hotplug scripts not working... xen/ia64 domU stoppedworking
From: "Dave Thompson \(davetho\)" <davetho@xxxxxxxxx>
Date: Tue, 6 Dec 2005 10:40:20 -0500
Delivery-date: Tue, 06 Dec 2005 15:44:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcX6d/pYVjGysVgASWqXU+1mbEPIsAAAlQdg
Thread-topic: [Xen-devel] Hotplug scripts not working... xen/ia64 domU stoppedworking
 

> -----Original Message-----
> From: Ewan Mellor [mailto:ewan@xxxxxxxxxxxxx] 
> Sent: Tuesday, December 06, 2005 9:16 AM
> To: Dave Thompson (davetho)
> Cc: Xen Mailing List
> Subject: Re: [Xen-devel] Hotplug scripts not working... 
> xen/ia64 domU stoppedworking
> 
> On Tue, Dec 06, 2005 at 09:51:24AM -0500, Dave Thompson 
> (davetho) wrote:
> 
> > UEVENT[1133877953] add@/devices/xen-backend/vbd-4-2049
> > UEVENT[1133877953] add@/devices/xen-backend/vif-4-0 
> UEVENT[1133877953] 
> > add@/class/net/vif4.0 UEVENT[1133877953] 
> > online@/devices/xen-backend/vif-4-0
> > UDEV  [1133877956] add@/devices/xen-backend/vbd-4-2049
> > 
> > Here is the output when the vbd failed:
> > 
> > UEVENT[1133880108] add@/devices/xen-backend/vbd-5-2049
> > UEVENT[1133880108] add@/devices/xen-backend/vif-5-0 
> UEVENT[1133880108] 
> > add@/class/net/vif5.0 UEVENT[1133880108] 
> > online@/devices/xen-backend/vif-5-0
> > UDEV  [1133880111] add@/devices/xen-backend/vif-5-0 UDEV  
> [1133880111] 
> > online@/devices/xen-backend/vif-5-0
> > UDEV  [1133880116] add@/class/net/vif5.0
> 
> Well this suggests that udevd is simply throwing away the vbd 
> event!  I don't suppose there's any indication in your syslog 
> as to why it might be doing this?  That is a bit strange.  
> Our driver triggers the event correctly, as you can see from 
> the first line, but udev then simply doesn't pass it on.

Actually there are some messages in syslog concerning udev:

Dec  6 08:41:51 davetho-intel udevsend[5693]: main: unable to connect to
event daemon, try to call udev directly
Dec  6 08:41:51 davetho-intel udevsend[5696]: main: unable to connect to
event daemon, try to call udev directly
Dec  6 08:41:51 davetho-intel udevsend[5699]: main: unable to connect to
event daemon, try to call udev directly
Dec  6 08:41:51 davetho-intel logger: /etc/xen/scripts/vif-bridge:
online XENBUS_PATH=backend/vif/5/0
Dec  6 08:41:51 davetho-intel kernel: device vif5.0 entered promiscuous
mode
Dec  6 08:41:51 davetho-intel kernel: xenbr0: port 4(vif5.0) entering
learning state
Dec  6 08:41:51 davetho-intel kernel: xenbr0: topology change detected,
propagating
Dec  6 08:41:51 davetho-intel kernel: xenbr0: port 4(vif5.0) entering
forwarding state
Dec  6 08:41:51 davetho-intel logger: /etc/xen/scripts/vif-bridge:
Successful vif-bridge online for vif5.0, bridge xenbr0.
Dec  6 08:41:51 davetho-intel logger: /etc/xen/scripts/vif-bridge:
Writing backend/vif/5/0/hotplug-status connected to xenstore.
Dec  6 08:41:56 davetho-intel ifup: No configuration found for vif5.0
Dec  6 08:42:01 davetho-intel kernel: vif5.0: no IPv6 routers present

> Could you try udevmonitor --env and we'll see if there's 
> anything odd in the environment that might be doing this.  

Here is the output of 'udevmonitor --env' during the create:

UEVENT[1133883393] add@/devices/xen-backend/vbd-6-2049
ACTION=add
DEVPATH=/devices/xen-backend/vbd-6-2049
SUBSYSTEM=xen-backend
SEQNUM=1205
PHYSDEVBUS=xen-backend
XENBUS_TYPE=vbd
XENBUS_PATH=backend/vbd/6/2049
XENBUS_BASE_PATH=backend/vbd
XENBUS_FRONTEND_ID=6

UEVENT[1133883393] add@/devices/xen-backend/vif-6-0
ACTION=add
DEVPATH=/devices/xen-backend/vif-6-0
SUBSYSTEM=xen-backend
SEQNUM=1206
PHYSDEVBUS=xen-backend
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/6/0
XENBUS_BASE_PATH=backend/vif
XENBUS_FRONTEND_ID=6

UEVENT[1133883393] add@/class/net/vif6.0
ACTION=add
DEVPATH=/class/net/vif6.0
SUBSYSTEM=net
SEQNUM=1207
INTERFACE=vif6.0

UEVENT[1133883393] online@/devices/xen-backend/vif-6-0
ACTION=online
DEVPATH=/devices/xen-backend/vif-6-0
SUBSYSTEM=xen-backend
SEQNUM=1208
PHYSDEVBUS=xen-backend
PHYSDEVDRIVER=vif
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/6/0
XENBUS_BASE_PATH=backend/vif
XENBUS_FRONTEND_ID=6
script=/etc/xen/scripts/vif-bridge
vif=vif6.0

UDEV  [1133883396] add@/devices/xen-backend/vif-6-0
HOME=/
PATH=/sbin:/bin:/usr/sbin:/usr/bin
ACTION=add
DEVPATH=/devices/xen-backend/vif-6-0
SUBSYSTEM=xen-backend
SEQNUM=1206
PHYSDEVBUS=xen-backend
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/6/0
XENBUS_BASE_PATH=backend/vif
XENBUS_FRONTEND_ID=6
UDEV_LOG=3

UDEV  [1133883396] online@/devices/xen-backend/vif-6-0
HOME=/
PATH=/sbin:/bin:/usr/sbin:/usr/bin
ACTION=online
DEVPATH=/devices/xen-backend/vif-6-0
SUBSYSTEM=xen-backend
SEQNUM=1208
PHYSDEVBUS=xen-backend
PHYSDEVDRIVER=vif
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/6/0
XENBUS_BASE_PATH=backend/vif
XENBUS_FRONTEND_ID=6
script=/etc/xen/scripts/vif-bridge
vif=vif6.0
UDEV_LOG=3

UDEV  [1133883401] add@/class/net/vif6.0
HOME=/
PATH=/sbin:/bin:/usr/sbin:/usr/bin
ACTION=add
DEVPATH=/class/net/vif6.0
SUBSYSTEM=net
SEQNUM=1207
INTERFACE=vif6.0
UDEV_LOG=3
RENAMED=yes

> Otherwise, the only other configurable part is the udev 
> rules.  Perhaps there's something odd about them that it 
> doesn't like, though it works some of the time, so that would 
> surprise me.
> 
> Ewan.
> 

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