Re: [libvirt] latency between LIFECYCLE event and notification generation

On 05/11/2013 07:41 AM, nishant burte wrote: Libvirt is not a real-time scheduler. We make no guarantees about when events will be delivered, and while it is likely that events are delivered in order, I'm not even brave enough to state that libvirt even guarantees in-order delivery to remote hosts. All I know is that libvirt tries to deliver events as soon as it knows about them, but that events are always best-effort, and you have to be prepared for guest state to have changed yet again in between when libvirt detected that an event should be delivered and when your code receives the event. How is the guest shutting down? Guest-initiated action, libvirt shutdown request, or libvirt destroy request? Are you interested in the specifics used by the qemu hypervisor, or in the lifecycle events in general without regards to which hypervisor? You may be best off trying to use the sample programs shipped as part of libvirt (see examples/domain-events/events-{c,python} in libvirt.git) to see what events are triggered in response to which actions. [And someday, I'd like to teach virsh to deal with events] -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org