Jeff Cody 5279efebcf block: mirror - fix full sync mode when target does not support zero init
During mirror, if the target device does not support zero init, a
mirror may result in a corrupted image for sync="full" mode.

This is due to how the initial dirty bitmap is set up prior to copying
data - we did not mark sectors as dirty that are unallocated.  This
means those unallocated sectors are skipped over on the target, and for
a device without zero init, invalid data may reside in those holes.

If both of the following conditions are true, then we will explicitly
mark all sectors as dirty:

    1.) sync = "full"
    2.) bdrv_has_zero_init(target) == false

If the target does support zero init, but a target image is passed in
with data already present (i.e. an "existing" image), it is assumed the
data present in the existing image is valid data for those sectors.

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-id: 91ed4bc5bda7e2b09eb508b07c83f4071fe0b3c9.1443705220.git.jcody@redhat.com
Signed-off-by: Jeff Cody <jcody@redhat.com>
2015-10-01 15:02:21 -04:00
2015-07-08 13:11:01 +02:00
2015-09-11 10:45:43 +03:00
2015-09-11 10:45:43 +03:00
2015-09-11 10:21:38 +03:00
2015-09-11 10:45:43 +03:00
2015-09-19 11:53:15 +02:00
2015-09-25 23:14:00 +01:00
2015-09-30 09:42:04 +02:00
2015-07-27 22:44:47 +03:00
2015-04-30 16:05:48 +03:00
2015-09-04 13:26:26 +02:00
2015-09-07 18:14:03 +02:00
2015-09-07 18:14:03 +02:00
2015-09-01 13:16:26 -05:00
2015-05-11 08:59:07 -04:00
2015-09-29 11:33:02 +05:30
2015-09-16 17:33:33 +02:00
2015-08-19 16:29:53 +01:00
2015-08-11 23:15:55 +01:00

Read the documentation in qemu-doc.html or on http://wiki.qemu-project.org

- QEMU team
Description
Languages
C 82.6%
C++ 7%
Python 3.3%
Dylan 2.8%
Shell 1.5%
Other 2.5%