search for: libxl_device_disk

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=[ ''tap:qcow2:/var/li...

This patch series provides the facility to eject and insert a cdrom when the used device-model is qemu-xen. The only difference between both device-model is a call to a QMP command as `xl cd-insert ...` will still update xenstore, even if it''s not used by QEMU. Anthony PERARD (3): libxl_qmp, Introduce libxl__qmp_insert_cdrom. libxl_dm: Set an id to cdrom drives with qemuu. libxl:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, 4.2 and 4.1 suffers from SEGV during xl network-attach in libxl__device_nic_add. In 4.3-unstable it is fixed by: 5420f2650 libxl: Set vfb and vkb devid if not done so by the caller So either the patch need to be backported to 4.1 and 4.2, or fixed by this one: - ------ libxl: Fix SEGV in network-attach When "device/vif" directory

...ootloader configured. - * - * Users should call libxl_file_reference_unmap on the kernel and - * ramdisk to cleanup or rely on libxl_domain_{build,restore} to do - * it. - */ -int libxl_run_bootloader(libxl_ctx *ctx, - libxl_domain_build_info *info, - libxl_device_disk *disk, - uint32_t domid, - libxl_asyncop_how *ao_how); - - /* 0 means ERROR_ENOMEM, which we have logged */ - - int libxl_domain_rename(libxl_ctx *ctx, uint32_t domid, const char *old_name, const char *new_name); diff -r a...

The following series implements libxl_domain_config_init as per the libxl API requirement that each type has an init function. The first function does this in an open coded manner and is proposed for Xen 4.2. The second function is RFC only since it moves the definition of this type into the IDL and makes the required infrastructure updates to enable this. I think this is more 4.3 material at

Hi, I am doing some experimentation with xen and Ceph and have a problem booting my guest when my disk = [] uses an alternate block script. Installation from a .iso was ok since the boot device was a file but now trying to boot from the rbd neither the hvmbuilder or pygrub can start as they treat the first value after target= as the /dev node to try and use. My disk parameter looks like: disk =

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.

$ git checkout RELEASE-4.2.2 $ git clean -ffdx [do a build, install, reboot] $ xl create a0 $ xl cd-eject a0 hdc [However, the guest OS still sees the CD inserted] $ xl block-list a0 Segmentation fault $ xl cd-insert a0 hdc file:/images/xs-tools-6.0.0.iso Segmentation fault The problem seems to be that xl cd-eject is writing corrupt values to xenstore. Note that vbd/1/5632 is still there

...-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> diff -r 0f0a25c4c991 tools/libxl/xl_cmdimpl.c --- a/tools/libxl/xl_cmdimpl.c Thu May 20 09:18:33 2010 -0700 +++ b/tools/libxl/xl_cmdimpl.c Thu May 20 14:37:24 2010 -0700 @@ -3444,7 +3444,7 @@ uint32_t fe_domid, be_domid = 0; libxl_device_disk disk = { 0 }; - if ((argc < 3) || (argc > 6)) { + if ((argc < 4) || (argc > 6)) { help("block-attach"); exit(0); } @@ -3489,7 +3489,7 @@ } disk.virtpath = argv[3]; disk.unpluggable = 1; - disk.readwrite = (argv[4][0] == '...

...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, @@ -1968,6 +1976,7 @@ int libxl__device_disk_setdefault(libxl__gc *gc, libxl_device_disk *disk) rc = libxl__device_disk_set_backend(gc, disk); if (rc) return rc; + rc = libxl__resolve_domid(gc, disk->backend_domname, &disk->backend_domid); return rc; } @@ -2799,7 +2808,7 @@ int libxl__device_nic_setdefault(libxl__gc *gc, libxl_device_nic *nic,...

...Iu32, target_memkb / 1024); if (enforce || !domid) diff -r dc335ebde3b5 tools/libxl/libxl.h --- a/tools/libxl/libxl.h Thu Aug 12 18:03:23 2010 +0100 +++ b/tools/libxl/libxl.h Fri Aug 13 15:32:31 2010 +0100 @@ -362,7 +362,6 @@ int libxl_run_bootloader(libxl_ctx *ctx, libxl_device_disk *disk, uint32_t domid); -char *libxl_uuid2string(libxl_ctx *ctx, const libxl_uuid uuid); /* 0 means ERROR_ENOMEM, which we have logged */ /* events handling */ diff -r dc335ebde3b5 tools/libxl/libxl_dom.c --- a/tools/libxl/libxl_dom.c Thu Aug 12 18:03:23 2010 +0100...

...f (is_hvm(ctx,domid)) { @@ -684,6 +729,7 @@ int libxl_domain_shutdown(libxl_ctx *ctx } } } + libxl_free_all(&gc); return 0; } @@ -705,7 +751,8 @@ int libxl_wait_for_domain_death(libxl_ct int libxl_wait_for_disk_ejects(libxl_ctx *ctx, uint32_t guest_domid, libxl_device_disk *disks, int num_disks, libxl_waiter *waiter) { - int i; + libxl_gc gc = LIBXL_INIT_GC(ctx); + int i, rc = -1; uint32_t domid = libxl_get_stubdom_id(ctx, guest_domid); if (!domid) @@ -713,14 +760,17 @@ int libxl_wait_for_disk_ejects(libxl_ctx for (i = 0; i < num_disks...

The series introduces auto-generation of the type definitions used in the libxl interface followed by auto-generation of a destructor function for each type. In the future it may be possible to use the related data structures for other purposes, for example auto-generation of the functions to marshal between C and language binding data types. tools/_libxl_types.h should be identical both before

...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 --- a/tools/libxl/libxl.c Tue Jan 11 15:30:48 2011 +0000 +++ b/tools/libxl/libxl.c Tue Jan 11 15:40:45 2011 +0000 @@ -1024,6 +1024,35 @@ int libxl_device_disk_local_detach(libxl } /******************************************************************************/ +int libxl_device_nic_init(libxl_device_nic *nic_info, int devnum) +{ + const uint8_t *r; + libxl_uuid uuid; + + libxl_uuid_generate(&uuid); + r = libxl_uuid_bytearray(&uuid...

This patch adds a new option for xen config files for directly mapping hardware io memory into a vm. Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5 index 013270d..428da21 100644 --- a/docs/man/xl.cfg.pod.5 +++ b/docs/man/xl.cfg.pod.5 @@ -496,6 +496,17 @@ is given in hexadecimal and may either a span e.g.

...+ c_val->u.pv.slack_memkb = Int64_val(Field(infopriv, 0)); + c_val->u.pv.cmdline = String_val(Field(infopriv, 1)); + c_val->u.pv.ramdisk = String_val(Field(infopriv, 2)); + c_val->u.pv.features = String_val(Field(infopriv, 3)); + } + + CAMLreturn(0); +} + +static int device_disk_val(libxl_device_disk *c_val, value v) +{ + CAMLparam1(v); + + c_val->backend_domid = Int_val(Field(v, 0)); + c_val->physpath = String_val(Field(v, 1)); + c_val->phystype = (Int_val(Field(v, 2))) + PHYSTYPE_QCOW; + c_val->virtpath = String_val(Field(v, 3)); + c_val->unpluggable = Bool_val(Field(v, 4)); +...

* 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

I think I posted this patch before, but it looks like it was in December 2012 (!). 1/1 libxl: introduce an option for disabling the non-O_DIRECT workaround Ideally it would go into 4.4, at least. Provided the corresponding qemu part has gone into qemu-xen, which I think it has. Can anyone confirm ?

.../* + * 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 either...

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