search for: libxl_device_disk_add

...</source> <target dev='xvdd' bus='xen'/> <serial>xxxxxxxx-7342-434b-9xx1-d046bcxxxxfd</serial> </disk> But there is no way to attach the device to running machine, I only see this error on libxl : libxl: debug: libxl.c:3538:libxl_device_disk_add: ao 0x7fe248006080: create: how=(nil) callback=(nil) poller=0x7fe24000ce20 libxl: debug: libxl_device.c:251:libxl__device_disk_set_backend: Disk vdev=xvdd spec.backend=qdisk libxl: debug: libxl_event.c:618:libxl__ev_xswatch_deregister: watch w=0x7fe248001780: deregister unregistered libxl: debug: l...

...block-attach nathannx "file:/mnt/test/disk" "xvdd4" DEBUG libxl__blktap_devpath 37 aio:/mnt/test/disk libxl: error: libxl.c:2149:device_disk_add: failed to get blktap devpath for 0xd3abd0 libxl: error: libxl.c:1727:device_addrm_aocomplete: unable to (null) device libxl_device_disk_add failed. I'm not sure why xen would care if the disk is writable? Would be nice to be able to mount these since many NFS storage arrays provide read only access to snapshots. - Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos...

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 =

...mnt/test/disk" > "xvdd4" > > DEBUG libxl__blktap_devpath 37 aio:/mnt/test/disk > > libxl: error: libxl.c:2149:device_disk_add: failed to get blktap devpath for > 0xd3abd0 > > libxl: error: libxl.c:1727:device_addrm_aocomplete: unable to (null) device > > libxl_device_disk_add failed. > > > > I'm not sure why xen would care if the disk is writable? Would be nice to be > able to mount these since many NFS storage arrays provide read only access > to snapshots. So by default, block-attach will set the access to a disk as read-write. If disk access i...

...tore (e.g. is a blktap1 thing). The usage in libxl_device_disk_del seems particularly dubious to me. diff -r 403080639e20 -r 281207ed3fb3 tools/libxl/libxl.c --- a/tools/libxl/libxl.c Tue Apr 05 17:26:32 2011 +0100 +++ b/tools/libxl/libxl.c Tue Apr 05 17:34:07 2011 +0100 @@ -1015,12 +1015,7 @@ int libxl_device_disk_add(libxl_ctx *ctx flexarray_append(back, "params"); flexarray_append(back, libxl__sprintf(&gc, "%s:%s", libxl__device_disk_string_of_format(disk->format), disk->pdev_path)); - - if (libxl__blktap_enabled(&amp...

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.

* 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

...changeset: 23030:87aa1277eae0 xen-unstable date: Sat Mar 12 13:19:02 2011 +0000 changeset: 22991:4f5534517e08 user: Ian Jackson <Ian.Jackson@eu.citrix.com> date: Fri Mar 11 18:35:15 2011 +0000 libxl: do not try to use blktap with qdisk libxl_device_disk_add tries to use blktap when available even for qdisk devices, this patch fixes it. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Acked-by: Ian Jackson <ian.jackson@eu.citrix.com> Committed-by: Ian Jackson <ian.jackson@eu.citrix.com>...

.../device/vfs",domid), perm, ARRAY_SIZE(perm)); if (!xs_transaction_end(ctx->xsh, t, 0)) if (errno == EAGAIN) goto retry_transaction; @@ -1429,26 +1510,32 @@ retry_transaction: for (i = 0; i < num_disks; i++) { disks[i].domid = domid; ret = libxl_device_disk_add(ctx, domid, &disks[i]); - if (ret) return ret; + if (ret) + goto out_free; } for (i = 0; i < num_vifs; i++) { vifs[i].domid = domid; ret = libxl_device_nic_add(ctx, domid, &vifs[i]); - if (ret) return ret; + if (ret) +...

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

...te(&c_state); + FREE_CTX(); + + CAMLreturn(result); +} + +value stub_xl_disk_add(value info, value domid) +{ + CAMLparam2(info, domid); + libxl_device_disk c_info; + struct libxl_ctx ctx; + int ret; + + device_disk_val(&c_info, info); + c_info.domid = Int_val(domid); + + INIT_CTX(); + ret = libxl_device_disk_add(&ctx, Int_val(domid), &c_info); + if (ret != 0) + failwith_xl("disk_add"); + FREE_CTX(); + CAMLreturn(Val_unit); +} + +value stub_xl_disk_remove(value info, value domid) +{ + CAMLparam2(info, domid); + libxl_device_disk c_info; + struct libxl_ctx ctx; + int ret; + + device_disk_v...

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