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

[Xen-devel] [PATCH v1 00/12] libxl: add driver domain backend daemon

This patch series introduces support to launch device backends from
driver domains using libxl, removing the need to setup udev on driver

The daemon currently supports vbds, vifs and qdisks as backends.

Patches from 1 to 11 focus on getting libxl to work on driver domains,
and add several helper functions that will be used to build the
infraestructure needed for libxl to work on domains different than

The last patch (12) adds a new xl command, "devd", that can be used to
launch a daemon that will listen to changes in the xenstore "backend"
directory for the domain and perform the necessary actions to attach
the devices.

Changes since RFC:
 * Added documentation for the new xenstore paths created on path 4.
 * Synchronize the removal of devices from the driver domain with the 
   toolstack domain.

* Acked
*[PATCH v1 01/12] libxl/hotplug: add support for getting domid
*[PATCH v1 02/12] libxl: remove unneeded libxl_domain_info in
*[PATCH v1 03/12] libxl: make hotplug execution conditional on
 [PATCH v1 04/12] libxl: create a local xenstore libxl and
 [PATCH v1 05/12] libxl: don't remove device frontend path from
 [PATCH v1 06/12] libxl: synchronize device removal when using driver
 [PATCH v1 07/12] libxl: remove the Qemu bodge for driver domain
 [PATCH v1 08/12] libxl: don't launch Qemu on Dom0 for Qdisk devices
 [PATCH v1 09/12] libxl: add Qdisk backend launch helper
 [PATCH v1 10/12] xl: put daemonize code in it's own function
 [PATCH v1 11/12] libxl: revert 326a7b74
 [PATCH v1 12/12] libxl: add device backend listener in order to

Xen-devel mailing list



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