similar to: NOTICE: Data corruption bug when writing to qcow2 files

https://bugzilla.redhat.com/show_bug.cgi?id=836710 https://bugzilla.redhat.com/show_bug.cgi?id=836913 There are at least two related bugs going on: (1) Linux sync(2) system call doesn't send a write barrier to the disk, so in effect it doesn't force the hard disk to flush its cache. libguestfs used sync(2) to force changes to disk. We didn't expect that qemu was caching anything

Hi, When I register a callback for events with this function call: eh = guestfs_set_event_callback(g, message_callback, GUESTFS_EVENT_ALL, 0, dev); Shouldnt it capture and redirect messages like this to message_callback(): "libguestfs: error: lstat: /.Trash: No such file or directory" I still get them in stderr .. Thanks, Or

QCOW2 disk image gets corrupted when you try to install Service Pack 1 AFTER installing GPLPV drivers. This means, without the pv drivers, everything works fine. I tested both RAW and QCOW2 without GPLPV drivers and the installation has completed without any error, and the image (at least qcow2) has no errors too. How to reproduce: - Install Windows 7 32-bit guest - Check the image with

Il 30-01-2018 13:17 Gionatan Danti ha scritto: > Hi all, > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > - when creating a new volumes using vol-create-as, the resulting file > is a qcow2 version 2 (compat=0.10) file. Example: > > [root@gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > 8589934592 --format=qcow2 --backing-vol

Hi, I am having trouble configuring a virtual machine domain and its corresponding xml definition to use a qcow2 delta disk. The delta disk is backed by a qcow2 base disk. I am able to successfully start the guest OS with the delta disk at the command line using qemu. However, I am not able to start the guest OS using the libvirt tools including virsh and virt-manager. I am hoping that

1. What are you trying to do? I'm trying to mount qcow2 using guestfish -remote, modify the qcow2 and reuse the modified qcow2. 1. What exact command(s) did you run? I have attached code.txt 1. What was the precise error or output of these commands? While remounting the qcow2 I'm not able to see the modifications I have made to the qcow2 during initial mounting. May I know

On Tue, May 1, 2018 at 10:45 AM, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Tue, Jan 30, 2018 at 01:17:21PM +0100, Gionatan Danti wrote: > > Hi all, > > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > > > - when creating a new volumes using vol-create-as, the resulting file is > a > > qcow2 version 2 (compat=0.10) file.

I found guestfs_compress_out do the compression to gzip, bzip2, compress...etc. I want to compress qcow2, and I found details about qcow2 compression in https://people.gnome.org/~markmc/qcow-image-format.html The QCOW format supports compression by allowing each cluster to be > independently compressed with zlib. Can I do that with guestfs_compress_out?

On Wed, Nov 21, 2018 at 11:33:33AM +0800, Han Han wrote: > Hello, I face a problem on the nbdkit server: > > Version-Release number of selected component (if applicable): > nbdkit-v1.9.1 > qemu-utils-2.12+dfsg-3+b1 > > How reproducible: > 100% > > Steps: > 1. Create a qcow2 file > # qemu-img create disk 1G -f qcow2 This creates a 1GB virtual size qcow2 (real

On Tue, Jan 30, 2018 at 01:17:21PM +0100, Gionatan Danti wrote: > Hi all, > on a fully patched CentOS 7.4 x86-64, I see the following behavior: > > - when creating a new volumes using vol-create-as, the resulting file is a > qcow2 version 2 (compat=0.10) file. Example: > > [root at gdanti-lenovo vmimages]# virsh vol-create-as default zzz.qcow2 > 8589934592 --format=qcow2

On Sat, Nov 30, 2019 at 01:12:31 +0100, ort_libvirt@bergersen.no wrote: > Hi! > > I need to convert a KVM virtual machine from LVM to a qcow2 image, and wonder if this is the best way to do it (*1): > [$] qemu-img convert -O qcow2 /dev/vg_name/lv_name/ /var/lib/libvirt/images/image_name.qcow2 > > If this is the best way to do this, will this keep the information on:

When creating qcow2 images using virt-builder, is there a way to specify the qcow2 preallocation, as possible with qemu-img create -o preallocation=metada , for example? TIA, Y.

On 2015-10-14 11:34, Jérôme wrote: > In other words, can I have this on a 60Go drive? > total 53G > 7,4G -rw------- 1 root root 11G oct. 8 06:34 prod_151008.qcow2 > 7,4G -rw------- 1 root root 11G oct. 9 06:37 prod_151009.qcow2 > 7,5G -rw------- 1 root root 11G oct. 10 06:41 prod_151010.qcow2 > 7,5G -rw------- 2 root root 11G oct. 11 06:49 prod_151011.qcow2 > 7,5G

Le 12/04/2017 ? 15:31, Scott Gennari a ?crit : > How would can you import/migrate this .qcow2 into a logical volume? Any > advice would be greatly appreciated. - get size of qcow2 image: qemu-img info yourFile.qcow2 - create a logical volume of same size: ssm create -s xxxxxxxb -n yourLvName -p centos - copy image: qemu-img convert yourFile.qcow2 -O raw /dev/centos/yourLvName --

On Mon, Oct 15, 2018 at 10:28:25AM -0400, Raghuram Devarakonda wrote: > On Mon, Oct 15, 2018 at 3:54 AM Richard W.M. Jones <rjones@redhat.com> wrote: > > > > [Adding libguestfs mailing list] > > > > On Sun, Oct 14, 2018 at 11:53:17AM -0400, Raghuram Devarakonda wrote: > > > Hi, > > > > > > In our project, we deal with quite large sparse

Problem: Want to be able to produce a qcow2 file with multiple ext4 File Systems. Days later want to reproduce the production of the qcow2 and have the exact same byte-for-byte file, to prove my build is reproducible. Currently the ctime attributes of the inodes will differ and thus the qcow2 files will differ. Since the file times are subsecond the trick of setting the system time and chmoding

This question was asked on IRC: $ virt-builder centos-6 --output box.img --format qcow2 --size 40G # ... $ qemu-img convert -O qcow2 box.img box-qcow2.img $ ls -lAhs 1.6G -rw-r--r--. 1 james 41G Jan 2 21:53 box.img 1.1G -rw-r--r--. 1 james 1.1G Jan 3 18:54 box-qcow2.img $ file box* box.img: QEMU QCOW Image (v2), 42949672960 bytes box-qcow2.img: QEMU QCOW Image (v2),

On Mon, Aug 11, 2014 at 02:06:54PM -0500, Andrew Martin wrote: > Hello, > > I am running several virtualization servers with QEMU 1.4.x and > libvirt 1.0.2 on Ubuntu 12.04 and am working on optimizing the cache= > and aio= options for the virtual machines. These VM images are mostly > qcow2, and are served both from a local ext4 filesystem (with > data=ordered,barrier) and

On 11/21/18 4:39 AM, Richard W.M. Jones wrote: > On Wed, Nov 21, 2018 at 09:25:05AM +0000, Richard W.M. Jones wrote: >> nbdkit: file.2: error: invalid request: offset and count are out of range: offset=196608 count=512 > > Actually what happens even more precisely is that the underlying file > is not a multiple of 512 bytes (196624 ≡ 16 mod 512). > > qemu-img (the client)

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