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 999749 - [RFE] should add a item to specify the backing file format when use qemu-img info to check it
Summary: [RFE] should add a item to specify the backing file format when use qemu-img ...
Keywords:
Status: CLOSED DUPLICATE of bug 1010610
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Hanna Czenczek
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-22 02:44 UTC by Sibiao Luo
Modified: 2014-03-21 09:33 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Cause: Consequence: Fix: Result:
Clone Of:
Environment:
Last Closed: 2014-03-21 09:33:26 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sibiao Luo 2013-08-22 02:44:19 UTC 
Description of problem:
rhel6 have no specified the backing file format after create snapshot when use qemu-img info to check it, but rhel7.0 has it.

Version-Release number of selected component (if applicable):
host info:
2.6.32-412.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.397.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.for rhel6.5:
# qemu-img create -f qcow2 -b data-disk.qcow2 -F qcow2 sluo-snapshot
Formatting 'sluo-snapshot', fmt=qcow2 size=10737418240 backing_file='data-disk.qcow2' backing_fmt='qcow2' encryption=off cluster_size=65536 
# qemu-img info sluo-snapshot 
image: sluo-snapshot
file format: qcow2
virtual size: 10G (10737418240 bytes)
disk size: 196K
cluster_size: 65536
backing file: data-disk.qcow2
2.for rhel7.0:
# qemu-img create -f qcow2 -b data-disk.qcow2 -F qcow2 sluo-snapshot
Formatting 'sluo-snapshot', fmt=qcow2 size=1073741824 backing_file='data-disk.qcow2' backing_fmt='qcow2' encryption=off cluster_size=65536 lazy_refcounts=off 
# qemu-img info sluo-snapshot 
image: sluo-snapshot
file format: qcow2
virtual size: 1.0G (1073741824 bytes)
disk size: 196K
cluster_size: 65536
backing file: data-disk.qcow2
backing file format: qcow2           <------------------here

Actual results:

Expected results:
should add a item to specify the backing file format when use qemu-img info to check it.

Additional info:
Comment 2 Hanna Czenczek 2014-03-21 04:07:18 UTC 
This is fixed for me since the backport of c054b3fd78f28b12f4d066583fc0ade017752479 (2ecf5c22465ffcfad3cad70b8c634703f0e9cfbb downstream), that is, as of version qemu-kvm-0.12.1.2-2.409.el6.

I'd propose closing this bug as WORKSFORME.
Comment 3 Kevin Wolf 2014-03-21 09:33:26 UTC 
I think the usual resolution in such cases is DUPLICATE. Closing.

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