Report the new VIR_DOMAIN_EVENT_STOPPED_REBOOT reason when reboot has been requested. I have only tested this on Xen. I preferred to rely on the stopped reason, as there is no discussion that it should be sent, while for the reboot event, there is debate that it shouldn't always be sent. CI: https://gitlab.com/libvirt/libvirt/-/merge_requests/567 Previous discussion and patches: https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/ZB5AL... https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/KYAL4... https://lists.libvirt.org/archives/list/devel@lists.libvirt.org/thread/5W4TO... Since last discussion, I: - Joined the libvirt patches so that each patch can build - Joined the drivers patches - Joined the NEWS patches - Fixed the documentation message Ben Grande (4): libvirt: Add stopped reason of reboot docs: libvirt-domain: briefly document reboot event drivers: Propagate stopped reason of reboot NEWS: Introduce VIR_DOMAIN_EVENT_STOPPED_REASON NEWS.rst | 12 ++++++++++++ examples/c/misc/event-test.c | 3 +++ include/libvirt/libvirt-domain.h | 1 + src/libvirt-domain.c | 5 ++++- src/libxl/libxl_domain.c | 2 +- src/lxc/lxc_process.c | 2 +- src/test/test_driver.c | 2 +- tools/virsh-domain-event.c | 3 ++- 8 files changed, 25 insertions(+), 5 deletions(-) -- Benjamin Grande