On Wed, Jan 19, 2011 at 19:35:32 +, Daniel P. Berrange wrote:
> On Wed, Jan 19, 2011 at 08:19:36PM +0100, Jiri Denemark wrote:
> > In some circumstances, libvirtd would issue two STOPPED events after it
> > stopped a domain. This was because an EOF event can arrive after a qemu
> > process is k
On Wed, Jan 19, 2011 at 08:19:36PM +0100, Jiri Denemark wrote:
> In some circumstances, libvirtd would issue two STOPPED events after it
> stopped a domain. This was because an EOF event can arrive after a qemu
> process is killed but before qemuMonitorClose() is called.
>
> qemuHandleMonitorEOF()
In some circumstances, libvirtd would issue two STOPPED events after it
stopped a domain. This was because an EOF event can arrive after a qemu
process is killed but before qemuMonitorClose() is called.
qemuHandleMonitorEOF() should ignore EOF when the domain is not running.
I wasn't able to repr