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 1089604 - QEMU core dumped when boot guest with a big multiple queues specified for virtio-scsi
Summary: QEMU core dumped when boot guest with a big multiple queues specified for vir...
Keywords:
Status: CLOSED DUPLICATE of bug 1067892
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Fam Zheng
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-21 06:44 UTC by Sibiao Luo
Modified: 2014-07-14 02:17 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-07-14 02:17:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sibiao Luo 2014-04-21 06:44:12 UTC 
Description of problem:
Boot guest with a big multiple queues specified for virtio-scsi, then QEMU core dumped.

Version-Release number of selected component (if applicable):
host info:
3.10.0-121.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
seabios-1.7.2.2-12.el7.x86_64
guest info:
3.10.0-121.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Boot guest with a big multiple queues specified for virtio-scsi.
# /usr/libexec/qemu-kvm -M pc -cpu host -enable-kvm -m 4096 -smp 64 -no-kvm-pit-reinjection -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x7,num_queues=64 -vnc :2 -monitor stdio
Warning: option deprecated, use lost_tick_policy property of kvm-pit instead.
QEMU 1.5.3 monitor - type 'help' for more information
(qemu) Aborted (core dumped)
2.
3.

Actual results:
after step 1, qemu core dumped, if num_queues<63 which cann't core dumped, while if num_queues>=63 core dumped.

Expected results:
It should no any QEMU core dumped, QEMU can give a warning prompt message for users if not support big num_queues.

