Re: [Xen-devel] [PATCH v2 4/5] libxl: call hotplug scripts from libxl for vif

[Roger Pau Monne <roger.pau@xxxxxxxxxx>]

On 18 Apr 2012, at 14:31, Ian Campbell wrote:

> > > It's probably too late in the 4.2 cycle to direct the tap hotplug
> > > script
> > > to a different backend dir so I think the best thing to do for now 
> > > is
> > > to
> > > put this key somewhere else so that it doesn't become a guest 
> > > visible
> > > API (which is what happens with where you have put it). The same 
> > > place
> > > as udev_disable would work fine.
> > Does this paths sound ok:
> >
> > /libxl/devices/<domid>/nic/<devid>/udev_disable
> > /libxl/devices/<domid>/nic/<devid>/type
> Works for me.
I've just realized that it's not possible to use exactly this paths, 
because then I won't be able to set the HOTPLUG_GATE env from the udev 
rules file, so I think something like:
/libxl/backend/vif/7/0

Is one of the only options left. Here are the env variable available 
when calling a hotplug script from udev:
UDEV_LOG=3
ACTION=remove
DEVPATH=/devices/vif-7-0
SUBSYSTEM=xen-backend
XENBUS_TYPE=vif
XENBUS_PATH=backend/vif/7/0
XENBUS_BASE_PATH=backend
SEQNUM=1382

So I would set ENV{HOTPLUG_GATE} as /libxl/$XENBUS_PATH

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel