> > > By setting vm->status to PAUSED before actually sending the request to
> > > qemu (and resetting it back if the request fails) we can ignore the
> > > event since the event handler does nothing when the guest is already
> > > paused. This solution is quite hacky but unfortunately it's the bes
On Tue, 27 Apr 2010 20:01:06 +0100
"Daniel P. Berrange" wrote:
> On Tue, Apr 27, 2010 at 03:50:20PM -0300, Luiz Capitulino wrote:
> > On Tue, 27 Apr 2010 11:20:39 +0200
> > jdene...@redhat.com wrote:
> >
> > > From: Jiri Denemark
> > >
> > > With JSON qemu monitor, we get a STOP event from qem
On Tue, Apr 27, 2010 at 03:50:20PM -0300, Luiz Capitulino wrote:
> On Tue, 27 Apr 2010 11:20:39 +0200
> jdene...@redhat.com wrote:
>
> > From: Jiri Denemark
> >
> > With JSON qemu monitor, we get a STOP event from qemu whenever qemu
> > stops guests CPUs. The downside of it is that vm->state is
On Tue, 27 Apr 2010 11:20:39 +0200
jdene...@redhat.com wrote:
> From: Jiri Denemark
>
> With JSON qemu monitor, we get a STOP event from qemu whenever qemu
> stops guests CPUs. The downside of it is that vm->state is changed to
> PAUSED and a new generic paused event is send to applications. How
> > With JSON qemu monitor, we get a STOP event from qemu whenever qemu
> > stops guests CPUs. The downside of it is that vm->state is changed to
> > PAUSED and a new generic paused event is send to applications. However,
> > when we ask qemu to stop the CPUs we are not really interested in qemu
>
> > With JSON qemu monitor, we get a STOP event from qemu whenever qemu
> > stops guests CPUs. The downside of it is that vm->state is changed to
> > PAUSED and a new generic paused event is send to applications. However,
> > when we ask qemu to stop the CPUs we are not really interested in qemu
>
On Tue, Apr 27, 2010 at 11:20:39AM +0200, jdene...@redhat.com wrote:
> From: Jiri Denemark
>
> With JSON qemu monitor, we get a STOP event from qemu whenever qemu
> stops guests CPUs. The downside of it is that vm->state is changed to
> PAUSED and a new generic paused event is send to application
From: Jiri Denemark
With JSON qemu monitor, we get a STOP event from qemu whenever qemu
stops guests CPUs. The downside of it is that vm->state is changed to
PAUSED and a new generic paused event is send to applications. However,
when we ask qemu to stop the CPUs we are not really interested in q