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] no udev events in netback domU driver domain 2.6.32.14

To: philip tricca <flihp@xxxxxxxxx>
Subject: Re: [Xen-devel] no udev events in netback domU driver domain 2.6.32.14
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 7 Jul 2010 09:45:05 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 07 Jul 2010 06:45:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C33E093.7090301@xxxxxxxxx>
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: <4C33E093.7090301@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.20 (2009-12-10)
On Tue, Jul 06, 2010 at 10:04:03PM -0400, philip tricca wrote:
> I've spent a bit trying to configure and unprivileged network driver
> domain using the current 2.6.32.14 pvops kernel (haven't up'd to .15
> due to incompatibility with 4.0.0 release).  I've been partially
> successful but am failing in what I'd think would be the last step:
> getting udev rules to fire when attaching network devices using
> xen-netback & xen-netfront drivers.  From my reading of the pvops
> wiki page there's a possibility that the wiring between the drivers
> and the udev events may not have been forward ported completely.  In
> fact, using 'udevadm monitor' I don't see any events at all when the
> vif is created in the driver domain and when eth0 is created in the
> client (both are created when xm network-attach is run).

You won't see the 'eth0' being created from Dom0 side. But you should
see the rest:
> 
> Is anyone familiar enough with these portions of the driver to
> comment on this?  If this "should" be working I can post the details
> of my setup and debug information if necessary but I don't want to
> flood the list with a huge email if it isn't necessary.

This is what I get:

[root@phenom ~]#  udevadm monitor --kernel --env --property
monitor will print the received events for:
KERNEL - the kernel uevent

KERNEL[1278510109.977326] add      /devices/vbd-2-51712 (xen-backend)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/vbd-2-51712
SUBSYSTEM=xen-backend
XENBUS_TYPE=vbd
XENBUS_PATH=backend/vbd/2/51712
XENBUS_BASE_PATH=backend
SEQNUM=2530

KERNEL[1278510110.042021] add      /devices/vbd-2-51744 (xen-backend)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/vbd-2-51744
SUBSYSTEM=xen-backend
XENBUS_TYPE=vbd
XENBUS_PATH=backend/vbd/2/51744
XENBUS_BASE_PATH=backend
SEQNUM=2531

KERNEL[1278510110.112319] add      /devices/vif-2-0 (xen-backend)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/vif-2-0
SUBSYSTEM=xen-backend
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/2/0
XENBUS_BASE_PATH=backend
SEQNUM=2532

KERNEL[1278510110.134121] add      /devices/vif-2-0/net/vif2.0 (net)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/vif-2-0/net/vif2.0
SUBSYSTEM=net
INTERFACE=vif2.0
IFINDEX=6
SEQNUM=2533

KERNEL[1278510110.134562] online   /devices/vif-2-0 (xen-backend)
UDEV_LOG=3
ACTION=online
DEVPATH=/devices/vif-2-0
SUBSYSTEM=xen-backend
DRIVER=vif
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/2/0
XENBUS_BASE_PATH=backend
script=/etc/xen/scripts/vif-bridge
vif=vif2.0
SEQNUM=2534

KERNEL[1278510110.343838] add      /devices/console-2-0 (xen-backend)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/console-2-0
SUBSYSTEM=xen-backend
XENBUS_TYPE=console
XENBUS_PATH=backend/console/2/0
XENBUS_BASE_PATH=backend
SEQNUM=2535


and then when I shut the guest:

5

KERNEL[1278510216.746063] offline  /devices/vif-2-0 (xen-backend)
UDEV_LOG=3
ACTION=offline
DEVPATH=/devices/vif-2-0
SUBSYSTEM=xen-backend
DRIVER=vif
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/2/0
XENBUS_BASE_PATH=backend
script=/etc/xen/scripts/vif-bridge
vif=vif2.0
SEQNUM=2536

KERNEL[1278510216.785420] remove   /devices/vif-2-0/net/vif2.0 (net)
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/vif-2-0/net/vif2.0
SUBSYSTEM=net
INTERFACE=vif2.0
IFINDEX=6
SEQNUM=2537


KERNEL[1278510217.514812] remove   /devices/console-2-0 (xen-backend)
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/console-2-0
SUBSYSTEM=xen-backend
XENBUS_TYPE=console
XENBUS_PATH=backend/console/2/0
XENBUS_BASE_PATH=backend
SEQNUM=2538

KERNEL[1278510217.588877] remove   /devices/vbd-2-51712 (xen-backend)
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/vbd-2-51712
SUBSYSTEM=xen-backend
XENBUS_TYPE=vbd
XENBUS_PATH=backend/vbd/2/51712
XENBUS_BASE_PATH=backend
SEQNUM=2539

KERNEL[1278510217.596581] remove   /devices/vbd-2-51744 (xen-backend)
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/vbd-2-51744
SUBSYSTEM=xen-backend
XENBUS_TYPE=vbd
XENBUS_PATH=backend/vbd/2/51744
XENBUS_BASE_PATH=backend
SEQNUM=2540


KERNEL[1278510217.602293] remove   /devices/vif-2-0 (xen-backend)
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/vif-2-0
SUBSYSTEM=xen-backend
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/2/0
XENBUS_BASE_PATH=backend
SEQNUM=2541

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

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