similar to: qemu-img-xen?

Hi,guys, During a HVM''s running which take a qcow format image file as its own virtual disk, the qcow image file will be always read.In the situation that its qcow format image is based on a raw format image, if nesethe backingfile ,just that raw format image file,would be read .my purpose is to cache the data that is read from the backingfile when the hvm is running . Now what I concern

[adding libguestfs] On 11/15/2017 09:52 AM, Gandalf Corvotempesta wrote: > I'm thinking if support for XVA files could be added to qemu-img > The file-format is well known (it's just a tar archive) and there are scripts > that are able to convert an XVA file to a RAW image. (ie: > https://gist.github.com/miebach/0433947bcf053de23159) > > Running these script on their

On Wed, Nov 15, 2017 at 04:52:56PM +0100, Gandalf Corvotempesta wrote: > I'm thinking if support for XVA files could be added to qemu-img > The file-format is well known (it's just a tar archive) and there are scripts > that are able to convert an XVA file to a RAW image. (ie: > https://gist.github.com/miebach/0433947bcf053de23159) > > Running these script on their own

Hi, i would like to use qcow2-sparse-images which point to a backup-file. After reading this: http://wiki.xensource.com/xenwiki/DmUserspace i figured out that this feature seems to be unsupported by the ubuntu 8.04 LTS kernel and xen-3.2.1. Is this a ubuntu-specific problem, or is it solved in Suse, Red Hat, XenSource, whatever? When i try to block-attach it, xm displays no error, but the

F12, libvirt 0.7.1-15, qemu 0.11.0-12, 32 bit I recently discovered that libvirt is stealing ownership of my disk images. How can I make it stop? I have a disk image in my home directory, owned by matt. When I create a domain that uses the disk it gets chowned to qemu.qemu. When the domain terminates it is owned by root.root. I've lost access to the file. It has been suggested that the

Hello xen-users, I am trying to access a guest disk that was created using qcow-create from dom0 using xl block-attach/block-detach, which appears to be the current "Xen way" of doing it. However, after the following command, no /dev/xvdb is appearing: $ xl block-attach 0 tap:qcow2:/home/root/images/test.img xvdb I am using Xen 4.1.2 (installed from source tarball) with an Ubuntu

Hello, This is a second post, with a trial which is different from the first one , in order to solve my blcok-attach problem. I tried the following two actions, according to the blktap readme: qcow-create 1000 qcowFile.img Creating file size 1048576000 Created cksum: 1813725440 then xm block-attach 0 tap:qcow:qcowFile.img /dev/xvda1 w 0 I see in the /var/log/xen/xend.log: [2007-03-13

I''m running latest 3.1.4. I need access to qemu-img to convert some image files. However this binary is not compiled after doing make world and make install. I notice that the source code is present, but I cannot figure out how to make it compile and install along with qemu-dm? Am I missing something? -- Randy _______________________________________________ Xen-users mailing

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

Hi All, Okay. Now I am confused. I have a bunch of virtual machines running under Virtual Box 3.2.12. I want to run them under KVM and drop Virtual Box from these systems. Supposedly "qemu-img convert" now supports direct conversion from vdi to whatever KVM uses. So I fired up the man page and got really confused. Then I fired up Google and got worse confused. Might I impose on

Is there a way to convert a Virtual PC vhd file to a raw img file for Xen without using XenServer ? I found a v2v utility from Starwind that converts to an .img format, but I don''t know if it is the same as the format that Xen uses. I ran the conversion and tried it under Xen, but could not get the console to come up, and had to destroy the domu to get that domain to shut down. I expect

Heres my setup. I have a workstation running windows xp sp3 that is currently acting as my symantec ghost and symantec endpoint server. For backup purposes I want to virtualize the physical machine so I can then just backup the xen image as opposed to making a copy of the hard drive image and having to transfer it to another machine in the case of a hardware failure. I connected an external

I was wondering if img''s are a lot slower then using lvm on dom0 partition? The domU will be handling web site and mail servers. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Xen Wiki for Stub Domain sample shows up syntax :- name = ''OVM_EL5U1_X86_HVM_4GB'' uuid = ''de0edfdc-c6f1-4d2b-a2a3-88c035208c79'' builder = ''hvm'' device_model = ''/usr/lib/xen/bin/stubdom-dm'' kernel = ''/usr/lib/xen/boot/hvmloader'' memory = ''256'' vif = [

I'm new to the lists so sorry about any faux pas I may have made. Also I apologize for the length, but I wanted to be sure I covered most of the details. I'm trying to do a PXE install on an Intel 1435VP2 server machine. The PXE install has worked on all the older machines in the cluster, so I know PXE is working. However, these new Intel server machines only support PXE booting from

hi im wondering if i can ''convert'' and existing physical windows partition to a xen image like this: - mount the existing ntfs fs - use dd to make a correct sized foo.img file - loop back mount foo.img - ntfs format (as bootable?) foo.img - ''cp -r '' the files from the mounted ntfs to the mounted and formated foo.img - use the

Hi, Trying to understand the current state of affairs with QCOW support in Xen with the blktap driver. It''s been made clear that a deviation from QEMU''s implementation of QCOW has occurred and that the QCOW files used in Xen must be created with the associated Xen tools only (e.g. qcow-create) and that images between QEMU and Xen are not interchangeable. My first question is

On Wed, Nov 15, 2017 at 11:52:46AM +0000, Richard W.M. Jones wrote: > [CC to qemu-devel since I'm obviously doing something wrong here, > I'm just not sure what.] > > I was getting ready to add multiple threads to ‘qemu-img convert’ (the > longest part of v2v conversions) when I noticed that it had them > already! (To be fair this was only added in February this year so

All, is it possible to create a new KVM machine from an existing qcow (v3) image with snapshots? snapshot-list doesn't show them, when using virt-manager 1:1.5.1-0ubuntu1.1 to create the machine. * t-ad5.img: QEMU QCOW Image (v3), 42949672960 bytes chris@cd:/data/md0$ qemu-img snapshot -l t-ad5.img Snapshot list: ID TAG VM SIZE DATE VM CLOCK 1

Old qemu-img versions return 1 instead of 0 for --help, failing the presence check: hence, which to `command` for checking the presence of qemu-img. Also, check that qemu-img actually has the --object option, since the test uses it. --- tests/test-tls.sh | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/tests/test-tls.sh b/tests/test-tls.sh index 73d44fa..7a6c949 100755