From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Bainbridge Subject: Re: Cannot create domU Date: Sat, 24 Sep 2005 10:54:07 +0000 Message-ID: <623652d50509240354750991d3@mail.gmail.com> References: <5d7aca9505092307156e0c7f00@mail.gmail.com> <20050923173759.GA25613@vrable.net> <623652d5050923153973b9804c@mail.gmail.com> <7d249e777fd88c08faab74751b15fca6@cl.cam.ac.uk> 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: <7d249e777fd88c08faab74751b15fca6@cl.cam.ac.uk> 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 List-Id: xen-devel@lists.xenproject.org On 24/09/05, Keir Fraser wrote: > On my box /proc/sys/kernel/hotplug points at /sbin/hotplug, which runs > a script in /etc/hotplug.d/defaults which then runs the appropriate > agent script (/etc/hotplug/xen-backend.agent). Ok, udevsend is the default hotplug event handler in Gentoo.. apparently /sbin/hotplug used to be, but has been deprecated ">From udev-047, udevd is capable of handling hotplug events from modules, as well as devices, and knows to call the appropriate hotplug rc script related to the module. (at module load, a hotplug event is generated by the kernel, and calls whatever is defined as the hotplug handler)." I just tried echo /sbin/hotplug > /proc/sys/kernel/hotplug and it works! Woohoo! I can now mount the virtual device. So... there is something wrong with either xen or udevsend that should be fixed. I have no experience with hotplug, but if someone can point me in the right direction I'll try to debug.