Displaying 2 results from an estimated 2 matches for "aaacbbbbccccxxxx".
2014 Jul 02
7
virsh blockcopy: doesn't seem to flatten the chain by default
Versions
--------
(Libvirt locally built from a recent git commit -ec7b922):
$ rpm -q libvirt-daemon-kvm qemu-system-x86
libvirt-daemon-kvm-1.2.6-1.fc20.x86_64
qemu-system-x86-2.0.0-1.fc21.x86_64
Test
----
[All images are qcow2 files.]
We have this simple chain:
base <- snap1
Let's quickly examine the contents of 'base' and 'snap1' images:
2014 Jul 03
0
Re: virsh blockcopy: doesn't seem to flatten the chain by default
...ng a file can be done by writing one sector, and
may still leave remnants of the file behind in other sectors, but in
such a way that the guest file system will never retrieve those
contents). Represent these changes with "C"
base: AAABBBBBXXXXXXXX
snap1: XXXCXXXXCCCCXXXX
====
guest: AAACBBBBCCCCXXXX
When you are doing a full blockcopy, you are asking to create a new file
whose contents match what the guest sees. When the copy finally reaches
sync, you have:
base: AAABBBBBXXXXXXXX
snap1: XXXCXXXXCCCCXXXX
copy: AAACBBBBCCCCXXXX
====
guest: AAACBBBBCCCCXXXX
The copy operation lasts as lo...