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.

Bug 1088610

Summary: qemu-img coredumpd when try to create a gluster format image
Product: Red Hat Enterprise Linux 6 Reporter: Jeff Cody <jcody>
Component: qemu-kvmAssignee: Jeff Cody <jcody>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.6CC: bsarathy, chayang, hhuang, juzhang, mazhang, michen, mkenneth, qiguo, qzhang, rbalakri, sluo, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.425.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1088150 Environment:
Last Closed: 2014-10-14 06:58:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 1 Miroslav Rezanina 2014-04-29 06:02:37 UTC
Fix included in qemu-kvm-0.12.1.2-2.425.el6

Comment 3 mazhang 2014-06-26 02:33:50 UTC
Reproduce this bug on qemu-img-0.12.1.2-2.415.el6.x86_64.

Host:
qemu-kvm-tools-0.12.1.2-2.415.el6.x86_64
qemu-kvm-0.12.1.2-2.415.el6.x86_64
qemu-img-0.12.1.2-2.415.el6.x86_64


Steps to Reproduce:
1.Try to create a gluster format image:
# qemu-img create -f gluster test 1G
Formatting 'test', fmt=gluster size=1073741824 
Segmentation fault (core dumped)

(gdb) bt full
#0  0x00007ffff7fd7145 in ?? ()
No symbol table info available.
#1  0x00007ffff7fd7458 in ?? ()
No symbol table info available.
#2  0x00007ffff7fb179d in bdrv_img_create ()
No symbol table info available.
#3  0x00007ffff7fa26f5 in ?? ()
No symbol table info available.
#4  0x00007ffff625fd1d in __libc_start_main () from /lib64/libc.so.6
No symbol table info available.
#5  0x00007ffff7fa1a29 in _start ()
No symbol table info available.


Verify this bug on qemu-img-0.12.1.2-2.428.el6.x86_64.

Host:
qemu-kvm-debuginfo-0.12.1.2-2.428.el6.x86_64
qemu-img-0.12.1.2-2.428.el6.x86_64
qemu-kvm-tools-0.12.1.2-2.428.el6.x86_64
qemu-kvm-0.12.1.2-2.428.el6.x86_64

Result:
# qemu-img create -f gluster test 1G
Formatting 'test', fmt=gluster size=1073741824 
Usage: file=gluster[+transport]://[server[:port]]/volname/image[?socket=...]
test: error while creating gluster: Invalid argument

So this bug has been fixed.

Comment 4 errata-xmlrpc 2014-10-14 06:58:19 UTC
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.

http://rhn.redhat.com/errata/RHBA-2014-1490.html