search for: base_disk

...acking_file=guest_disk.qcow2 -O qcow2 -s snapshot_n guest_disk.qcow2 new_disk_for_libguestfs.qcow2 Could it be that, as the backing file is pointing to the guest's disk which will evolve in time, when guestfs tries to read the data sees incosistencies? The guest_disk.qcow2 is a COW clone of a base_disk.qcow2, what if I rebase the new_disk_for_libguestfs.qcow2 to the base_disk.qcow2?

...the guest's disk which > will evolve in time, when guestfs tries to read the data sees > incosistencies? qemu-img convert makes a full copy, so it's not guestfs that's the problem, but qemu-img. The copy is not done instantaneously. > The guest_disk.qcow2 is a COW clone of a base_disk.qcow2, what if I rebase > the new_disk_for_libguestfs.qcow2 to the base_disk.qcow2? Many copies and snapshots. I'm thoroughly confused ... Anyhow, unless you either make a full copy while the guest is paused, *or* you use a point-in-time snapshot feature of either qemu (drive-backup) or y...

...gt; will evolve in time, when guestfs tries to read the data sees > > incosistencies? > > qemu-img convert makes a full copy, so it's not guestfs that's the > problem, but qemu-img. The copy is not done instantaneously. > > > The guest_disk.qcow2 is a COW clone of a base_disk.qcow2, what if I > rebase > > the new_disk_for_libguestfs.qcow2 to the base_disk.qcow2? > > Many copies and snapshots. I'm thoroughly confused ... > > Anyhow, unless you either make a full copy while the guest is paused, > *or* you use a point-in-time snapshot feature o...

2015-05-28 10:10 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > On Thu, May 28, 2015 at 09:48:41AM +0300, NoxDaFox wrote: > > 2015-05-27 15:21 GMT+03:00 Richard W.M. Jones <rjones@redhat.com>: > > > > > On Wed, May 27, 2015 at 09:38:38AM +0300, NoxDaFox wrote: > > > > * RuntimeError: file receive cancelled by daemon - On r = > > >