On Wed, Nov 19, 2014 at 12:39:25PM +0100, Christophe Fergeau wrote: > Hey, > > On Wed, Nov 19, 2014 at 04:31:00AM +0100, Fabiano Fidêncio wrote: > > Apart from the usual virDomain's Lifecycle events, we have to listen to > > the virNetwork's Lifecycle events in order to get notifications about > > libvirt deamon being started/stopped/restarted, which is useful when > > connecting to guest through qemu+ssh:// > > virNetwork lifecycle events are related to libvirt networks > started/stopped with virsh net-start/virsh net-destroyed. That you get > such events when libvirtd restarts seems to just be a side-effect. Imo > we really should get an event from virConnectRegisterCloseCallback when > libvirtd goes away. Could it be that libvirt has a similar issue to what > was fixed in virt-viewer in 3eaecbb "Use socat instead of nc if > possible" ? Yeah, virConnectRegisterCloseCallback should be sufficient to detect when libvirtd goes away. If it isn't working for some cases plesae do report a bug so we can fix it. Apps shouldn't have to play games to infer when libvirtd went away. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ virt-tools-list mailing list virt-tools-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/virt-tools-list
