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

[Xen-devel] no udev events in netback domU driver domain 2.6.32.14

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] no udev events in netback domU driver domain 2.6.32.14
From: philip tricca <flihp@xxxxxxxxx>
Date: Tue, 06 Jul 2010 22:04:03 -0400
Delivery-date: Tue, 06 Jul 2010 19:05:04 -0700
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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird 2.0.0.24 (X11/20100329)
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).

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.

TIA,
- Philip


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

<Prev in Thread] Current Thread [Next in Thread>