similar to: Need help using libvirt with qcow2 delta and base images

Hello Richard and all, (continuing from https://www.redhat.com/archives/libguestfs/2014-September/msg00112.html ). I'm experimenting with libguestfs on non-linux VMs, encountered errors on FreeBSD9.3 and MINIX3 (and few others, but these ones are easy to share), with host Ubuntu 14.04.01 LTS x86-64. Attached are logs from "virt-inspector -v -x" for each VM. The images are here:

Hi, After upgrading to libvirt 0.8.1, I can no longer create empty volumes with no backing store and an explicit format of qcow2. This XML volume definition: <volume> <name>testserverb-data2.img</name> <allocation>0</allocation> <capacity units='G'>20</capacity> <target> <format type='qcow2'/>

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

On 02/12/2015 07:41 PM, Edward Young wrote: > Hi all, > > > When I live migrate a vm using > > "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system > tcp://192.168.1.3" > > > I got the following error > > > WARNING: Image format was not specified for > 'nbd://node2:49155/drive-virtio-disk0' and

Hi, In most cases we use image files as virtual disks under the full-virtualization situation.On the version 4.1.2 of xen,I do the following command: ############################################################ dd if=/dev/zero of=myraw.img bs=1M seek=8K count=1 #Before the command below I install the operating system in myraw.img qemu-img-xen create -b myraw.img -f qcow2 myqcow1.img 20000M

On Wed, Sep 11, 2013 at 10:33:06AM +0800, bigclouds wrote: > hi,all > images of qcow2 format with backing files, its backing files have > two path infos (absolute path and relative path), This is not true. The file format only contains the relative path. qemu-img info will print an absolute path, but it's not stored inside the file. > how to let > libguestfs use absolute path

After snapshot-delete, the qcow2 image file size doesn't decrease, isn't that a waste of disk space? Would someone please tell me how to decrease the file size when snapshot-delete, if that's possible? The image file name of my virtual machine is d0.qcow As follows: [root at test1 ]# virsh list Id Name State

Hello, I converted a W2003-Server to a vmdk-image, I didn't think too much back then ... Now I have 2 windows-drives C: and E: inside one vmdk-image-file, which was converted to qcow2. I have installed drivers and stuff into that VM already and would like to avoid to start over again with the vmdk-file -> Is there a way to split that one qcow2 into 2 separate files, one for each

thanks . now i know qcow2 only store relative path. look at my error message, 6a3256bb-b247-4fb5-9f75-8ffa7151eeda i a symlink to a LV. it is the backing_file of several images(LV).. i have no idea of the reason of the error. # virt-win-reg 6a3256bb-b247-4fb5-9f75-8ffa7151eeda 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' 'Productname' hivex:

Hi all, We have done several speed tests on a qcow2 Linux Image to test how fast tar-in with a big tarball can be. Virtio seems to be active, and we get transfers in a range from 100-160MB/sec, independent of the disk speed on the host. For example we had a 20 core host system with 900MB for serial writing and 350MB for mixed read/write on the native filesystem. We've expected a faster

Hi, all My xml 'dom1.xml' is as following: <domain type='kvm' id='1'> <name>kvm-xp</name> <description>xp kvm</description> <memory>524288</memory> <currentMemory>524288</currentMemory> <os> <type>hvm</type> <!--loader>/usr/lib/xen/boot/hvmloader</loader--> <boot dev="hd"/>

Hello All, I am using Centos 6.3 with libvirt 0.910 and qemu-kvm 0.12 I had to resize a qcow2 disk, and came across several issues; I used this command to resize the image: sudo -i /usr/bin/qemu-img /var/lib/libvirt/images/mydisk.img resize +100G . The disk is attached using virtio. I then tried to use parted from within the guest to resize the partition. The first problem was that the

Hi There, I''ve been trying to get this to work for the last couple of days, but found no information on the internet that would help. Essentially, a tap-ctl opencommand with a qcow2 image does not work (error code 2) and produces the following line in syslog: tap-ctl: tap-err:tap_ctl_open: open failed, err -2 I have attached a shell script that reproduces the problem on my machine. The

On Thu, Feb 12, 2015 at 08:41:31PM -0600, Edward Young wrote: > Hi all, > > > When I live migrate a vm using > > "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system > tcp://192.168.1.3" > > > I got the following error > > > WARNING: Image format was not specified for >

For the appliance of the QCOW2 format, get the UUID of the disk by reading the first 256k bytes with 'qemu-img dd' command. Then pass the read block to the 'file' command. In case of failure, run the 'file' command again directly. Suggested-by: Denis V. Lunev <den@openvz.org> Signed-off-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com> ---

On 02/13/2015 03:15 AM, Kashyap Chamarthy wrote: > On Thu, Feb 12, 2015 at 08:41:31PM -0600, Edward Young wrote: >> Hi all, >> >> >> When I live migrate a vm using >> >> "migrate --live --copy-storage-all mig-vm qemu+ssh://192.168.1.3/system >> tcp://192.168.1.3" >> >> >> I got the following error >> >> >>

On Thu, Aug 13, 2020 at 07:48:52AM +0300, Andrey Shinkevich wrote: > For the appliance of the QCOW2 format, the function get_root_uuid() > fails to get the UUID of the disk image. > In this case, let us read the first 256k bytes of the disk image with > the 'qemu-img dd' command. Then pass the read block to the 'file' > command. > > Suggested-by: Denis V.

On Wed, Aug 12, 2020 at 03:52:34PM +0300, Vladimir Sementsov-Ogievskiy wrote: > 12.08.2020 15:39, Andrey Shinkevich wrote: > >For the appliance of the QCOW2 format, get the UUID of the disk by > >reading the first 256k bytes with 'qemu-img dd' command. Then pass the > >read block to the 'file' command. In case of failure, run the 'file' > >command

On Wed, Aug 12, 2020 at 04:12:28PM +0300, Vladimir Sementsov-Ogievskiy wrote: > 12.08.2020 15:52, Vladimir Sementsov-Ogievskiy wrote: > >12.08.2020 15:39, Andrey Shinkevich wrote: > >>For the appliance of the QCOW2 format, get the UUID of the disk by > >>reading the first 256k bytes with 'qemu-img dd' command. Then pass the > >>read block to the

Hi All, I am presently doing a small POC with rsync for incremental backup and restore starategies. I have come up with certain question down the line, can anyone help me with the explanation. Used the config and ideas from: http://www.mikerubel.org/computers/rsync_snapshots/ The commands executed on two machines in sequence Machine 1: root at Andruil:~# vim testfile root at Andruil:~# ls