Testing on Fedora 20 (JSON output slightly modified for legibility):
$ qemu-kvm --version
QEMU emulator version 2.0.0, Copyright (c) 2003-2008 Fabrice Bellard
$ touch f
$ qemu-kvm -qmp stdio -drive file=f
<= {"QMP": {"version": {"qemu": {"micro": 0, "minor": 0, "major": 2},
"package": ""}, "capabilities": []}}
{"execute":"qmp_capabilities"}
<= {"return": {}}
{"execute":"blockdev-snapshot-sync","arguments":{"device":"ide0-hd0","snapshot-file":"g"}}
Formatting 'g', fmt=qcow2 size=0 backing_file='f' backing_fmt='raw'
encryption=off cluster_size=65536 lazy_refcounts=off
<= {"return": {}}
{"execute":"block-commit","arguments":{"device":"ide0-hd0","top":"g"}}
{"timestamp": {"seconds": 1401921011, "microseconds": 498888}, "event":
"BLOCK_JOB_COMPLETED", "data": {"device": "ide0-hd0", "len": 0,
"offset": 0, "speed": 0, "type": "commit"}}
<= {"return": {}}
{"execute":"query-block-jobs"}
<= {"return": []}
Huh? I thought that an active commit was not supposed to complete
automatically, but that the job would remain around until I either
'block-job-cancel' or 'block-job-complete' it. That is, I should have
gotten a BLOCK_JOB_READY event and still see the job when I query for
it. Where am I going wrong, or did I uncover a bug in active commit?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