Core was generated by `/usr/libexec/qemu-kvm -M pc -cpu host -enable-kvm -m 4096 -smp 64 -no-kvm-pit-r'.
Program terminated with signal 6, Aborted.
#0  0x00007fad077a2989 in raise () from /lib64/libc.so.6

(gdb) bt
#0  0x00007fad077a2989 in raise () from /lib64/libc.so.6
#1  0x00007fad077a4098 in abort () from /lib64/libc.so.6
#2  0x00007fad0cd4e075 in virtio_add_queue (vdev=vdev@entry=0x7fad0e4408c8, queue_size=queue_size@entry=128, 
    handle_output=handle_output@entry=0x7fad0cd47380 <virtio_scsi_handle_cmd>)
    at /usr/src/debug/qemu-1.5.3/hw/virtio/virtio.c:719
#3  0x00007fad0cd47e6f in virtio_scsi_common_init (s=s@entry=0x7fad0e4408c8)
    at /usr/src/debug/qemu-1.5.3/hw/scsi/virtio-scsi.c:607
#4  0x00007fad0cd47f11 in virtio_scsi_device_init (vdev=0x7fad0e4408c8)
    at /usr/src/debug/qemu-1.5.3/hw/scsi/virtio-scsi.c:622
#5  0x00007fad0cd4d056 in virtio_device_init (qdev=0x7fad0e4408c8) at /usr/src/debug/qemu-1.5.3/hw/virtio/virtio.c:1118
#6  0x00007fad0cc2d9d4 in device_realize (dev=0x7fad0e4408c8, err=0x7fffd04ddf90) at hw/core/qdev.c:178
#7  0x00007fad0cc2e93b in device_set_realized (obj=0x7fad0e4408c8, value=<optimized out>, err=0x7fffd04de080)
    at hw/core/qdev.c:693
#8  0x00007fad0ccd39be in property_set_bool (obj=0x7fad0e4408c8, v=<optimized out>, opaque=0x7fad0e441ce0, 
    name=<optimized out>, errp=0x7fffd04de080) at qom/object.c:1302
#9  0x00007fad0ccd5a97 in object_property_set_qobject (obj=0x7fad0e4408c8, value=<optimized out>, 
    name=0x7fad0ce2949a "realized", errp=0x7fffd04de080) at qom/qom-qobject.c:24
#10 0x00007fad0ccd4c80 in object_property_set_bool (obj=obj@entry=0x7fad0e4408c8, value=value@entry=true, 
    name=name@entry=0x7fad0ce2949a "realized", errp=errp@entry=0x7fffd04de080) at qom/object.c:853
#11 0x00007fad0cc2ddaa in qdev_init (dev=dev@entry=0x7fad0e4408c8) at hw/core/qdev.c:163
#12 0x00007fad0cc90bde in virtio_scsi_pci_init_pci (vpci_dev=0x7fad0e4400e0) at hw/virtio/virtio-pci.c:1160
#13 0x00007fad0cc91162 in virtio_pci_init (pci_dev=<optimized out>) at hw/virtio/virtio-pci.c:1025
#14 0x00007fad0cc64fa2 in pci_qdev_init (qdev=0x7fad0e4400e0) at hw/pci/pci.c:1720
#15 0x00007fad0cc2d9d4 in device_realize (dev=0x7fad0e4400e0, err=0x7fffd04de1b0) at hw/core/qdev.c:178
#16 0x00007fad0cc2e93b in device_set_realized (obj=0x7fad0e4400e0, value=<optimized out>, err=0x7fffd04de2d8)
    at hw/core/qdev.c:693
#17 0x00007fad0ccd39be in property_set_bool (obj=0x7fad0e4400e0, v=<optimized out>, opaque=0x7fad0e43fe70, 
    name=<optimized out>, errp=0x7fffd04de2d8) at qom/object.c:1302
#18 0x00007fad0ccd5a97 in object_property_set_qobject (obj=0x7fad0e4400e0, value=<optimized out>, 
    name=0x7fad0ce2949a "realized", errp=0x7fffd04de2d8) at qom/qom-qobject.c:24

#19 0x00007fad0ccd4c80 in object_property_set_bool (obj=obj@entry=0x7fad0e4400e0, value=value@entry=true, 
    name=name@entry=0x7fad0ce2949a "realized", errp=errp@entry=0x7fffd04de2d8) at qom/object.c:853
#20 0x00007fad0ccc2b2f in qdev_device_add (opts=0x7fad0df32110) at qdev-monitor.c:556
#21 0x00007fad0cd00029 in device_init_func (opts=<optimized out>, opaque=<optimized out>) at vl.c:2290
#22 0x00007fad0ce14d3b in qemu_opts_foreach (list=<optimized out>, func=func@entry=0x7fad0cd00020 <device_init_func>, 
    opaque=opaque@entry=0x0, abort_on_failure=abort_on_failure@entry=1) at util/qemu-option.c:1198
#23 0x00007fad0cbb9cd1 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at vl.c:4258
(gdb) 

Additional info:
Comment 1 Sibiao Luo 2014-04-21 06:44:35 UTC 
]# lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                2
On-line CPU(s) list:   0,1
Thread(s) per core:    1
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             AuthenticAMD
CPU family:            15
Model:                 107
Model name:            AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Stepping:              2
CPU MHz:               2700.000
BogoMIPS:              5411.30
Virtualization:        AMD-V
L1d cache:             64K
L1i cache:             64K
L2 cache:              512K
NUMA node0 CPU(s):     0,1
Comment 3 Sibiao Luo 2014-04-21 07:13:43 UTC 
We fix the virtio-scsi multi-queue support for qemu-kvm in bug 911389, and i also tried it on qemu-kvm-rhev-1.5.3-21.el7.x86_64 which also hit this issue.
So this issue is not regression issue and i think it cann't prevent this kind of dump by libvirt.

Best Regards,
sluo
Comment 5 Fam Zheng 2014-05-07 08:45:45 UTC 
Yet another example of "abort on input that I don't like" in virtio code.

Also triggerable with device hot plug, so giving an error message and exit is not the answer to all cases, but still slightly better.

For on flight queue add limit, none of the callers of virtio_add_queue handle fail case for now, so it's not an easy fix.

Setting priority and severity to low since libvirt won't hit this, but correct me if I'm wrong.

Fam
Comment 6 Fam Zheng 2014-07-14 02:17:29 UTC 
Libvirt won't hit the command line side of the crash, and we already have a BZ to improve the runtime virtio abort, so closing this as duplicate of bug 1067892.

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