libvirt daemon hangs on malloc locks after fork tries to virLogReset on parent
so i have posted my problem here: https://forum.level1techs.com/t/libvirtd-stuck-starting-up/158895
and quote it:
expecting my libvirtd to start normally as soon as i log in or atleast restarting it is >reliable once it gets stuck.
after logging in i do my usual routine and it worked for most of the time, but about 2 weeks ago virt-manager started showing this message
QEMU/KVM - Connecting…
no luck with virsh too.
atm i am doing a combination of restarting the service, rebooting and logging out and logging in again until it works.
i have enabled logs to a file and increasing log verbosity, and there seems to be no >error message. i stop the service, kill all related processes (dnsmasq too), restart it and it still >would get stuck i read about red hats libvirt common problems, but i cant seem to find any related >issue. the libvirt daemon is running and from the processes count and so forth it looks >normal.
i first assumed the network starts after the daemon and this caused problems starting it >up, but it wouldnt explain the inreproducibility of the problem.
i am running void
how could i further debug this? has any one have had similar expiriences? any suggestions?
EDIT: i added an strace here (from this “guide” :https://www.redhat.com/archives/libvirt-users/2017-February/msg00072.html) https://termbin.com/csovx
EDIT2: i added the timeout option (-t/–timeout) which should restart the service after given >seconds if no activity is registered.
EDIT3: i put dnsmasq and libvirt (separately and together) on disable for apparmor but couldnt get anything to work, both acted just the same with enabled profiles.
also putting them in complain mode would not bear any fruit or logs. so i went on and >started systrace back up which a collection is posted here shortly. strangely when i used strace it started to work as expected and the daemon would no longer hang. when i closed strace again and restarted the service (with all >networks and vms running in the background) it was unable to connect successfulyl.
so it maybe apparmor afterall…
anyways i managed to strace an unsuccessful try here:
and another strace of a successfull try:
at this point i am eager to file a bug report and let the pros school me.
additionally i want to add that the libvirt service on void linux looks like this:
#!/bin/sh sv check dbus >/dev/null || exit 1
[ -f ./conf ] && . ./conf
exec /bin/libvirtd $OPTS 2>&1