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 996809 - qemu should not crash when boot guest with 260 scsi disks
Summary: qemu should not crash when boot guest with 260 scsi disks
Keywords:
Status: CLOSED DUPLICATE of bug 1007332
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Asias He
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 1003469 (view as bug list)
Depends On: 1007332
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-14 02:36 UTC by CongLi
Modified: 2013-10-16 14:11 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 987257
Environment:
Last Closed: 2013-10-16 14:11:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 CongLi 2013-08-14 03:05:37 UTC 
gdb info:

(gdb) bt
#0  0x00007fb7c9e528a5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007fb7c9e54085 in abort () at abort.c:92
#2  0x00007fb7c9e907b7 in __libc_message (do_abort=2, fmt=0x7fb7c9f77f80 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:198
#3  0x00007fb7c9e960e6 in malloc_printerr (action=3, str=0x7fb7c9f78250 "free(): invalid next size (normal)", ptr=<value optimized out>) at malloc.c:6311
#4  0x00007fb7c9e98c13 in _int_free (av=0x7fb790000020, p=0x7fb79000e060, have_lock=0) at malloc.c:4811
#5  0x00007fb7cc55bd08 in virtio_scsi_handle_cmd (vdev=0x7fb7ce83fc10, vq=0x7fb7e6733340) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/virtio-scsi.c:517
#6  0x00007fb7cc565715 in kvm_handle_io (env=0x7fb7e3ef2010) at /usr/src/debug/qemu-kvm-0.12.1.2/kvm-all.c:147
#7  kvm_run (env=0x7fb7e3ef2010) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1048
#8  0x00007fb7cc5657c9 in kvm_cpu_exec (env=<value optimized out>) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:1743
#9  0x00007fb7cc5666ad in kvm_main_loop_cpu (_env=0x7fb7e3ef2010) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:2004
#10 ap_main_loop (_env=0x7fb7e3ef2010) at /usr/src/debug/qemu-kvm-0.12.1.2/qemu-kvm.c:2060
#11 0x00007fb7cbe8f851 in start_thread (arg=0x7fb79e3e7700) at pthread_create.c:301
#12 0x00007fb7c9f0890d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115
(gdb)
Comment 6 Asias He 2013-09-18 04:52:10 UTC 
*** Bug 1003469 has been marked as a duplicate of this bug. ***
Comment 11 Ademar Reis 2013-10-16 13:32:05 UTC 
TestOnly bug, so keeping it in sync with Bug 1007332 (ON_QA)
Comment 12 Qunfang Zhang 2013-10-16 14:01:46 UTC 
(In reply to Ademar de Souza Reis Jr. from comment #11)
> TestOnly bug, so keeping it in sync with Bug 1007332 (ON_QA)

Hi, Ademar

Actually we plan to test bug 1007332 with the scenario in this bug, so we tested two bugs with 1 scenario. Do we need to add this bug to errata as well or treat it as a duplicate? 

Thanks,
Qunfang
Comment 13 Ademar Reis 2013-10-16 14:11:09 UTC 
(In reply to Qunfang Zhang from comment #12)
> (In reply to Ademar de Souza Reis Jr. from comment #11)
> > TestOnly bug, so keeping it in sync with Bug 1007332 (ON_QA)
> 
> Hi, Ademar
> 
> Actually we plan to test bug 1007332 with the scenario in this bug, so we
> tested two bugs with 1 scenario. Do we need to add this bug to errata as
> well or treat it as a duplicate? 

Given the nature of the other bug, the testcase is indeed this very same scenario, so marking it as duplicate is good enough. Thanks.

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