This bug has been copied from bug #903238 and has been proposed to be backported to 6.4 z-stream (EUS).
Moving to POST: http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-February/msg00216.html
The v2 that backports one more commit: http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-February/msg00223.html
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.
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
*** Bug 919057 has been marked as a duplicate of this bug. ***
*** Bug 924756 has been marked as a duplicate of this bug. ***
*** Bug 915636 has been marked as a duplicate of this bug. ***