[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 20 of 29 RFC] libxl: introduce libxl hotplug public API functions

Ian Campbell writes ("Re: [Xen-devel] [PATCH 20 of 29 RFC] libxl: introduce 
libxl hotplug public API functions"):
> I was wondering if perhaps xl/libxl should handle these events by
> default (using the same APIs as xldeviced uses) such that in the simple
> case users can continue to just use xl without worrying about
> configuring or enabling additional daemons. There would then be an
> option to disable this if you were running xldeviced (either in dom0 or
> in a driver dom). Perhaps a more DWIM extension would be to default to
> running things within xl/libxl only if the backend is in dom0 and assu,e
> xldeviced is running in backend doms != 0.

This is a good idea.  It can probably be implemented with some kind of
loopback function which either runs the script, or communicates with
the xldeviced via xenstore.

> Do you integrate with the libxl event loop? If you did wouldn't this be
> trivial to handle in xl and wouldn't the xldeviced become the trivial
> setup + run the event loop program?

That would be one way to look at it.

  void libxl_xldeviced_enter(libxl_ctx*); /* never returns */


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.