Jiri Denemark 38527c9ae0 qemu: Rework handling of shutdown event ... When QEMU guest finishes its shutdown sequence, qemu stops virtual CPUs and when started with -no-shutdown waits for us to kill it using SGITERM. Since QEMU is flushing its internal buffers, some time may pass before QEMU actually dies. We mistakenly used "paused" state (and events) for this which is quite confusing since users may see a domain going to pause while they expect it to shutdown. Since we already have "shutdown" state with "the domain is being shut down" semantics, we should use it for this state. However, the state didn't have a corresponding event so I created one and called its detail as VIR_DOMAIN_EVENT_SHUTDOWN_FINISHED (guest OS finished its shutdown sequence) with the intent to add VIR_DOMAIN_EVENT_SHUTDOWN_STARTED in the future if we have a sufficiently capable guest agent that can notify us when guest OS starts to shutdown.		2011-12-05 14:14:31 +01:00
..
.gitignore	Ignore auto-generated header file	2009-09-22 16:12:51 +01:00
libvirt-qemu.h	Define a QEMU specific API to attach to a running QEMU process	2011-07-12 15:39:03 +01:00
libvirt.h.in	qemu: Rework handling of shutdown event	2011-12-05 14:14:31 +01:00
Makefile.am	maint: add missing copyright notices	2011-07-28 15:01:17 -06:00
virterror.h	Export KVM Host Power Management capabilities	2011-11-22 11:31:22 +08:00