similar to: [PATCH] libxl: make domain resume API asynchronous

Changes since v1: - Fix a double-free bug introduced by v1, pointed out by Stefano where internal pointer was being passed back to caller from libxl_create_stubdom() 8<---------------------------------------------------------------------- Currently scratch variables allocated by libxl have the same lifetime as the context. While this is suitable for one off invocations of xl. It is not

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1317224719 -3600 # Node ID f63f089585652829ec3816590292fde32ee8fbfe # Parent 5f25a693b738d2578e8803ba7ee49da1f5495a03 libxl: correctly propagate errors from libxl_domain_resume currently it return success no matter what. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> diff -r 5f25a693b738 -r

This patch exposes a generic interface which can be expanded in the future to implement USB for PVUSB, qemu, and stubdoms. It can also be extended to include other types of USB other than host USB (for example, tablets, mice, or keyboards). For each device removed or added, one of two protocols is available: * PVUSB * qemu (DEVICEMODEL) The caller can additionally specify "AUTO", in

# HG changeset patch # User Ian Campbell <ian.campbell@citrix.com> # Date 1337273492 -3600 # Node ID cdb947baea102aa6a1d53472f8a3e5f2d6cc485e # Parent ac45608496cd85b0bf1aed6e5b869b4a86ca672f libxl: do not overwrite user supplied config when running bootloader. Currently when running the bootloader libxl will update b_info->u.pv.kernel, .ramdisk, .cmdline and .bootloader. This can

# HG changeset patch # User Roger Pau Monne <roger.pau@entel.upc.edu> # Date 1326564288 -3600 # Node ID 259112aee618753552056e398f940d1fd9fcc6f7 # Parent f581bb82fecd51e8fbd9c2e4ae9e76b08a695587 libxl: fix mutex initialization The macro PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP is not defined on NetBSD, so define mutex attributes manually. Changes since v1: * Fix leak of mutex attr.

libxenlight exports a function libxl_uuid2string which is used internally in several places but has one external caller in xl. The function mainly implements policy so should not be part of the libxenlight API. The extent to which it can be considered mechanism it is not a xen mechanism since UUID''s are not a concept exlusive to xen. The one caller in xl seems to be an

Ian Campbell wrote: > On Mon, 2013-09-09 at 03:29 +0000, Liu, Jinsong wrote: >> From 18344216b432648605726b137b348f28ef64a4ef Mon Sep 17 00:00:00 >> 2001 >> From: Liu Jinsong <jinsong.liu@intel.com> >> Date: Fri, 23 Aug 2013 23:30:23 +0800 >> Subject: [PATCH V3] xl: HVM domain S3 bugfix >> >> Currently Xen hvm s3 has a bug coming from the

From 18344216b432648605726b137b348f28ef64a4ef Mon Sep 17 00:00:00 2001 From: Liu Jinsong <jinsong.liu@intel.com> Date: Fri, 23 Aug 2013 23:30:23 +0800 Subject: [PATCH V3] xl: HVM domain S3 bugfix Currently Xen hvm s3 has a bug coming from the difference between qemu-traditioanl and qemu-xen. For qemu-traditional, the way to resume from hvm s3 is via ''xl trigger'' command.

To remove a pci passthough device from QEMU (upstream). Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> --- tools/libxl/libxl_internal.h | 2 ++ tools/libxl/libxl_qmp.c | 35 +++++++++++++++++++++++++++++++++++ 2 files changed, 37 insertions(+), 0 deletions(-) diff --git a/tools/libxl/libxl_internal.h b/tools/libxl/libxl_internal.h index 1dff211..84da6b1 100644 ---

Changes since v1: - Include nic,net2,vkb,vfb init functions --- This allows libxl users to get some sane default values for this complex set of structures. This is purely code movement and there are no functional changes except for a trivial error handling change in nic device init. Signed-off-by: Gianni Tedesco <gianni.tedesco@citrix.com> diff -r efe2d3ea22ae tools/libxl/libxl.c ---

* Introduce new variants of the logging functions which include errno values (converted using strerror) in the messages passed to the application''s logging callback. * Use the new errno-including logging functions everywhere where appropriate. In general, xc_... functions return errno values or 0; xs_... functions return 0 or -1 (or some such) setting errno. * When

Signed-off-by: Vincent Hanquez <vincent.hanquez@eu.citrix.com> --- tools/ocaml/Makefile | 2 +- tools/ocaml/common.make | 2 +- tools/ocaml/libs/xl/xl.ml | 209 ++++++++++++ tools/ocaml/libs/xl/xl.mli | 209 ++++++++++++ tools/ocaml/libs/xl/xl_stubs.c | 706 ++++++++++++++++++++++++++++++++++++++++ 5 files changed, 1126 insertions(+), 2 deletions(-)

Hello, When statically linking the following program: #include <stdio.h> #include <xenctrl.h> #include <xenguest.h> int main(void) { printf("%p\n", xc_domain_resume); printf("%p\n", xc_domain_save); return 0; } gcc -static test.c -o test -lxenguest -lxenctrl -lpthread -lz we get

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

--------------------------------------------------------------------------- Backport of the following patch from development: # User Ian Campbell <[hidden email]> # Date 1309968705 -3600 # Node ID e4781aedf817c5ab36f6f3077e44c43c566a2812 # Parent 700d0f03d50aa6619d313c1ff6aea7fd429d28a7 libxl: attempt to cleanup tapdisk processes on disk backend destroy. This patch properly terminates the

--------------------------------------------------------------------------- The following patch when applied on top of: libxl: attempt to cleanup tapdisk processes on disk backend destroy. Establishes correct cleanup behavior for blktap devices. This patch implements the release of the backend device before calling for the destruction of the userspace component of the blktap device. Without

When xl is called to create a domU and there is not enough memory available, then the autoballooning is called to extract memory from dom0. During the ballooning a loop in libxl_wait_for_free_memory() waits unless enough memory is available to create the domU. But because of a variable-underflow the loop can finish too soon and xl finally aborts with the message: xc: error: panic:

# HG changeset patch # User George Dunlap <george.dunlap@eu.citrix.com> # Date 1345022863 -3600 # Node ID 0982bad392e4f96fb39a025d6528c33be32c6c04 # Parent dc56a9defa30312a46cfb6ddb578e64cfbc6bc8b xl: Suppress spurious warning message for cpupool-list libxl_cpupool_list() enumerates the cpupools by "probing": calling cpupool_info, starting at 0 and stopping when it gets an error.

Source: xen Version: 4.17.3+10-g091466ba55-1 Severity: serious Tags: patch pending sid trixie Justification: library ABI skew on upgrade User: debian-arm at lists.debian.org Usertags: time-t NOTICE: these changes must not be uploaded to unstable yet! Dear maintainer, As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond

This is problem 1 of 3 problems we are having with live migration and/or ACPI on Xen-4.3 and Xen-4.2. Any help would be appreciated. Detailed description of problem: We are using Xen-4.3-rc1 with dom0 running Ubuntu Precise and 3.5.0-23-generic kernel, and domU running Ubuntu Precise (12.04) cloud images running 3.2.0-39-virtual. We are using the xl.conf below on qemu-upstream-dm and HVM and