Red Hat Bugzilla – Bug 1278847
libvirtd crashes in libxl if libvirt-daemon-driver-vbox is installed due to a SIGCHLD handling conflict
Last modified: 2017-05-03 14:31:16 EDT
Description of problem:
If both libvirt-daemon-driver-xen and libvirt-daemon-driver-vbox are installed, libvirtd crashes when an user connects to it.
This problem was reported by other people several months ago, but it is still not fixed:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install libvirt-daemon-driver-xen and libvirt-daemon-driver-vbox.
2. Boot the system as a Xen dom0.
3. Run virsh -c xen:///
libvirtd: libvirtd: libxl_fork.c:350: sigchld_installhandler_core: Assertion `((void)"application must negotiate with libxl about SIGCHLD", !(sigchld_saved_action.sa_flags & 4) && (sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 0) || sigchld_saved_action.__sigaction_handler.sa_handler == ((__sighandler_t) 1)))' failed.
systemd: libvirtd.service: Main process exited, code=killed, status=6/ABRT
systemd: libvirtd.service: Unit entered failed state.
systemd: libvirtd.service: Failed with result 'signal'.
Removing /usr/lib64/libvirt/connection-driver/libvirt_driver_vbox.so fixes the problem.
There was an older bug about this crash as well, but the culprit wasn't identified:
I can confirm this bug too.
I had to do: rpm -e --nodeps libvirt-daemon-driver-vbox
Then libvirtd worked.
When I tried to remove it via "dnf remove libvirt-daemon-driver-vbox" DNF wanted to remove libvirt too, so I did "rpm -e --nodeps libvirt-daemon-driver-vbox"
I don't see why libvirt needs libvirt-daemon-driver-vbox. Wrong dependency issue perhaps?
'libvirt' is just a back compatible meta-package that pulls in *all* libvirt* packages. You can safely remove it. If you want xen bits all you really need is libvirt-client, libvirt-daemon, libvirt-daemon-driver-xen
(In reply to Cole Robinson from comment #3)
I see, thanks for pointing that out.
Note I did revive the thread in november and one the xen devs added more info:
But I still don't think this is resolved anywhere
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
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 23 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.
It is still broken on Fedora 25.