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 1069239 - QMP socket breaks on unexpected close
Summary: QMP socket breaks on unexpected close
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Miroslav Rezanina
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1060024
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-24 14:33 UTC by Jan Kurik
Modified: 2018-12-04 17:36 UTC (History)
17 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.415.el6_5.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-10 10:00:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0262 0 normal SHIPPED_LIVE qemu-kvm bug fix update 2014-03-10 13:59:56 UTC

Description Jan Kurik 2014-02-24 14:33:00 UTC 
This bug has been copied from bug #1060024 and has been proposed
to be backported to 6.5 z-stream (EUS).
Comment 5 Qunfang Zhang 2014-02-27 05:44:08 UTC 
Reproduced on qemu-kvm-0.12.1.2-2.415.el6_5.4.x86_64:

1. Start qemu command line with qmp:

# /usr/libexec/qemu-kvm -qmp unix:/tmp/qmp,server,nowait
VNC server running on `::1:5900'

2. Run the script in bug 1060024:

# python break_qmp.py  qemu-kvm/  /tmp/qmp 
Connecting to QMP...
OK
Connecting using socket...
OK
Connecting to QMP...
^^^^^^^^^^^^^^^^^^ (Stuck here.)


#top (On host)

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND       
 1082 root      20   0  388m  21m 5084 R 103.4  0.6   0:14.50 qemu-kvm     
 1078 root      20   0 15036 1184  904 R  0.3  0.0   0:00.19 top  
   
Result: The script stuck and host top shows qemu-kvm burns cpu. 


Verified on qemu-kvm-0.12.1.2-2.415.el6_5.5.x86_64:


# /usr/libexec/qemu-kvm -qmp unix:/tmp/qmp,server,nowait
VNC server running on `::1:5900'

# python break_qmp.py  qemu-kvm/  /tmp/qmp 
Connecting to QMP...
OK
Connecting using socket...
OK
Connecting to QMP...
OK
Connecting using socket...
OK
Connecting to QMP...
OK
Connecting using socket...
OK
......
(Continue printing the log)

# top (on host) 

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND       
 1129 root      20   0  388m  21m 5072 R 67.1  0.6   0:16.49 qemu-kvm      
 1141 root      20   0  149m 5540 2700 R 46.9  0.1   0:06.68 python  
      
Result: The script does not stuck and host top info shows qemu-kvm does not consume 100% cpu. 

Based on above, the bug is fixed.
Comment 8 errata-xmlrpc 2014-03-10 10:00:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0262.html
Note You need to log in before you can comment on or make changes to this bug.