Red Hat Bugzilla – Bug 805950
Crash in virNetSocketWriteWire when deleting volumes in virt-manager
Last modified: 2012-08-09 19:23:52 EDT
libreport version: 2.0.8
cmdline: /usr/bin/python /usr/share/virt-manager/virt-manager.py
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
time: Thu 22 Mar 2012 09:56:29 PM SGT
backtrace: Text file, 144011 bytes
build_ids: Text file, 7913 bytes
dso_list: Text file, 18706 bytes
maps: Text file, 80149 bytes
smolt_data: Text file, 4196 bytes
:I was removing volumes one by one in "Storage" tab of "Connection Details" dialog until it crashed during deletion of next file.
:After restarting it, I continued deleting the rest of files. The problem persisted. The crashes happened with different image files and appeared randomly (deletion seems always successful, but some of them are followed by the crash, some aren't). The images were not used by any of the VMs (only single VM was configured).
:The images were in raw format and were created on Fedora 15 (currently F16) and left since OS reinstallation without re-creating VMs for them.
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:Mar 19 20:54:26 master yum: Updated: kross-python-4.8.1-1.fc16.x86_64
:Mar 19 20:56:21 master yum: Updated: liblouis-python-2.4.1-1.fc16.noarch
:Mar 19 20:56:25 master yum: Updated: plasma-scriptengine-python-4.8.1-6.fc16.x86_64
:Mar 19 20:57:08 master yum: Updated: libvirt-python-0.9.6-5.fc16.x86_64
:Mar 22 21:56:28 master kernel: [ 2047.852637] python: segfault at 10 ip 0000003a2699e3ff sp 00007fffff425a60 error 4 in libgtk-x11-2.0.so.0.2400.8[3a26800000+46c000]
:Mar 22 21:56:29 master abrt: Saved core dump of pid 3368 (/usr/bin/python) to /var/spool/abrt/ccpp-2012-03-22-21:56:29-3368 (52895744 bytes)
Created attachment 572007 [details]
Created attachment 572008 [details]
Created attachment 572009 [details]
Created attachment 572010 [details]
Created attachment 572011 [details]
Reassigning to libvirt
Actually there's a virt-manager fix for this IIRC (note to self: pull the fix out of the RHEL6 package)
*** Bug 825501 has been marked as a duplicate of this bug. ***
*** Bug 830466 has been marked as a duplicate of this bug. ***
*** Bug 817191 has been marked as a duplicate of this bug. ***
*** Bug 749234 has been marked as a duplicate of this bug. ***
*** Bug 813252 has been marked as a duplicate of this bug. ***
*** Bug 810501 has been marked as a duplicate of this bug. ***
virt-manager-0.9.3-1.fc16 has been submitted as an update for Fedora 16.
virt-manager-0.9.3-1.fc17 has been submitted as an update for Fedora 17.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-0.9.3-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
*** Bug 842491 has been marked as a duplicate of this bug. ***
virt-manager-0.9.4-1.fc17 has been submitted as an update for Fedora 17.
virt-manager-0.9.4-1.fc16 has been submitted as an update for Fedora 16.
virt-manager-0.9.4-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
virt-manager-0.9.4-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.