https://bugzilla.novell.com/show_bug.cgi?id=854343 https://bugzilla.novell.com/show_bug.cgi?id=854343#c4 --- Comment #4 from James Fehlig <jfehlig@suse.com> 2013-12-11 18:39:53 UTC --- (In reply to comment #3)
So safe to restart libvirtd ( doesn't destroy the running vm ) but then why did we get a so long first time connection ?
dlopen'ing all the driver modules, resolving symbols, etc. ? Once the daemon and all drivers are loaded, subsequent virsh commands respond much quicker right? On my test system # systemctl restart libvirtd.service # time virsh list --all .. real 0m2.822s user 0m0.016s sys 0m0.016s # time virsh list --all .. real 0m0.047s user 0m0.024s sys 0m0.008s We could probably investigate if time required to load modules, etc. can be improved, but unfortunately I have bigger fish to fry ATM. I am interested in fixing the dependency problem you noted in #0 and will send a mail to the libvirt dev list about how to approach that. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.