search for: libxl_device_disk_local_attach

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/lib/xen/images/...

I''m trying to create a pv guest with qcow/qcow2 disk image by xl, it always fails atlibxl_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 Does that mean we cannot create such a pv guest by xl? I''m no...

...domain_config *d_config, libxl_console_ready cb, void *priv, uint32_t *domid); int libxl_domain_create_restore(libxl_ctx *ctx, libxl_domain_config *d_config, libxl_console_ready cb, void *priv, uint32_t *domid, int restore_fd); @@ -419,16 +422,19 @@ int libxl_cdrom_insert(libxl_ctx *ctx, u char * libxl_device_disk_local_attach(libxl_ctx *ctx, libxl_device_disk *disk); int libxl_device_disk_local_detach(libxl_ctx *ctx, libxl_device_disk *disk); +int libxl_device_nic_init(libxl_device_nic *nic, int dev_num); int libxl_device_nic_add(libxl_ctx *ctx, uint32_t domid, libxl_device_nic *nic); int libxl_device_nic_del(libxl...

...end: Disk vdev=xvda, backend tap unsuitable because blktap not available libxl: debug: libxl_device.c:219:libxl__device_disk_set_backend: Disk vdev=xvda, using backend qdisk libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk vdev=xvda spec.backend=qdisk libxl: debug: libxl.c:1714:libxl_device_disk_local_attach: locally attaching qdisk /root/debian-blktap2.img libxl: error: libxl_create.c:603:do_domain_create: failed to run bootloader: -3 xc: debug: hypercall buffer: total allocations:14 total releases:14 xc: debug: hypercall buffer: current allocations:0 maximum allocations:2 xc: debug: hypercall buffer...

...xarray_free(back); flexarray_free(front); - return 0; +out: + libxl_free_all(&gc); + return rc; } int libxl_device_disk_del(libxl_ctx *ctx, @@ -1750,9 +1870,10 @@ int libxl_device_disk_del(libxl_ctx *ctx return libxl_device_del(ctx, &device, wait); } -const char * libxl_device_disk_local_attach(libxl_ctx *ctx, libxl_device_disk *disk) +char * libxl_device_disk_local_attach(libxl_ctx *ctx, libxl_device_disk *disk) { - char *dev = NULL; + libxl_gc gc = LIBXL_INIT_GC(ctx); + char *dev = NULL, *ret; int phystype = disk->phystype; switch (phystype) { case PHYSTY...

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.

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

What are the outstanding things to do before we think we can start on the 4.2 -rc''s? Does anyone have a timetable in mind? hypervisor: * ??? - Keir, Tim, Jan? tools: * libxl stable API -- we would like 4.2 to define a stable API which downstream''s can start to rely on not changing. Aspects of this are: * event handling (IanJ working