From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: philip tricca <flihp@twobit.us>
Cc: xen-devel@lists.xensource.com
Subject: Re: no udev events in netback domU driver domain 2.6.32.14
Date: Wed, 7 Jul 2010 09:45:05 -0400 [thread overview]
Message-ID: <20100707134505.GC4823@phenom.dumpdata.com> (raw)
In-Reply-To: <4C33E093.7090301@twobit.us>
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@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-07-07 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 2:04 no udev events in netback domU driver domain 2.6.32.14 philip tricca
2010-07-07 13:45 ` Konrad Rzeszutek Wilk [this message]
2010-07-08 21:34 ` philip tricca
2010-07-12 15:13 ` Konrad Rzeszutek Wilk
2010-07-14 21:16 ` philip tricca
-- strict thread matches above, loose matches on Subject: below --
2010-07-09 19:27 no udev events in netback domU driver domain, 2.6.32.14 Steven Harp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100707134505.GC4823@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=flihp@twobit.us \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.