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 1745822 - qemu-kvm core dumped when hotplug 384 vcpu to win2019 guest
Summary: qemu-kvm core dumped when hotplug 384 vcpu to win2019 guest
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: qemu-kvm
Version: 8.1
Hardware: x86_64
OS: Windows
low
low
Target Milestone: rc
: ---
Assignee: Amnon Ilan
QA Contact: Yiqian Wei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-27 03:48 UTC by Yiqian Wei
Modified: 2021-01-25 09:25 UTC (History)
8 users (show)

Fixed In Version: qemu-kvm-4.2.0-25.module+el8.3.0+6986+29a4dcd7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-24 15:48:35 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
execute hotplug_384vcpu.sh script (1.82 KB, application/x-shellscript)
2019-08-27 03:48 UTC, Yiqian Wei
no flags Details

Description Yiqian Wei 2019-08-27 03:48:12 UTC
Created attachment 1608375 [details]
execute hotplug_384vcpu.sh script

Description of problem:
In the hotplug 384 vcpu process,qemu-kvm core dump 

Version-Release number of selected component (if applicable):
host version:
qemu-kvm-2.12.0-85.module+el8.1.0+4046+aa244b40.x86_64
kernel-4.18.0-136.el8.x86_64
seabios-1.11.1-4.module+el8.1.0+4010+d6842f29.x86_64

How reproducible:
100%

Steps to Reproduce:
1.execute "hotplug_384vcpu.sh" script
#sh hotplug_384vcpu.sh q35

Actual results: qemu-kvm core dumped
...
(qemu) QEMU 2.12.0 monitor - type 'help' for more information
(qemu) device_add SandyBridge-x86_64-cpu,socket-id=1,core-id=41,thread-id=1,id=core179
(qemu) free(): invalid next size (normal)
Ncat: Connection reset by peer.
hotplug_384vcpu.sh: line 63: 208589 Aborted                 (core dumped) $CLI
Ncat: Connection refused.
Ncat: Connection refused
...

Expected results:
qemu-kvm no core dumped,can hotplug 384 vcpu to win2019 guest,guest work well

Additional info:
1)host name:lenovo-sr950-01.khw2.lab.eng.bos.redhat.com
2)with rhel8.1.0 guest,not hit this issue.
3)(gdb) bt
#0  0x00007faeea4d38df in raise () at /lib64/libc.so.6
#1  0x00007faeea4bdcf5 in abort () at /lib64/libc.so.6
#2  0x00007faeea516c17 in __libc_message () at /lib64/libc.so.6
#3  0x00007faeea51d53c in .annobin_top_check.start () at /lib64/libc.so.6
#4  0x00007faeea51ee3c in _int_free () at /lib64/libc.so.6
#5  0x00007faeeef6d2e2 in g_free () at /lib64/libglib-2.0.so.0
#6  0x0000559f1e20d3c9 in m_free ()
#7  0x0000559f1e211846 in tcp_input ()
#8  0x0000559f1e20cbb0 in slirp_input ()
#9  0x0000559f1e1fcaa4 in net_slirp_receive ()
#10 0x0000559f1e1f4f3e in qemu_deliver_packet_iov ()
#11 0x0000559f1e1f7858 in qemu_net_queue_send_iov ()
#12 0x0000559f1e1f7dbb in net_hub_port_receive_iov ()
#13 0x0000559f1e1f4e77 in qemu_deliver_packet_iov ()
#14 0x0000559f1e1f7858 in qemu_net_queue_send_iov ()
#15 0x0000559f1e18c3b1 in net_tx_pkt_do_sw_fragmentation ()
#16 0x0000559f1e18d033 in net_tx_pkt_send ()
#17 0x0000559f1e1912c8 in e1000e_start_xmit.isra ()
#18 0x0000559f1e1913d1 in e1000e_set_tdt ()
#19 0x0000559f1e01a596 in memory_region_write_accessor ()
#20 0x0000559f1e0189e6 in access_with_adjusted_size ()
#21 0x0000559f1e01c84a in memory_region_dispatch_write ()
#22 0x0000559f1dfcaaa3 in flatview_write ()
#23 0x0000559f1dfcf243 in address_space_write ()
#24 0x0000559f1e02b878 in kvm_cpu_exec ()
#25 0x0000559f1e00821e in qemu_kvm_cpu_thread_fn ()
#26 0x00007faeea8672de in start_thread () at /lib64/libpthread.so.0
#27 0x00007faeea598133 in clone () at /lib64/libc.so.6

Comment 2 Yiqian Wei 2019-08-28 03:17:57 UTC
reproduce this bug with "qemu-kvm-2.12.0-65.module+el8.0.0+4068+6a1b8d73.4.x86_64",so this bug is not regression.

Comment 3 Yiqian Wei 2019-08-28 05:34:17 UTC
cannot reproduce this bug with fast train.

fast train version:
qemu-kvm-4.1.0-5.module+el8.1.0+4076+b5e41ebc.x86_64

Comment 4 Yiqian Wei 2019-08-28 07:15:38 UTC
can reproduce this bug with slow train.

host version:
qemu-kvm-2.12.0-85.module+el8.1.0+4046+aa244b40.x86_64
kernel-4.18.0-136.el8.x86_64
seabios-1.11.1-4.module+el8.1.0+4010+d6842f29.x86_64

 
(gdb) bt
#0  0x00007ffff2fb2050 in __condvar_dec_grefs () at /lib64/libpthread.so.0
#1  0x00007ffff2fb24a6 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#2  0x0000555555b7145d in qemu_cond_wait_impl ()
#3  0x0000555555877ab3 in qemu_wait_io_event ()
#4  0x00005555558791f8 in qemu_kvm_cpu_thread_fn ()
#5  0x00007ffff2fac2de in start_thread () at /lib64/libpthread.so.0
#6  0x00007ffff2cdd133 in clone () at /lib64/libc.so.6
(gdb)

Comment 8 Ademar Reis 2020-02-05 23:03:58 UTC
QEMU has been recently split into sub-components and as a one-time operation to avoid breakage of tools, we are setting the QEMU sub-component of this BZ to "General". Please review and change the sub-component if necessary the next time you review this BZ. Thanks

Comment 9 Yiqian Wei 2020-06-15 11:32:57 UTC
reproduce this bug version:
qemu-kvm-2.12.0-99.module+el8.2.0+6760+8b4be739.1.x86_64
kernel-4.18.0-213.el8.x86_64
virtio-win-prewhql-0.1-185
guest:win2019

verified this bug version:
qemu-kvm-4.2.0-25.module+el8.3.0+6986+29a4dcd7.x86_64
kernel-4.18.0-213.el8.x86_64
virtio-win-prewhql-0.1-185
guest:win2019


changed to verified status


Note You need to log in before you can comment on or make changes to this bug.