similar to: xm block-attach and qcow image - why does it fail ? second try

For many months now we have been trying to create a file-backed qcow image with the qcow-create code. Each time we try to back a file with a qcow, it screams: *** buffer overflow detected ***: qcow-create terminated Below is the output from two different attempts and information about qcow-create. Any ideas/thoughts/help you can offer? Thank you for your help! -Eric [root@trogdor ~]#

Hello, I read the blktap readme; there is a section there titled: Mounting images in Dom0 using the blktap driver. It says there that you can mount an image by: xm block-attach 0 tap:aio:<FILENAME> /dev/xvda1 w 0 mount /dev/xvda1 /mnt/disk <--- don''t use loop driver This option also appears in: http://wiki.rpath.com/wiki/Xen_DomU_Guide I assume that this option is not

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

Package: xen-utils-common Version: 4.1.3-6 Severity: minor Dear Maintainer, I am trying to run the following command on a dom0 Debian server in order to mount a vmware vmdk. I don't want to use kpartx or losetup as they have poor write performance and I'm hoping blktap will provide better performance. xm block-attach 0 tap:vmdk:/mnt/backup/3MSYDDP01/3MSYDDP01_2-flat.vmdk /dev/xvda1 w 0

I have a qcow file It shows correct size on one server Fdisk -l w.qcow 70 GB On the other server Fdisk w.qcow 0 MB stupid

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

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

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

On Tue, Aug 13, 2019 at 15:15:11 +0200, Petr Stodulka wrote: > Hi guys, > I had to move to the new laptop week ago and I screw migration of my virtual > machines. I recovered my virtual machines on the new laptop (virsh define) > using the backed up xml files, but I am missing any file with metadata about > snapshots. The original storage is cleaned so I cannot take these files >

Dear,Beg for your help. I am really puzzled with this problem.HVM domain can not boot up with Qcow incremental image(using command: qcow-create size incremental_file original_Qcow_img_file), but it can boot up with the original Qcow disk image file. When using Qcow incremental image, the guest qemu window would disappear before loading grub, and `xm list` can not find this guest domain.The VM

Hello, I installed Xen 3.2.1 on Debian Lenny from packages. Then created image files with 'xen-create-image --size=2Gb --swap=128Mb --dhcp --dir=/xen --hostname=test'. Now I'm trying to run Debian in PV mode using the following configuration file: kernel = "/boot/vmlinuz-2.6.26-1-xen-686" ramdisk = "/boot/initrd.img-2.6.26-1-xen-686" memory = 128 name =

Hi, I want to ask if anyone of you is familiar with QCOW and has used this with xen? I''ve googled a bit about and could''nt really find out if it''s a good choice or not. Has anyone experience with usage in xen and can say something about performance and snapshot usability? Thanks in advance, Alex _______________________________________________ Xen-users mailing

I have been messing with QCOW on Xen and I''ve come to the conclusion that nobody actually uses it otherwise it would work. Has anyone gotten QCOW2 and Xen to work reliably? I have 40 PV VMs that are identical (initially) and would like to move from separate disk images to one base image sitting in a ramdisk and the COW images hosted on an iSCSI storage device. The VMs would boot off the

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

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

I am using a sparse image with a backed file. Using a dd inside domU the performance doesn''t exceed 3.0MB/s. If I try this on an NFS mount the performance (in an uninitialized qcow image) is below 1.0MB/s. Is this as expected? Are there currently any improvements in the Xen 3.3 hg repo that increase speed in the blktap backend? Stefan _______________________________________________

I''ve a problem with the syntax of qcow images on HVM guest. In my configuration file i''ve this string disk = [''tap:aio:/mnt/qcowwin,hda1,w''] Is it correct??? Windows installation cannot find the harddisk to proceed os installation... _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi, I am able to get Xend running on Fedora 8 but when I try to create any VM it fails. The xm create osc.cfg throws following error - [root@asds174 vm_images]# xm create osc.cfg Modified arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'',

Hi guys, I had to move to the new laptop week ago and I screw migration of my virtual machines. I recovered my virtual machines on the new laptop (virsh define) using the backed up xml files, but I am missing any file with metadata about snapshots. The original storage is cleaned so I cannot take these files anymore. Using qemu-info I can see my snapshots inside the qcow images, but libvirt

I''ve been using lvm under centos to create the backing store for domUs and although the performance seems acceptable it has some shortcomings. The biggest of which is the LVM bug which prevents me from removing an lv (it says it is still mounted and it definitely isnt). I thought this was just a centos bug but it appears to be evident in debian and ubuntu too and I really can''t