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. In fact I'm not even sure how this helps solve the quoted problem of detecting libvirtd restarts. 1. virt-viewer has a connection to libvirtd PID 123 2. virt-viewer listens for events from libvirtd PID 123 2. libvirtd PID 123 stops 3. libvirtd PID 456 starts 4. libvirtd PID 456 emits started events for virNetwork How exactly is virt-viewer supposed to be able to use the virNetwork events to detect libvirtd restarts ? They are being emitted by a libvirtd daemon that virt-viewer is not even connected to. 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
