search for: libxl_device_

..._path) return -1; - } + if (libxl_domid_to_uuid(ctx, &uuid, domid) < 0) { - XL_LOG(ctx, XL_LOG_ERROR, "failed ot get uuid for %d\n", domid); + XL_LOG(ctx, XL_LOG_ERROR, "failed ot get uuid for %d", domid); return -1; } if (libxl_device_pci_shutdown(ctx, domid) < 0) - XL_LOG(ctx, XL_LOG_ERROR, "pci shutdown failed for domid %d\n", domid); + XL_LOG(ctx, XL_LOG_ERROR, "pci shutdown failed for domid %d", domid); xs_write(ctx->xsh, XBT_NULL, libxl_sprintf(ctx, "/local/doma...

The following series of patches fill in most of the gaps in the OCaml bindings to libxl, to make them useful for clients such as xapi/xenopsd (from XCP). There are a number of bugfixes to the existing bindings as well. I have an experimental version of xenopsd that successfully uses the new bindings. An earlier version of the first half of the series was submitted to the last by Ian Campbell on

...uint32_t *domid) +{ + if (!name) + return 0; + return libxl_domain_qualifier_to_domid(libxl__gc_owner(gc), name, domid); +} + /******************************************************************************/ int libxl__device_vtpm_setdefault(libxl__gc *gc, libxl_device_vtpm *vtpm) { if(libxl_uuid_is_nil(&vtpm->uuid)) { libxl_uuid_generate(&vtpm->uuid); } - return 0; + return libxl__resolve_domid(gc, vtpm->backend_domname, &vtpm->backend_domid); } static int libxl__device_from_vtpm(libxl__gc *gc, uint32_t domid, @@ -1...

...nse to generate are now accounted for. * disabled destructor generation for types which have no interesting fields (i.e. had empty destructor functions). I have retained the empty destructors for types which belong to a set where some types do have a valid need for a destructor funntion (e.g. libxl_device_* or libxl_*info) * Audit for usages of libxl_device_* and libxl_*info which can use the new destructors. I''m sure I haven''t caught them all. Tested with: create destroy (w/ valgrind) block-list (w/ valgrind) network-list (w/ valgrind) networ...

...* If it is set, callers may use hvm.usbversion to specify if the usb + * controller is usb1, usb2 or usb3. + * + * If this is not defined, the hvm.usbversion field does not exist. + */ +#define LIBXL_HAVE_BUILDINFO_USBVERSION 1 + +/* * LIBXL_HAVE_DEVICE_BACKEND_DOMNAME * * If this is defined, libxl_device_* structures containing a backend_domid diff --git a/tools/libxl/libxl_create.c b/tools/libxl/libxl_create.c index 9d793ba..14009dc 100644 --- a/tools/libxl/libxl_create.c +++ b/tools/libxl/libxl_create.c @@ -280,6 +280,15 @@ int libxl__domain_build_info_setdefault(libxl__gc *gc, libxl_defb...

.../* + * LIBXL_HAVE_USB indicates the functions for doing hot-plug of + * USB devices. + */ +#define LIBXL_HAVE_USB 1 + +/* * libxl ABI compatibility * * The only guarantee which libxl makes regarding ABI compatibility @@ -735,6 +741,37 @@ int libxl_cdrom_insert(libxl_ctx *ctx, uint32_t domid, libxl_device_disk *disk, const libxl_asyncop_how *ao_how) LIBXL_EXTERNAL_CALLERS_ONLY; +/* + * USB + * + * For each device removed or added, one of these protocols is available: + * - PV (i.e., PVUSB) + * - DEVICEMODEL (i.e, qemu) + * + * PV is available for eit...