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 616703

Summary: qemu-kvm core dump with virtio-serial-pci max-port greater than 31
Product: Red Hat Enterprise Linux 6 Reporter: Keqin Hong <khong>
Component: qemu-kvmAssignee: Amit Shah <amit.shah>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1CC: amit.shah, gyue, lihuang, michen, mkenneth, snagar, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.114.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 11:31:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 580953    

Description Keqin Hong 2010-07-21 08:52:30 UTC
Description of problem:
qemu-kvm got core-dump with virtio-serial-pci max-port greater than 31.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.91.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot VM with "-device virtio-serial-pci,id=virtio-serial0,max_ports=32,vectors=4,bus=pci.0"
  
Actual results:
Aborted (core dumped)


Expected results:
no core dumps. qemu-kvm should prompt for maximum supported ports, then exit normally.

Additional info:
(gdb) bt
#0  0x00000033da4329b5 in raise () from /lib64/libc.so.6
#1  0x00000033da434195 in abort () from /lib64/libc.so.6
#2  0x0000000000577b06 in virtio_add_queue (vdev=0x4c43, queue_size=19523, handle_output=0x6)
    at /usr/src/debug/qemu-kvm-0.12.1.2/hw/virtio.c:597
#3  0x0000000000420f78 in virtio_serial_init (dev=<value optimized out>, max_nr_ports=36)
    at /usr/src/debug/qemu-kvm-0.12.1.2/hw/virtio-serial-bus.c:772
#4  0x0000000000420d5b in virtio_serial_init_pci (pci_dev=0x12608d0) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/virtio-pci.c:616
#5  0x0000000000419663 in pci_qdev_init (qdev=0x12608d0, base=0x844bd0) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/pci.c:1486
#6  0x00000000004c04b8 in qdev_init (dev=0x12608d0) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/qdev.c:275
#7  0x00000000004c0839 in qdev_device_add (opts=0x11adea0) at /usr/src/debug/qemu-kvm-0.12.1.2/hw/qdev.c:250
#8  0x0000000000408ec9 in device_init_func (opts=<value optimized out>, opaque=<value optimized out>)
    at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:4784
#9  0x000000000047588a in qemu_opts_foreach (list=<value optimized out>, func=0x408ec0 <device_init_func>, opaque=0x0, 
    abort_on_failure=<value optimized out>) at qemu-option.c:903
#10 0x000000000040d850 in main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>)
    at /usr/src/debug/qemu-kvm-0.12.1.2/vl.c:6238

Comment 2 RHEL Program Management 2010-07-21 09:19:40 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 3 Amit Shah 2010-07-21 09:40:53 UTC
Thanks, fix submitted upstream.

Not a blocker for 6.0 so moving to 6.1.

Comment 8 Golita Yue 2011-01-19 10:00:22 UTC
Verified in qemu-kvm-0.12.1.2-2.120.el6.x86_64, this bug fixed. 

The following note display when boot up with max_ports=32:

qemu-kvm: -device virtio-serial-pci,id=virtio-serial0,max_ports=32,bus=pci.0,addr=0x4: maximum ports supported: 31
qemu-kvm: -device virtio-serial-pci,id=virtio-serial0,max_ports=32,bus=pci.0,addr=0x4: Device 'virtio-serial-pci' could not be initialized

Comment 9 Miya Chen 2011-03-17 10:35:38 UTC
move to verified based on comment#8

Comment 10 errata-xmlrpc 2011-05-19 11:31:13 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0534.html

Comment 11 errata-xmlrpc 2011-05-19 12:46:37 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0534.html