search for: diskpath

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

...hanks The 4.4.1-4 release only included one related fix there are actually two more: commit 379b351889a8f02abe30a06e2ce9ba8b381b91ab Author: Ian Campbell <ian.campbell at citrix.com> Date: Thu Nov 6 13:00:31 2014 +0000 tools: libxl: do not leak diskpath during local disk attach libxl__device_disk_local_initiate_attach is assigning dls->diskpath with a strdup of the device path. This is then passed to the callback, e.g. parse_bootloader_result but bootloader_cleanup will not free it....

...virt-manager` as I don't use it much > in my workflow. But if you have users who're comfortable with CLI, you > can import disk images into libvirt (and which will also be accessible > via `virt-manager`) tribvially: > > $ virt-install --name f21vm --ram 2048 \ > --diskpath=/export/f21vm.qcow2,format=qcow2,cache=writeback \ > --nographics --os-variant fedora21 --import > > (The above has the option '--nographics' because, it's just a small, > server image, but still - when the image is imported into libvirt, it > should be accessible v...

Hi. I need to get ability to download backups of kvm virtual machines (raw images) to end users. Virtualbox users can import ovs images, that i can create, but in case of linux and virt-manager - how users can import images and simply run it? I think about newbie linux users, that can install virt-manager under ubuntu via graphical package manager and do some easy steps... Can you share me info

...} - libxl_free(ctx, b); } + libxl_free_all(&gc); return ret; } int libxl_device_disk_getinfo(libxl_ctx *ctx, uint32_t domid, libxl_device_disk *disk, libxl_diskinfo *diskinfo) { + libxl_gc gc = LIBXL_INIT_GC(ctx); char *dompath, *diskpath; char *val; - dompath = libxl_xs_get_dompath(ctx, domid); + dompath = libxl_xs_get_dompath(&gc, domid); diskinfo->devid = device_disk_dev_number(disk->virtpath); /* tap devices entries in xenstore are written as vbd devices. */ - diskpath = libxl_sprintf(ctx, &...

...opposed to ~500kb for wheezy i386 guests. At guest reboot it jumps to 17mb and then, after a few seconds, to ~34mb. I also rebooted the host to help make sure the test is valid. Thanks, Gedalya -------------- next part -------------- A non-text attachment was scrubbed... Name: 0039-do-not-leak-diskpath-during-localdisk-attach.patch Type: text/x-patch Size: 407 bytes Desc: not available URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20141107/856667fe/attachment.bin>

...t have immediate steps with `virt-manager` as I don't use it much in my workflow. But if you have users who're comfortable with CLI, you can import disk images into libvirt (and which will also be accessible via `virt-manager`) tribvially: $ virt-install --name f21vm --ram 2048 \ --diskpath=/export/f21vm.qcow2,format=qcow2,cache=writeback \ --nographics --os-variant fedora21 --import (The above has the option '--nographics' because, it's just a small, server image, but still - when the image is imported into libvirt, it should be accessible via virt-manager, albiet...

...se it much > > in my workflow. But if you have users who're comfortable with CLI, you > > can import disk images into libvirt (and which will also be accessible > > via `virt-manager`) tribvially: > > > > $ virt-install --name f21vm --ram 2048 \ > > --diskpath=/export/f21vm.qcow2,format=qcow2,cache=writeback \ > > --nographics --os-variant fedora21 --import > > > > (The above has the option '--nographics' because, it's just a small, > > server image, but still - when the image is imported into libvirt, it > &g...

On Thu, 2014-11-06 at 12:14 +0000, Ian Campbell wrote: > On Wed, 2014-10-29 at 17:36 -0400, Gedalya wrote: > > When booting domU's running amd64 jessie, I notice some memory problems > > with xl. > > I ran it (actually, upstream staging-4.4) under valgrind and it reported > after a reboot: > > ==5722== 24 bytes in 1 blocks are definitely lost in loss record 35

...et kernel and ramdisk to point to a file + * reference which will be updated and mapped, cmdline will be + * updated */ + libxl__file_reference *kernel, *ramdisk; + const char *cmdline; /* private to libxl__run_bootloader */ char *outputpath, *outputdir, *logfile; char *diskpath; /* not from gc, represents actually attached disk */ @@ -1803,7 +1823,6 @@ struct libxl__domain_create_state { * for the non-stubdom device model. */ }; - /* * Convenience macros. */ diff -r ac45608496cd -r cdb947baea10 tools/libxl/libxl_json.c --- a/tools/libxl/libxl_json.c Thu...