PID: 0.144
device: 0.128
other: 0.123
files: 0.119
semantic: 0.097
vnc: 0.074
socket: 0.060
permissions: 0.057
performance: 0.043
network: 0.038
graphic: 0.035
boot: 0.034
debug: 0.028
KVM: 0.021
debug: 0.415
vnc: 0.268
files: 0.108
device: 0.051
PID: 0.031
other: 0.030
network: 0.019
socket: 0.016
boot: 0.014
semantic: 0.013
performance: 0.013
graphic: 0.008
KVM: 0.008
permissions: 0.007

drive_mirror on a resized image creates file with wrong size

Repro steps:

qemu-img create -f qcow2 base 32M
qemu-img create -f qcow2 -o backing_file=base disk
qemu-img resize /home/vishvananda/disk 64M
qemu-system-x86_64 -drive file=disk,id=vda -vnc :1 -monitor stdio
QEMU 1.3.0 monitor - type 'help' for more information
(qemu) drive_mirror vda test
Formatting 'test', fmt=qcow2 size=33554432 backing_file='base' backing_fmt='qcow2' encryption=off cluster_size=65536 lazy_refcounts=off

the file is 32M instead of 64M:

qemu-img info test
image: test
file format: qcow2
virtual size: 32M (33554432 bytes)
disk size: 196K
cluster_size: 65536
backing file: base
backing file format: qcow2

Workaround is to precreate the new file of the proper size and pass -n

qemu-img create -f qcow2 base 32M
qemu-img create -f qcow2 -o backing_file=base disk
qemu-img resize /home/vishvananda/disk 64M
qemu-img create -f qcow2 -o backing_file=base test 64M
qemu-system-x86_64 -drive file=disk,id=vda -vnc :1 -monitor stdio
QEMU 1.3.0 monitor - type 'help' for more information
(qemu) drive_mirror vda test -n



reformatted patch and submitted upstream:

http://lists.gnu.org/archive/html/qemu-devel/2013-01/msg04584.html

Patch has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=8689907266b649b757c220
... so I think it should be OK to close this bug ticket now.