From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Bainbridge Subject: Re: xen_blk timeout connecting to device Date: Wed, 5 Oct 2005 19:50:02 +0100 Message-ID: <623652d50510051150x13a260d6q@mail.gmail.com> References: <9e246b4d0510050618m2af7f13cu39e1f4ddbd1a3f2a@mail.gmail.com> Reply-To: Chris Bainbridge Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <9e246b4d0510050618m2af7f13cu39e1f4ddbd1a3f2a@mail.gmail.com> Content-Disposition: inline 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 On 05/10/05, Tim Durack wrote: > I have hotplug and udev installed, but am seeing the same problem. "cat /proc/sys/kernel/hotplug". /sbin/hotplug seems to work for everyone (?). /sbin/udevsend needs udev rules. The backward compatible udev rules should work, but don't. Some notes on debugging this stuff, in case anyone else has problems in /etc/udev/udev.conf add: udev_log=3D"info" In /etc/hotplug.d/default/default.hotplug: DEBUG=3Dyes export DEBUG In /etc/hotplug/xen-backend.agent: add "set -x" as 2nd line. You should now get debug info in either /var/log/messages or /var/log/udev (depends on syslog setup). I gave up with the hotplug stuff, and used the udev rules I posted a few days ago. If you go that route comment out this line from /etc/udev/rules.d/50-udev.rules: ENV{UDEVD_EVENT}=3D=3D"1", RUN+=3D"/sbin/udev_run_hotplugd" That will disable the backward compatible hotplug stuff which seems to be broken with respect to xen. You will now be able to see the udev events and rules in your log file, and exactly what is going on in the scripts you execute (echo to stdout will be syslogged by udev). After that it's just a matter of tying together the unhandled events with actions.