similar to: [PATCH] vhd-util create: add -C|nocow option

blktap2: fix makefile of vhd for parallel make With parallel make, libvhd might not be created before link resulting in link error. This patch guarantees it. Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp> diff --git a/tools/blktap2/vhd/Makefile b/tools/blktap2/vhd/Makefile --- a/tools/blktap2/vhd/Makefile +++ b/tools/blktap2/vhd/Makefile @@ -12,6 +12,9 @@ CFLAGS +=

Changes: tools/blktap: remove unneeded pointer dereferencing in convert_dev_name_to_num tools/blktap: constify string arrays in convert_dev_name_to_num tools/blktap: fix params and physical-device parsing tools/blktap: remove unneeded pointer dereferencing from img2qcow.c tools/blktap: remove unneeded pointer dereferencing from qcow2raw.c tools/blktap2: fix build errors caused by Werror in

This patch series introduces the VHD library. It is based on the blktap2 one, with changes coming from the blktap2.5 one. Signed-off-by: Thanos Makatos <thanos.makatos@citrix.com>

Guys, I'm trying to compile the Xen 4.0.0 via debian/rules makefile but I got this: administrativo at sid01:~/xen/xen-4/xen-4.0.0$ make -f debian/rules build-tools ..... make -C lib all make[7]: Entering directory `/home/administrativo/xen/xen-4/xen-4.0.0/debian/build/build-tools/tools/blktap2/vhd/lib' make[7]: Nothing to be done for `all'. make[7]: Leaving directory

Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.

Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.

Hi there, I''m running several VMs within Xen, and now I''m trying to create/revert snapshots of my VMs. Along with Xen and blktap2, another utility, vhd-util is also delivered, and according to its description, i guess I can use it to create/revert VM snapshots. To create a snapshot is actually easy, I just call |vhd-util snapshot -n aSnapShot.vhd -p theVMtoBackup.vhd | But

For those wanting to know how to mount filesystems through blktap2 here is how you do it, as I couldn''t find it fully documented. The instructions on the blktap2 readme file are rather out of date. You can mount them under Dom0 like so. e.g. to mount a vhd file, sudo xm block-attach 0 tap2:vhd:/home/xen/xenwin7-persist.vhd xvdb w 0 Now the device should appear under /dev ls

Hi, I''m currently trying xen 4.1.1 with the 3.0.0-rc5 (heard that it now contains the xen code to run as front or back xen domain). Everything seems to run fine, except that I am trying since a few hours to mount a .vhd file in the dom0. What I tried so far: to create a blank vhd file (this is working): host# vhd-util create -n /storage/test.vhd -s 20G Then i try to mount the file

Hi list, Saw that there''s a patch for xenserver 5.6fp1 which should fix this: http://support.citrix.com/article/CTX129267 Anybody know if/when this will happen on XCP? I have the same problem - disk usage remains the same after snapshot deletion - this is in the log on the pool master: vhd-util: libvhd::vhd_validate_footer: invalid footer cookie: ÇÇÇÇÇÇÇÇ This guy has the same

Forwarding to you original patch requested. It works for me. Boris --- On Sun, 7/11/10, eXeC001er <execooler@gmail.com> wrote: From: eXeC001er <execooler@gmail.com> Subject: [Xen-devel] [PATCH] blktap2: blktap2 and pygrub (xen-unstable) To: "Xen-devel" <xen-devel@lists.xensource.com> Date: Sunday, July 11, 2010, 9:18 AM 1. Bug fix for error: "Error: Device

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

I''m getting this message (subject line) in daemon.log every time I start or restart xend. I''m not sure if this is related to the fact that I cannot boot up my Windows domU from a VHD file. The Windows domU was working fine with Xen 4.0.0 (with 2.6.32.14 dom0 kernel). When I upgraded to Xen 4.0.1-rc4 (with 2.6.32.16 dom0 kernel), I can no long boot the Windows domU from VHD. The

Package: blktap Version: 2.0.90-4 Severity: important User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-6 gcc-6-unused-const-variable This package fails to build with GCC 6. GCC 6 has not been released yet, but it's expected that GCC 6 will become the default compiler for stretch. Note that only the first error is reported; there might be more. You can find a snapshot of GCC 6 in

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: normal Due to license issues this version of Xen does not include the blktap2 backend (tapdisk2) and associated utilities (vhd-util, etc.). The decision was made to disable the blktap v1 kernel module (the default is now blktap2). As a result we can't use any tap devices which means worse performance than previousl. Since blktap1 was available

I was wondering if someone can shed some light on why vhd files created with qemu-img don''t really work right with vhd-util and consequentially blktap in general. To validate the incompatiblity its simple enough to do qemu-img create -f vpc test.vhd 40g vhd-util snapshot -n child.vhd -p test.vhd Which will show the below and then the headers don''t display the BATMAP summary:

----- Forwarded Message ----- From: "Stefan Hajnoczi" <stefanha@redhat.com> To: "Eric Sandeen" <sandeen@redhat.com> Cc: virt-devel@redhat.com, "Kevin Wolf" <kwolf@redhat.com> Sent: Friday, November 22, 2013 9:20:51 AM Subject: [virt-devel] btrfs NOCOW for VM disk images Hi, In upstream QEMU we''re discussing patches that set the NOCOW flag

(new) blktap-dev_2.0.90-1_amd64.deb extra devel Xen API blktap shared library (development files) The Xen Cloud Platform (XCP) is an open source enterprise-ready server virtualization and cloud computing platform, delivering the Xen Hypervisor with support for a range of guest operating systems. This package is part of it. It implements the userland part of the blktap driver. . Virtual Hard

Hello, some time ago we discussed on #btrfs that the nocow attribute for files wasn''t working (around 3.3 or 3.4 kernels). That was evident by files fragmenting even with the attribute set. Chris mentioned to find a fix quickly for that, and posted some lines of change into irc. But recently someone mentioned that 3.6-rc looks like still not respecting nocow for files. Is there really

Folks, The tag 4.0.1-rc3 has been added to http://xenbits.xensource.com/xen-4.0-testing.hg Please test! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel