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.
020:
This is a QED bug, fixed by upstream commit 55aff7f1. It means that offline
commit returns an error after having performed the commit successfully.
We probably don't care.
030:
This is a test case bug.
034:
This one is real and it is an image corruption bug. We may want to fix it even
though we don't officially support QED. The test case passes after disabling
(commenting out) the zero write support in QED, so if we want to fix it, that's
what I would suggest.
041:
Doesn't fail for me. Probably a test case problem.
(In reply to Kevin Wolf from comment #10)
> Please test with qemu-kvm-rhev. Test cases 040 and 041 are tests for live
> commit
> and mirroring, which are disabled features in the RHEL version.
Yes, thanks for your kindly reminds. Retry it with qemu-kvm-rhev which has passed all the cases.
qemu-kvm]# git branch -v
* rhel6/master a1b4b8e Update to qemu-kvm-0.12.1.2-2.470.el6
[root@intel-e52650-16-1 qemu-kvm]# ./configure --target-list=x86_64-softmmu; make
qemu-kvm]# cat .git/config | grep url
url = git://git.app.eng.bos.redhat.com/virt/rhel6/qemu-kvm.git
qemu-kvm]# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-0.12.1.2-2.470.el6.x86_64
qemu-kvm]# export QEMU_PROG=/usr/libexec/qemu-kvm
qemu-kvm]# cd tests/qemu-iotests/
qemu-iotests]# ./check -qed
QEMU -- /usr/libexec/qemu-kvm
QEMU_IMG -- /home/qemu-kvm/tests/qemu-iotests/../../qemu-img
QEMU_IO -- /home/qemu-kvm/tests/qemu-iotests/../../qemu-io
QEMU_NBD -- /home/qemu-kvm/tests/qemu-iotests/../../qemu-nbd
IMGFMT -- qed
IMGPROTO -- file
PLATFORM -- Linux/x86_64 intel-e52650-16-1 2.6.32-544.el6.x86_64
SOCKET_SCM_HELPER --
...
Not run: 007 013 014 015 016 022 023 026 029 030 031 035 044 049 054 060 067 068 073 074 079 080 081 083 084 085 086 088 092 095 107 108 114
Passed all 31 tests
Base on above, set this bug to verified status, please correct me if any mistake, thanks.
Best Regards,
sluo
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-2015-1275.html
Created attachment 926696 [details] qemu-iotests-results-for-qed.txt