similar to: Why is virt-resize designed to involve two disks?

HI, As you've known, vhd-util and qemu-img both provide the capacity for resizing the original disk, but why is virt-resize designed to involve two disks, not only original disk? Is there any concern? Is it possible that only one original disk is involved in virt-resize? -- Regards, Zhi Yong Wu

On Tue, Sep 23, 2014 at 06:19:21PM +0800, Zhi Yong Wu wrote: > As you've known, vhd-util and qemu-img both provide the capacity for > resizing the original disk, .. although they only resize the container, not the contents which is what virt-resize does. So these tools are not really comparable. > but why is virt-resize designed to involve > two disks, not only original disk? Is

On Mon, Sep 29, 2014 at 1:14 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Sep 29, 2014 at 12:55:04AM +0800, Zhi Yong Wu wrote: >> On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones <rjones@redhat.com> wrote: >> > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: >> >> Yeah, but why did it happen when i directly issue guest VM

I have try to resize one vhd file with vhd-util, i did some test... For example i have try: vhd-util resize -n /mnt/vm/disks/ring-12.disk1.vhd -s 6000 but output always: options: <-n name> <-j journal> <-s size (in MB)> [-h help] I not understand what i wrong, someone can help me please? -- View this message in context:

On Mon, Sep 29, 2014 at 1:27 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Mon, Sep 29, 2014 at 01:22:19AM +0800, Zhi Yong Wu wrote: >> Yes, I am trying to run it in Xen Domain0. I thought that we can use >> Domain0 as a public libguestfs VM, This will avoid starting a new >> guest for virt-xxx every time, But Domain0 has no corresponding qemu >> task. So

On Sun, Sep 28, 2014 at 11:31 PM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Sep 28, 2014 at 11:04:11PM +0800, Zhi Yong Wu wrote: >> On Sun, Sep 28, 2014 at 6:48 PM, Richard W.M. Jones <rjones@redhat.com> wrote: >> > On Sun, Sep 28, 2014 at 06:33:53PM +0800, Zhi Yong Wu wrote: >> >> On Sun, Sep 28, 2014 at 6:26 PM, Richard W.M. Jones

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

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

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:

Add ''-C'' (nocow) option to vhd-util create. Btrfs has terrible performance when hosting VM images, even more when the guest in those VM are also using btrfs as file system. One way to mitigate this bad performance is to turn off COW attributes on VM files (since having copy on write for this kind of data is not useful). According to ''chattr'' manpage, NOCOW

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

Hi all, I`m evaluating methods for nightly "snapshot" a physical win2003 to xcp vm. I know it would be a lot easier and reliable just to to one convert one time and start to generate real vm snapshots, but at this time I cannot use this method. I tested the sequence: disk2vdh -> xenconvert (to xcp), but a big deal of using this method is that xenconvert does not send

On Mon, Sep 29, 2014 at 12:36 AM, Richard W.M. Jones <rjones@redhat.com> wrote: > On Sun, Sep 28, 2014 at 11:43:17PM +0800, Zhi Yong Wu wrote: >> Yeah, but why did it happen when i directly issue guest VM via above command? > > OK I see. When libguestfs runs qemu-kvm, it sets up a TCP socket > first [on RHEL 5 -- it works differently upstream]. Without the > socket

Hello List, I''m using blktap on XCP 1.1 and developing a difference copy program for easy backup and remote archival. The idea is to read the BAT of VHD1 and sync it to BAT of VHD2 with BITMAP and the data blocks. Other way would be by adding a sha1 signature in each data block and comparing it with remote VHD. I tried to get some info from below programs but could not get required

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

I''ve just pushed vdiskadm translate to the 3.3 vdisk repo. You can now translate data from one virtual disk data type to another without creating a virtual disk. This allows the user to use a vmdk file and directly translate the data into a zvol without having to import it first to a vdisk and then export it to the zvol. # vdiskadm help translate translate - translate virtual disk data

I''ve just pushed vdiskadm import/export/convert to the 3.3 vdisk and vbox repos. You can now import a disk image from a block device or file to a vdisk, convert (in place) to a different type of vdisk and export from a vdisk to a block device or file. I''ve also pushed the full vhd support (sparse and fixed) and the ability to import a vmdk 1.1 optimized stream file. An

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

Hi, This is the first time I use syslinux mailing list, so I am sorry if I have made any mistake. Well, I follow this post : http://www.linuxbyexamples.net/2012/08/boot-winxp-from-http-server.html and I can successfully boot into winxp using gpxelinux.0 loading vhd image through http. This works well. But when the vhd image getting bigger than 512MB (I added some more files into the image),

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