688723 – libvirtd crashes with poorly formatted command

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 688723 - libvirtd crashes with poorly formatted command

Summary: libvirtd crashes with poorly formatted command

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	libvirt
Sub Component:
Version:	6.1
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Osier Yang
QA Contact:	Virtualization Bugs
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2011-03-17 20:08 UTC by Alex Williamson
Modified:	2014-03-27 01:02 UTC (History)
CC List:	8 users (show)
Fixed In Version:	libvirt-0.8.7-15.el6
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2011-05-19 13:29:14 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2011:0596	0	normal	SHIPPED_LIVE	libvirt bug fix and enhancement update	2011-05-18 17:56:36 UTC

Description Alex Williamson 2011-03-17 20:08:52 UTC

Description of problem:

$ sudo virsh qemu-monitor-command rhel6vm-libvirt {system_reset}
error: server closed connection: 

$ sudo virsh list
error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: Connection refused
error: failed to connect to the hypervisor


Version-Release number of selected component (if applicable):
libvirt-0.8.7-11.el6.x86_64

How reproducible:
1/1

Steps to Reproduce:
1. do a bad json command as in description
2.
3.
  
Actual results:
libvirtd dies

Expected results:
no death

Additional info:

Comment 4 Osier Yang 2011-03-23 15:08:38 UTC

http://www.redhat.com/archives/libvir-list/2011-March/msg01066.html

patch pushed to upstream.

Comment 5 Osier Yang 2011-03-23 15:44:44 UTC

http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-March/msg00634.html

patch posted internally, move to POST.

Comment 6 Osier Yang 2011-03-25 08:43:10 UTC

*** Bug 690734 has been marked as a duplicate of this bug. ***

Comment 8 zhanghaiyan 2011-03-30 02:35:37 UTC

Reproduced this bug with older package libvirt-0.8.7-11.el6.x86_64
# for i in {1..10}; do virsh qemu-monitor-command rhel6-qcow2 {system_reset}; done
error: server closed connection: 

error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: Connection refused
......
# service libvirtd status
libvirtd dead but pid file exists

Verified this bug PASS with libvirt-0.8.7-15.el6.x86_64
- 2.6.32-125.el6.x86_64
- qemu-kvm-0.12.1.2-2.153.el6.x86_64
# for i in {1..10}; do virsh qemu-monitor-command rhel6-qcow2 {system_reset}; done
error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


error: internal error cannot parse json {system_reset}: lexical error: invalid char in json text.
                                      {system_reset}
                     (right here) ------^


[root@dhcp-65-132 ~]# virsh list
 Id Name                 State
----------------------------------
  7 rhel6-qcow2          running

[root@dhcp-65-132 ~]# service libvirtd status
libvirtd (pid  24069) is running...

Comment 11 errata-xmlrpc 2011-05-19 13:29:14 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/RHBA-2011-0596.html

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