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.
Comment 2RHEL Program Management
2013-10-13 23:02:52 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Description of problem: met this quit (core dumped) by chance that when start guest with virtio serial and start guest agent inside guest, then connect the chardev socket in host side for sending commands to guest and press 'Ctrl |' keyboard will trigger the chardev socket for virtagent quit (core dumped). Version-Release number of selected component (if applicable): host info: 2.6.32-420.el6.x86_64 qemu-kvm-0.12.1.2-2.410.el6.x86_64 nc-1.84-22.el6.x86_64 guest info: 2.6.32-420.el6.x86_64 qemu-guest-agent-0.12.1.2-2.410.el6.x86_64 How reproducible: Steps to Reproduce: 1.start guest with virtio serial and start guest agent inside guest. e.g:...-chardev socket,path=/tmp/qga.sock,server,nowait,id=qga0 -device virtio-serial -device virtserialport,chardev=qga0,name=org.qemu.guest_agent.0 2.connect the chardev socket in host side for sending commands to guest. # service qemu-ga restart Stopping qemu-ga: [ OK ] Starting qemu-ga: [ OK ] # service qemu-ga status qemu-ga (pid 2576) is running... 3.press \ and 'Ctrl |' keyboard. # nc -U /tmp/qga.sock readline \ <----------press '\' {"error": {"class": "JSONParsing", "desc": "Invalid JSON syntax", "data": {}}} ^\Quit (core dumped) <----------press '|' Actual results: after step 3, the chardev socket for virtagent quit (core dumped), bt log as following: Core was generated by `nc -U /tmp/qga.sock readline'. Program terminated with signal 3, Quit. #0 0x00000034012df2d8 in poll () from /lib64/libc.so.6 Missing separate debuginfos, use: debuginfo-install glib2-2.26.1-3.el6.x86_64 glibc-2.12-1.130.el6.x86_64 (gdb) bt #0 0x00000034012df2d8 in poll () from /lib64/libc.so.6 #1 0x0000000000401ae9 in readwrite (nfd=3) at netcat.c:712 #2 0x000000000040302c in main (argc=<value optimized out>, argv=<value optimized out>) at netcat.c:366 (gdb) bt full #0 0x00000034012df2d8 in poll () from /lib64/libc.so.6 No symbol table info available. #1 0x0000000000401ae9 in readwrite (nfd=3) at netcat.c:712 pfd = {{fd = 3, events = 1, revents = 0}, {fd = 0, events = 1, revents = 0}} buf = '\000' <repeats 16120 times>"\352, R#\001\064", '\000' <repeats 11 times>, "\004\000\000\000\000\000\000\000\300\016Y\001\064\000\000\000\004\000\000\000\000\000\000\000\030\000\000\000\000\000\000\000\000O>\257\377\177\000\000\260N>\257\377\177\000\000\235\343,\001\064", '\000' <repeats 11 times>"\330, =@\000\000\000\000\000\000\000\000\000\001", '\000' <repeats 11 times>, "\001", '\000' <repeats 15 times>, "H\222>\257\377\177", '\000' <repeats 18 times>, "\003", '\000' <repeats 15 times>, "+$@\000\000\000\000\000\001\000/tmp/qga.sock", '\000' <repeats 80 times> n = <value optimized out> wfd = <value optimized out> lfd = <value optimized out> plen = <value optimized out> #2 0x000000000040302c in main (argc=<value optimized out>, argv=<value optimized out>) at netcat.c:366 ch = <value optimized out> s = 3 ret = 0 socksv = 5 host = 0x7fffaf3e9877 "/tmp/qga.sock" uport = <value optimized out> endp = 0x0 hints = {ai_flags = 0, ai_family = 0, ai_socktype = 0, ai_protocol = 0, ai_addrlen = 0, ai_addr = 0x0, ai_canonname = 0x0, ai_next = 0x0} sv = 0x0 len = <value optimized out> cliaddr = {ss_family = 37150, __ss_align = 223357765255, __ss_padding = "v", '\000' <repeats 23 times>"\377, \262\360\000\000\000\000\000\302\000\000\000\000\000\000\000\036\221>\257\377\177\000\000\037\221>\257\377\177\000\000\001", '\000' <repeats 15 times>"\355, \b)\001\064", '\000' <repeats 11 times>, "\020\070@", '\000' <repeats 13 times>, "\003\020@\000\000\000\000"} proxy = <value optimized out> proxyhost = <value optimized out> proxyport = <value optimized out> proxyhints = {ai_flags = 0, ai_family = 0, ai_socktype = 0, ai_protocol = 0, ai_addrlen = 0, ai_addr = 0x0, ai_canonname = 0x0, ai_next = 0x0} (gdb) Expected results: it should not quit and no any core dump, it should give a prompt message instead, like: {"error": {"class": "JSONParsing", "desc": "Invalid JSON syntax", "data": {}}} Additional info: