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.
Bug 1170963 - test case 025 026 030 040 041 and 067 of qemu-iotests fail for qcow2 with qemu-kvm-1.5.3-83.el7.x86_64
Summary: test case 025 026 030 040 041 and 067 of qemu-iotests fail for qcow2 with qem...
Keywords:
Status: CLOSED DUPLICATE of bug 1427176
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Kevin Wolf
QA Contact: Ping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-05 08:41 UTC by Sibiao Luo
Modified: 2017-03-14 16:21 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-14 16:21:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
qemu-iotest-for-qcow2-results. (73.10 KB, text/plain)
2014-12-05 08:42 UTC, Sibiao Luo 		no flags Details
View All

Description Sibiao Luo 2014-12-05 08:41:28 UTC 
Description of problem:
test case 025 026 030 040 041 and 067 of qemu-iotests fail for qcow2 with qemu-kvm-1.5.3-83.el7.x86_64.

Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
3.10.0-211.el7.x86_64
qemu-kvm-1.5.3-83.el7.x86_64
qemu-kvm.git branch:
# git branch -v
  all                d3697f2 Update to qemu-kvm-1.5.3-83.el7
* rhel7/master-1.5.3 d3697f2 Update to qemu-kvm-1.5.3-83.el7
  rhev7-master-2.1.2 0f80785 [behind 5] Update to qemu-kvm-rhev-2.1.2-14.el7

How reproducible:
100%

Steps to Reproduce:
1.# git clone git://git.app.eng.bos.redhat.com/virt/rhel7/qemu-kvm.git
2.# cd qemu-kvm
  # git branch -a                           

  # git branch -v
    all                d3697f2 Update to qemu-kvm-1.5.3-83.el7
  * rhel7/master-1.5.3 d3697f2 Update to qemu-kvm-1.5.3-83.el7
    rhev7-master-2.1.2 0f80785 [behind 5] Update to qemu-kvm-rhev-2.1.2-14.el7
3.# git pull
4.# ./configure --target-list=x86_64-softmmu; make
5.Go to /home/qemu-kvm/tests/qemu-iotests directory.
  # export QEMU_PROG=/usr/libexec/qemu-kvm
6.# ./check -qcow2|vmdk|vhdx|raw...

Actual results:
after step 6, test case 025 026 030 040 041 and 067 of qemu-iotests fail for qcow2 with qemu-kvm-1.5.3-83.el7.x86_64.
Not run: 006 013 014 016 045 059 064 070 075 076 078 084 088 092
Failures: 025 026 030 040 041 067
Failed 6 of 63 tests

Expected results:
It should passed all testing cases successfully.

Additional info:
Comment 1 Sibiao Luo 2014-12-05 08:42:53 UTC 
Created attachment 965018 [details]
qemu-iotest-for-qcow2-results.
Comment 5 Kevin Wolf 2017-03-14 16:21:39 UTC 

*** This bug has been marked as a duplicate of bug 1427176 ***
Note You need to log in before you can comment on or make changes to this bug.