Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
QE tested qemu-kvm-rhev-1.5.3-60.el7ev, it hit the same issue as 1114793 bug. so file a new bug to track this issue. I am trying to reproduce it with qmp command directly. will update result to bz asap.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
3.10.0-123.4.2.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.qemu-img create -f raw base.img 10M
2.qemu-img create -f qcow2 -b base.img -o backing_fmt=raw snap1.img
3.qemu-img create -f qcow2 -b snap1.img -o backing_fmt=qcow2 snap2.img
# set up blank space to hold the copy
touch copy.img
# cp base.img copy.img
4.xml file
<domain type='kvm'>
<name>testvm4</name>
<memory unit='MiB'>256</memory>
<vcpu>1</vcpu>
<os>
<type arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type>
<boot dev='hd'/>
</os>
<devices>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2' cache='none'/>
<source file='/var/lib/libvirt/images/snap2.img'/>
<target dev='hda' bus='virtio'/>
</disk>
<graphics type='vnc'/>
</devices>
</domain>
5.# check for events
virsh event testvm1 block-job --loop --timeout 10 &
pid=$!
sleep 1
# run the blockcopy
virsh blockcopy testvm1 vda --wait --verbose --raw /tmp/copy.img --reuse-external
echo job started
sleep 5
virsh blockjob testvm1 vda --abort
wait $pid
Actual results:
error: Requested operation is not valid: domain is not transient
job started
error: Requested operation is not valid: No active operation on device: drive-virtio-disk0
Expected results:
Block Copy: [ 0 %]event 'block-job' for domain testvm1: Block Copy for /tmp/snap2.img ready
Block Copy: [100 %]
Now in mirroring phase
job started
event 'block-job' for domain testvm1: Block Copy for /tmp/snap2.img completed
event loop timed out
events received: 2
Additional info:
(In reply to FuXiangChun from comment #0)
> Description of problem:
> QE tested qemu-kvm-rhev-1.5.3-60.el7ev, it hit the same issue as 1114793
> bug. so file a new bug to track this issue. I am trying to reproduce it with
> qmp command directly. will update result to bz asap.
Have you tried reproducing it with QEMU only?
Summary: I tested with the latest qemu, this issue seams has gone.
Versions:
qemu-kvm-rhev:qemu-kvm-rhev-2.3.0-31.el7_2.5.x86_64
Steps:
1. Same step as https://bugzilla.redhat.com/show_bug.cgi?id=1114793#c0
2. Below results are the original bug expected results.
...
Block Copy: [100 %]event 'block-job' for domain testvm1: Block Copy for /tmp/snap2.img ready
Block Copy: [100 %]
Now in mirroring phase
job started
event 'block-job' for domain testvm1: Block Copy for /tmp/snap2.img completed
event loop timed out
events received: 2
Verified with:
qemu-kvm-rhev-2.6.0-20.el7.x86_64
qemu-img-rhev-2.6.0-20.el7.x86_64
kernel-3.10.0-491.el7.x86_64
Steps same as https://bugzilla.redhat.com/show_bug.cgi?id=1114793#c0
Results:
Block Copy: [100 %]event 'block-job' for domain testvm1: Block Copy for /tmp/snap2.img ready
Block Copy: [100 %]
Now in mirroring phase
job started
event 'block-job' for domain testvm1: Block Copy for /tmp/snap2.img completed
event loop timed out
events received: 2
Moving to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2673.html
Description of problem: QE tested qemu-kvm-rhev-1.5.3-60.el7ev, it hit the same issue as 1114793 bug. so file a new bug to track this issue. I am trying to reproduce it with qmp command directly. will update result to bz asap. Version-Release number of selected component (if applicable): qemu-kvm-rhev-1.5.3-60.el7ev.x86_64 3.10.0-123.4.2.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.qemu-img create -f raw base.img 10M 2.qemu-img create -f qcow2 -b base.img -o backing_fmt=raw snap1.img 3.qemu-img create -f qcow2 -b snap1.img -o backing_fmt=qcow2 snap2.img # set up blank space to hold the copy touch copy.img # cp base.img copy.img 4.xml file <domain type='kvm'> <name>testvm4</name> <memory unit='MiB'>256</memory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc-i440fx-rhel7.0.0'>hvm</type> <boot dev='hd'/> </os> <devices> <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/var/lib/libvirt/images/snap2.img'/> <target dev='hda' bus='virtio'/> </disk> <graphics type='vnc'/> </devices> </domain> 5.# check for events virsh event testvm1 block-job --loop --timeout 10 & pid=$! sleep 1 # run the blockcopy virsh blockcopy testvm1 vda --wait --verbose --raw /tmp/copy.img --reuse-external echo job started sleep 5 virsh blockjob testvm1 vda --abort wait $pid Actual results: error: Requested operation is not valid: domain is not transient job started error: Requested operation is not valid: No active operation on device: drive-virtio-disk0 Expected results: Block Copy: [ 0 %]event 'block-job' for domain testvm1: Block Copy for /tmp/snap2.img ready Block Copy: [100 %] Now in mirroring phase job started event 'block-job' for domain testvm1: Block Copy for /tmp/snap2.img completed event loop timed out events received: 2 Additional info: