Daniel P. Berrange c5728cd618 Add support for an explicit watchdog event ... This introduces a new event type VIR_DOMAIN_EVENT_ID_WATCHDOG This event includes the action that is about to be taken as a result of the watchdog triggering typedef enum { VIR_DOMAIN_EVENT_WATCHDOG_NONE = 0, VIR_DOMAIN_EVENT_WATCHDOG_PAUSE, VIR_DOMAIN_EVENT_WATCHDOG_RESET, VIR_DOMAIN_EVENT_WATCHDOG_POWEROFF, VIR_DOMAIN_EVENT_WATCHDOG_SHUTDOWN, VIR_DOMAIN_EVENT_WATCHDOG_DEBUG, } virDomainEventWatchdogAction; Thus there is a new callback definition for this event type typedef void (*virConnectDomainEventWatchdogCallback)(virConnectPtr conn, virDomainPtr dom, int action, void *opaque); * daemon/remote.c: Dispatch watchdog events to client * examples/domain-events/events-c/event-test.c: Watch for watchdog events * include/libvirt/libvirt.h.in: Define new watchdg event ID and callback signature * src/conf/domain_event.c, src/conf/domain_event.h, src/libvirt_private.syms: Extend API to handle watchdog events * src/qemu/qemu_driver.c: Connect to the QEMU monitor event for watchdogs and emit a libvirt watchdog event * src/remote/remote_driver.c: Receive and dispatch watchdog events to application * src/remote/remote_protocol.x: Wire protocol definition for watchdog events * src/qemu/qemu_monitor.c, src/qemu/qemu_monitor.h, src/qemu/qemu_monitor_json.c: Watch for WATCHDOG event from QEMU monitor		2010-03-26 13:53:01 +00:00
..
apparmor	add AppArmor test and examples to dist	2009-12-14 13:40:42 +01:00
domain-events	Add support for an explicit watchdog event	2010-03-26 13:53:01 +00:00
dominfo	gnulib added a new syntax-check test: use $(VAR), not @VAR@	2010-01-18 09:50:08 +01:00
domsuspend	gnulib added a new syntax-check test: use $(VAR), not @VAR@	2010-01-18 09:50:08 +01:00
hellolibvirt	Fix build in separate build directory	2009-10-01 16:55:09 +02:00
python	Add a Python example that lists active ESX domains	2009-11-08 01:03:24 +01:00
xml	test: Support loading node device info from file/XML	2009-10-05 14:07:17 -04:00