Re: [libvirt] [PATCH v5 5/5] startupPolicy: Emit event on disk source dropping

If a disk source gets dropped because it is not accessible, mgmt application might want to be informed about this. Therefore we need to emit an event. The event presented in this patch is however a bit superset of what written above. The reason is simple: an intention to be easily expanded, e.g. on 'user ejected disk in guest' events. Therefore, callback gets source string and disk alias (which should be unique among a domain) and reason (an integer); --- daemon/remote.c | 51 +++++++++++++ examples/domain-events/events-c/event-test.c | 29 +++++++- examples/domain-events/events-python/event-test.py | 4 + include/libvirt/libvirt.h.in | 36 +++++++++ python/libvirt-override-virConnect.py | 9 +++ python/libvirt-override.c | 53 ++++++++++++++ src/conf/domain_event.c | 76 ++++++++++++++++++++ src/conf/domain_event.h | 11 +++ src/libvirt_private.syms | 2 + src/qemu/qemu_domain.c | 7 ++ src/qemu/qemu_process.c | 14 ++-- src/remote/remote_driver.c | 36 +++++++++ src/remote/remote_protocol.x | 11 +++- src/remote_protocol-structs | 7 ++ 14 files changed, 337 insertions(+), 9 deletions(-)