Description of problem:
this was separated from bug 906246, I charted with kwolf for this problem in IRC, and he throught this maybe the RHEVM bug. Please correct me if any mistake.
If i do live mirroring just to one disk at one time in RHEVM, it can complete successfully, and i can monitor the mirroring related commands. for the "block-job-complete" commands, and i check the HMP and QMP monitor commands that did not find it in rhel6.4. I am very curious that qemu cann't provide it but rhevm tools need this command, how they works well ?
Version-Release number of selected component (if applicable):
host info:
2.6.32-355.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.352.el6.x86_64
vdsm-4.10.2-4.0.el6ev.x86_64
rhevm-3.2.0-5.el6ev.noarch
libvirt-0.10.2-16.el6.x86_64
guest info:
rhel6.4-32bit: kernel-2.6.32-355.el6.i686
windows:windows-2k8R2
How reproducible:
100%
Steps to Reproduce:
1.prepare a qcow2 format rhel6.4-32bit guest with one disk in RHEVM.
2.do live mirroring to the data disk simultaneously moving it from one storage domain to another in RHEVM.
Actual results:
after step 2, it can complete successfully, and i can monitor the mirroring related commands, like:
{"execute":"__com.redhat_drive-mirror","arguments":{"device":"drive-virtio-disk0","target":"/rhev/data-center/xxxxx","speed":0,"full":false,"mode":"existing","format":"qcow2"},"id":"libvirt-4338"}
{"execute":"block-job-complete","arguments":{"device":"drive-virtio-disk0"},"id":"libvirt-4484"}
{"execute":"__com.redhat_drive-reopen","arguments":{"device":"drive-virtio-disk0","new-image-file":"/rhev/data-center/xxxx","format":"qcow2"},"id":"libvirt-4485"}
Additional info:
Comment 3Federico Simoncelli
2013-02-18 22:39:37 UTC
(In reply to comment #1)
> Fede, can you take a look and add some info here?
According to bug 906246 comment 9 this bug could be closed as the requests for the live snapshot and disk replica (__com.redhat_drive-mirror / block-job-complete) never reached the HSM (connection refused).
Comment 4Federico Simoncelli
2013-02-19 10:06:48 UTC
This bug is based on the idea that RHEV would be using the regular rhel6 qemu-kvm package (that doesn't include __com.redhat_drive-mirror/__com.redhat_drive-reopen).
RHEV instead depends (and uses) qemu-kvm-rhev which includes all the required commands for live snapshots and live storage migration:
{"name": "transaction"}, {"name": "blockdev-snapshot-sync"}, {"name": "__com.redhat_drive-mirror"}, {"name": "__com.redhat_drive-reopen"}
Closing as NOTABUG.