nishant burte
2013-May-10 08:17 UTC
[libvirt-users] latency between LIFECYCLE event and notification generation
Hi, I have registered for LIFECYCLE events of libvirt. But I don't know, 1. about the the latency of these events happening and notification generation. e.g. suppose a VM goes down. How much time it takes to realize that the particular VM has gone down(going to say, DEFINED state) and then notification is generated? 2. Second question is, can someone please explain what are the sequence of steps happen between a VM going down and the notification is generated? Coul you please answer both the queries? Thanks Nishant -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20130510/2a7e56a1/attachment.htm>
Apparently Analagous Threads
- node device lifecycle callback can't resive event
- Suspend fails, "not managed by Xend lifecycle support"
- [RFC] [XEND] Lifecycle Patches 1/7
- Puppet Development Lifecycle Documentation - How to contribute to Puppet
- [PATCH] virtio-mmio: don't break lifecycle of vm_dev