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 915353 - Concurrency/locking causes segfault
Summary: Concurrency/locking causes segfault
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.4
Hardware: x86_64
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Michal Privoznik
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 915636 919057 924756 (view as bug list)
Depends On: 903238
Blocks: 896690
TreeView+ depends on / blocked
 
Reported: 2013-02-25 15:08 UTC by Chris Pelland
Modified: 2018-12-01 16:07 UTC (History)
16 users (show)

Fixed In Version: libvirt-0.10.2-18.el6_4.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-21 13:55:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 336833 0 None None None 2018-12-01 16:07:09 UTC
Red Hat Product Errata RHBA-2013:0664 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2013-03-21 17:37:54 UTC

Description Chris Pelland 2013-02-25 15:08:17 UTC 
This bug has been copied from bug #903238 and has been proposed
to be backported to 6.4 z-stream (EUS).
Comment 4 Michal Privoznik 2013-02-25 16:01:07 UTC 
Moving to POST:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-February/msg00216.html
Comment 5 Michal Privoznik 2013-02-25 17:39:19 UTC 
The v2 that backports one more commit:

http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-February/msg00223.html
Comment 7 yanbing du 2013-03-18 10:42:58 UTC 
Reproduce this bug with libvirt-0.10.2-18.el6.x86_64.
Following the steps from
http://www.redhat.com/archives/libvir-list/2012-December/msg01365.html
About 15 mins later, libvirtd crashed:

# virsh list
error: Failed to reconnect to the hypervisor
error: no valid connection
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': Connection refused

# service libvirtd status
libvirtd dead but pid file exists

libvirtd.log:

2013-03-18 10:14:34.707+0000: 3874: error : qemuMonitorIO:613 : internal error End of file from monitor
Caught Segmentation violation dumping internal log buffer:


    ====== start of log =====
<snip/>
     ====== end of log =====

Then upgrade libvirt to libvirt-0.10.2-18.el6_4.1.x86_64, and test again, about 20 mins later, libvirtd still running, So this bug can move to VERIFIED.
Comment 9 errata-xmlrpc 2013-03-21 13:55:35 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-2013-0664.html
Comment 10 Eric Blake 2013-04-19 15:51:18 UTC 
*** Bug 919057 has been marked as a duplicate of this bug. ***
Comment 11 Eric Blake 2013-05-15 15:00:39 UTC 
*** Bug 924756 has been marked as a duplicate of this bug. ***
Comment 12 John Ferlan 2013-05-22 11:00:19 UTC 
*** Bug 915636 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.