Re: [Xen-devel] Cannot create domU - Keir Fraser - com.xensource.lists.xen-devel

21 messages in com.xensource.lists.xen-develRe: [Xen-devel] Cannot create domU

From	Sent On	Attachments
NAHieu	23 Sep 2005 07:14
Michael Vrable	23 Sep 2005 10:37
Michael Vrable	23 Sep 2005 10:42
Michael Vrable	23 Sep 2005 10:59
Chris Bainbridge	23 Sep 2005 15:38
Keir Fraser	24 Sep 2005 00:38
Chris Bainbridge	24 Sep 2005 03:53
Keir Fraser	24 Sep 2005 06:21
NAHieu	24 Sep 2005 10:31
Chris Bainbridge	24 Sep 2005 12:59
Keir Fraser	25 Sep 2005 03:19
Keir Fraser	26 Sep 2005 06:23
Keir Fraser	26 Sep 2005 07:41
Gerd Knorr	26 Sep 2005 07:59	.rules, .Other
Greg KH	26 Sep 2005 08:01
Keir Fraser	26 Sep 2005 08:40
Chris Bainbridge	26 Sep 2005 08:54
Greg KH	26 Sep 2005 14:21
Chris Bainbridge	27 Sep 2005 08:33
Chris Bainbridge	30 Sep 2005 07:47
Gerd Knorr	06 Oct 2005 08:53	.rules, .Other, .Other

Subject:	Re: [Xen-devel] Cannot create domU
From:	Keir Fraser (Keir...@cl.cam.ac.uk)
Date:	09/26/2005 07:41:16 AM
List:	com.xensource.lists.xen-devel

On 26 Sep 2005, at 15:14, Greg KH wrote:

That's been "depreciated" for quite some time now. I would recommend you switch to moving your script to /etc/hotplug.d/xen/ or /etc/hotplug.d/default/ (depending on how your hotplug event is being created. Which reminds me, how is it? Pointers to code anywhere?)

We originally placed the script in /etc/hotplug.d/xen, but found that didn't work on some distros. Can't remember which ones, nor how old they were. We should perhaps detect such systems and treat them specially in our install script, and move the script back to /etc/hotplug.d by default.

Our main hotplug event function is in drivers/xen/xenbus/xenbus_probe.c, I think (it's used by our network driver at least). Actually xenbus registers all our virtual devices with sysfs, and I guess that generates some hotplug events automatically?

-- Keir