similar to: QCOW in RAMDISK on Xen

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 ~]#

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

tags 490409 + patch thanks Hi, The following is the diff for my xen-3 3.2.1-2.1 NMU. It incorporates three patches from upstream and aims to fix CVE-2008-2004 aka #490409. It is not yet tested much, I would appreciate if interested parties could give it a try. I'll upload in due course. Kind regards T. diff -u xen-3-3.2.1/debian/control.md5sum xen-3-3.2.1/debian/control.md5sum ---

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

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

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 just ordered quite a few servers, and, without verifying ahead of time, ordered without hard drives planning to boot over iSCSI using the built-in network cards (NOT an iSCSI HBA). I''m wondering if anyone has tried (and hopefully succeeded) installing XCP to an iSCSI volume using a network card with iSCSI boot support and the software iSCSI initiator in XCP. Obviously I can order HDs

On Sun, Mar 25, 2018 at 11:05 PM Nir Soffer <nirsof@gmail.com> wrote: > On Sun, Mar 25, 2018 at 2:41 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > >> On Sat, Mar 24, 2018 at 10:36:06PM +0000, Nir Soffer wrote: >> > On Thu, Mar 22, 2018 at 5:25 PM Richard W.M. Jones <rjones@redhat.com> >> > wrote: >> > >> > > PROBLEMS:

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''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

Hi All I am using xen 3.3.0 version and I want to start network virtual interface on Dom U by using the following command # xend start *************************************************************** *************************************************************** ** WARNING: Currently emulating unsupported memory accesses ** ** in /lib/tls glibc libraries. The emulation is

Thanks for letting me know I'm not making myself clear, let me try again with a few more specifics, These are Windows VMs with three disk images for C:, D: and L:. To simplify I'll focus on the image for C: which had grown to 77G physical size on the hypervisor's ssd (I just double-checked that with 'ls -al' because qemu-img below says 70G, this image had two snapshots at one

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

Package: xen-utils-3.4 Version: 3.4.3~rc6-1 Severity: important blktapctrl doesn't start. This means that none of the tap: disks work (eg tap:aio). It produces this in the log BLKTAPCTRL[6569]: blktapctrl.c:788: blktapctrl: v1.0.0 BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (aio)] BLKTAPCTRL[6569]: blktapctrl.c:790: Found driver: [raw image (sync)]

You're right, there's a procedure following it, once the space is zeroed qemu-img will recognize it as such and will eliminate it when 'convert' is used. Apparently Fedora qemu has some better capabilities to shrink partitions but they haven't made it to "long term support" distributions yet. For now, what has to be done to shrink qcow[2] partitions (raw works) is

Hello libvirt experts, I use libvirt (0.7.5-5ubuntu27.7) with KVM / qemu (0.12.3+noroms-0ubuntu9.2). Some machines use raw images but same use Virtualbox images (.vdi). Since last Ubuntu 10.04 LTS update I can not start the vdi-images. The "driver name= type=" option was new. <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file'

On 04/19/2017 10:00 AM, Marco Aurelio L. Gomes wrote: > Hi, > > I'm using virsh to instance a VM in my environment, but I'm running on > some issues. > I got the following error: > > error: Failed to create domain from domain.xml > error: internal error: qemu unexpectedly closed the monitor: > 2017-04-17T17:00:37.012369Z qemu-kvm: -drive >