WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Is the hotplug/udev stuff worth the troubles?

To: Michael Holzt <kju-xen@xxxxxxxx>
Subject: Re: [Xen-devel] Is the hotplug/udev stuff worth the troubles?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 4 Dec 2005 15:50:17 +0000
Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 04 Dec 2005 15:59:49 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051204135754.GA1960@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20051204135754.GA1960@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 4 Dec 2005, at 13:57, Michael Holzt wrote:

There is nothing
changing in my setup during this, so why do i need hotplug? Now, i don't
know why you have opted to use hotplug in Xen 3. Maybe it has big
advantages which i fail to see. Maybe someone who knows can explain
why hotplug is needed.

Main reason is for dynamic creation of virtual devices. The best example is that every guest network interface needs a 'backend' virtual interface to be created in domain0, and that needs to be configured after creation. The callback for userspace to do that setup (e.g., attach to a bridge) is via hotplug. In 2.0 the config (attach to bridge xen-br0) was hardcoded in the kernel. Which is a nice simple solution but hardly flexible.

For simple setups that really don't want to be running full hotplug/udev scripts perhaps a solution is to hijack the hotplug callback utility -- e.g., install a very simple script or even C program, point /proc/sys/kernel/hotplug at it, and implement fairly 'dumb' setup policies in there. It's probably less effort to just get hotplug running though. :-)

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>