Displaying 3 results from an estimated 3 matches for "libxl_toolstack_domid".
2012 Aug 14
4
[PATCH] libxl: fix usage of backend parameter and run_hotplug_scripts
...return ERROR_FAIL;
+ run_hotplug_scripts = libxl__hotplug_settings(gc, XBT_NULL);
+ if (run_hotplug_scripts < 0) {
+ LOG(ERROR, "unable to get current hotplug scripts execution setting");
+ return run_hotplug_scripts;
+ }
+ if (nic->backend_domid != LIBXL_TOOLSTACK_DOMID && run_hotplug_scripts) {
+ LOG(ERROR, "the vif ''backend='' option cannot be used in conjunction "
+ "with run_hotplug_scripts, please set run_hotplug_scripts "
+ "to 0 in xl.conf");
+ return ER...
2013 Apr 12
11
[PATCH v4 1/2] libxl: postpone backend name resolution
This adds a backend_domname field in libxl devices that contain a
backend_domid field, allowing either a domid or a domain name to be
specified in the configuration structures. The domain name is resolved
into a domain ID in the _setdefault function when adding the device.
This change allows the backend of the block devices to be specified
(which previously required passing the libxl_ctx down
2013 Oct 21
36
[PATCH 0 of 5 V3] Remus/Libxl: Network buffering support
This patch series adds support for network buffering in the Remus
codebase in libxl.
Changes in V3:
[1/5] Fix redundant checks in configure scripts
(based on Ian Campbell''s suggestions)
[2/5] Introduce locking in the script, during IFB setup.
Add xenstore paths used by netbuf scripts
to xenstore-paths.markdown
[3/5] Hotplug scripts setup/teardown invocations are now