From mboxrd@z Thu Jan 1 00:00:00 1970 From: philip tricca Subject: no udev events in netback domU driver domain 2.6.32.14 Date: Tue, 06 Jul 2010 22:04:03 -0400 Message-ID: <4C33E093.7090301@twobit.us> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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