https://bugzilla.novell.com/show_bug.cgi?id=854343 https://bugzilla.novell.com/show_bug.cgi?id=854343#c3 --- Comment #3 from Bruno Friedmann <bruno@ioda-net.ch> 2013-12-11 18:09:58 UTC --- Unfortunately experience prove that's not completely the case. I've started a vm (13.1) virsh start suse131-64 Domain suse131-64 started yoda:~ # virsh list Id Name State ---------------------------------------------------- 2 suse131-64 running yoda:~ # systemctl restart libvirtd.service yoda:~ # time virsh list Id Name State ---------------------------------------------------- 2 suse131-64 running real 0m44.209s user 0m0.012s sys 0m0.004s in the meantime systemctl status libvirtd.service libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Wed, 2013-12-11 19:03:22 CET; 54s ago Main PID: 21794 (libvirtd) CGroup: name=systemd:/system/libvirtd.service ├ 20284 /usr/bin/qemu-system-x86_64 -machine accel=kvm -name suse131-64 -S -machine pc-1.3,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,thr... ├ 21794 /usr/sbin/libvirtd --listen └ 21938 /sbin/udevadm settle Dec 11 19:03:22 yoda.labaroche.ioda.net systemd[1]: Started Virtualization daemon. Dec 11 19:03:22 yoda.labaroche.ioda.net libvirtd[21794]: libvirt version: 12.0 Dec 11 19:03:22 yoda.labaroche.ioda.net libvirtd[21794]: Configured security driver "none" disables default policy to create confined guests So safe to restart libvirtd ( doesn't destroy the running vm ) but then why did we get a so long first time connection ? Are you able to reproduce it? ps: the vm server is still using 12.3 but with kernel-stable + repo virtualization. -- 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.