search for: libxl__log_error

Add commands to automatically prep devices for pass-through The current method for passing through devices requires users to either modify cryptic Linux boot parameters and reboot, or do a lot of manual reads and writes into sysfs nodes. This set of patches introduces commands to make this easier. It expands on the concept of "assignable" (from the list_assignable_devices command).

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and

Matthew Daley (13): libxl: fix unsigned less-than-0 comparison in e820_sanitize libxl: check for xc_domain_setmaxmem failure in libxl__build_pre libxl: correct file open success check in libxl__device_pci_reset libxl: don''t leak p in libxl__wait_for_backend libxl: remove unsigned less-than-0 comparison libxl: actually abort if initializing a ctx''s lock fails libxl:

...ause - * PTHREAD_RECURSIVE_MUTEX_INITIALIZER_NP is defined to be valid - * only as an initialiser, not as an expression. */ - memcpy(&ctx->lock, &mutex_value, sizeof(ctx->lock)); + if (libxl__init_recursive_mutex(ctx, &ctx->lock) < 0) { + LIBXL__LOG(ctx, LIBXL__LOG_ERROR, "Failed to initialize mutex"); + return ERROR_FAIL; + } if ( stat(XENSTORE_PID_FILE, &stat_buf) != 0 ) { LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "Is xenstore daemon running?\n" diff -r f581bb82fecd -r 259112aee618 tools/libxl/libxl_internal.c --- a...

Anthony PERARD (3): libxl_qmp: Use GC instead of CTX as parameter for _initialize. Provide dm_vnc() as a in libxl helper. libxl: Set VNC password through QMP tools/libxl/libxl_create.c | 2 +- tools/libxl/libxl_dm.c | 32 ++++++++++++++---------- tools/libxl/libxl_internal.h | 7 ++++- tools/libxl/libxl_qmp.c | 55 ++++++++++++++++++++++++++++++----------- 4 files

...2 @@ static int qmp_next(libxl__gc *gc, libxl__qmp_handler *qmp) FD_ZERO(&rfds); FD_SET(qmp->qmp_fd, &rfds); +do_select_again: ret = select(qmp->qmp_fd + 1, &rfds, NULL, NULL, &timeout); if (ret == 0) { LIBXL__LOG(qmp->ctx, LIBXL__LOG_ERROR, "timeout"); return -1; } else if (ret < 0) { + if (errno == EINTR) + goto do_select_again; LIBXL__LOG_ERRNO(qmp->ctx, LIBXL__LOG_ERROR, "Select error"); return -1; } rd = read(qm...

...rc; } -int libxl_domain_resume(libxl_ctx *ctx, uint32_t domid, int suspend_cancel) +int libxl__domain_resume(libxl__gc *gc, uint32_t domid, int suspend_cancel) { - GC_INIT(ctx); int rc = 0; - if (xc_domain_resume(ctx->xch, domid, suspend_cancel)) { - LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, - "xc_domain_resume failed for domain %u", - domid); + if (xc_domain_resume(CTX->xch, domid, suspend_cancel)) { + LOGE(ERROR, "xc_domain_resume failed for domain %u", domid); rc = ERROR_FAIL; goto out;...

Hi, the function libxl_domain_setmaxmem in libxl.c doesn''t seem to do anything besides argument checking, or am I overlooking something? Cheers, Markus _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, List, I''m trying xl create a pv guest with qcow/qcow2 image, it always fails at libxl_device_disk_local_attach. #xl create pv_config_file libxl: error: libxl.c:1119:libxl_device_disk_local_attach: cannot locally attach a qdisk image if the format is not raw libxl: error: libxl_create.c:467:do_domain_create: failed to run bootloader: -3 disk configuration is: disk=[

...t libxl__build_pv(libxl__gc *gc, uint3 xc_dom_loginit(ctx->xch); - dom = xc_dom_allocate(ctx->xch, info->u.pv.cmdline, info->u.pv.features); + dom = xc_dom_allocate(ctx->xch, state->pv_cmdline, info->u.pv.features); if (!dom) { LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, "xc_dom_allocate failed"); return ERROR_FAIL; } - if (info->u.pv.kernel.mapped) { + LOG(INFO, "pv kernel mapped %d path %s\n", state->pv_kernel.mapped, state->pv_kernel.path); + if (state->pv_kernel.mapped) { ret = xc_dom_kernel_mem...

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and

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 ---

I just built 4.3.0 in order to get > 2GB of RAM in domU with GPU passthrough without crashes. Unfortunately, the same crashes still happen. Massive frame buffer corruption on domU before it locks up solid. It seems the PCI memory stomp is still happening. I am using qemu-dm, as I did on Xen 4.2.x. So whatever fix for this went into 4.3.0 didn''t fix it for me. Passing less than 2GB

...; 0 && abs(target_memkb) > current_target_memkb) + new_target_memkb = 0; + else + new_target_memkb = current_target_memkb + target_memkb; + } else new_target_memkb = target_memkb; if (new_target_memkb > memorykb) { LIBXL__LOG(ctx, LIBXL__LOG_ERROR, _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...p; - disk->backend != DISK_BACKEND_QDISK) - device.backend_kind = DEVICE_TAP; - else - device.backend_kind = DEVICE_QDISK; + device.backend_kind = DEVICE_QDISK; break; default: LIBXL__LOG(ctx, LIBXL__LOG_ERROR, "unrecognized disk backend type: %d\n", disk->backend); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...ger_type = -1; + + if (!strcmp(trigger_name, "s3resume")) { + xc_set_hvm_param(ctx->xch, domid, HVM_PARAM_ACPI_S_STATE, 0); + return 0; + } + + trigger_type = trigger_type_from_string(trigger_name); if (trigger_type == -1) { LIBXL__LOG_ERRNOVAL(ctx, LIBXL__LOG_ERROR, -1, "Invalid trigger, valid triggers are <nmi|reset|init|power|sleep>"); _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

..."spicevmc,name=usbredir,id=usbrc%d", i), "-device", + libxl__sprintf(gc, "usb-redir,chardev=usbrc%d," + "id=usbrc%d", i, i), NULL); + } else { + LIBXL__LOG(CTX, LIBXL__LOG_ERROR, + "usbredirection parameter must be between 1 and 4"); + return NULL; + } + if (b_info->u.hvm.usbdevice) { flexarray_vappend(dm_args, "-usbdevice", b_info-&g...

..._qmp_handler *qmp, const libxl__json_object *resp) { callback_id_pair *pp = qmp_get_callback_from_id(qmp, resp); @@ -283,19 +283,17 @@ static void qmp_handle_error_response(libxl__qmp_handler *qmp, free(pp); } - LIBXL__LOG(qmp->ctx, LIBXL__LOG_ERROR, - "received an error message from QMP server: %s", - libxl__json_object_get_string(resp)); + LOG(ERROR, "received an error message from QMP server: %s", + libxl__json_object_get_string(resp)); } -static int qmp_handle_response(libxl__qmp...

I noticed recently that there is no real easy way to get the kernel driver for blktap working in mainline. I''ve pulled down the source from Daniel Stodden''s linux git tree on xensource, but it looks like it''s for debian and I''m running Fedora 14, so I''m trying to sort it out. I run the 3.1.x kernel and don''t want to go back to the 2.6.32 that