Red Hat Bugzilla – Bug 979392
[abrt] virt-manager crash from libguestfs launch_libvirt
Last modified: 2015-02-17 10:43:52 EST
Description of problem:
virt-manager crashes after about 15 seconds
Version-Release number of selected component:
cmdline: /usr/bin/python /usr/share/virt-manager/virt-manager
runlevel: N 5
Thread no. 1 (10 frames)
#6 launch_libvirt at launch-libvirt.c:153
#7 guestfs__launch at launch.c:88
#8 guestfs_launch at actions-3.c:142
#9 py_guestfs_launch at guestfs-py.c:2352
#10 call_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4098
#11 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2740
#12 fast_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4184
#13 call_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4119
#14 PyEval_EvalFrameEx at /usr/src/debug/Python-2.7.5/Python/ceval.c:2740
#15 fast_function at /usr/src/debug/Python-2.7.5/Python/ceval.c:4184
Created attachment 766538 [details]
Created attachment 766539 [details]
Created attachment 766540 [details]
Created attachment 766541 [details]
Created attachment 766542 [details]
Created attachment 766543 [details]
Created attachment 766544 [details]
Created attachment 766545 [details]
Created attachment 766546 [details]
Created attachment 766547 [details]
Created attachment 766548 [details]
What libguestfs version is this?
libguestfs-1.22.2-1.fc19.x86_64 is installed
Until this morning akmod-nvidia was installed. have had this issue before but then it was a known problem. also want to mention that i did a fedup from fedora 18 and not a installation using isntall iso.
Do you have the version of libvirt that you've got installed there?
Weirdly although the crash certainly happens in libguestfs, it's
a crash freeing a pointer returned by libvirt. Whatever that means ...
BTW as a workaround you can set:
which avoids running libvirt.
Actually i want to use libvirt in combo with virt-mananger.
I'm going to delete the whole libvirt config and start fresh.
maybe its because of configs of fedora 18.
please feel free to close this bugreport.
(In reply to Johannes Hofmann from comment #16)
> Actually i want to use libvirt in combo with virt-mananger.
> I'm going to delete the whole libvirt config and start fresh.
> maybe its because of configs of fedora 18.
> please feel free to close this bugreport.
Setting LIBGUESTFS_BACKEND=direct doesn't disable libvirt,
it just stops libguestfs from using libvirt, avoiding the
code path which is causing this crash.
I believe this is a real bug, although I cannot reproduce it
here (but I'm using slightly newer packages from Rawhide).
Therefore I would prefer to leave this bug open.
Found problem. did set selinux boolean virt_use_rawip to enable.
Now i can use virt-manager again.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.