summaryrefslogtreecommitdiff
path: root/tests/nwfilterxml2xmlin
diff options
context:
space:
mode:
authorJiri Denemark <jdenemar@redhat.com>2010-04-27 10:10:31 +0200
committerJiri Denemark <jdenemar@redhat.com>2010-04-27 12:14:47 +0200
commit35b6137696cd102b60aa8f919554b416d0caca6f (patch)
tree0f1baa3537d23a0603e1f3d514596efe323bf566 /tests/nwfilterxml2xmlin
parent29bca037aa9144f7013c7845715a4d2bc15b802a (diff)
downloadlibvirt-35b6137696cd102b60aa8f919554b416d0caca6f.tar.gz
Ignore qemu STOP event when stopping CPUs
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 event and we usually want to issue a more specific event. 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 best solution which I was able to come up with and it doesn't introduce a race condition.
Diffstat (limited to 'tests/nwfilterxml2xmlin')
0 files changed, 0 insertions, 0 deletions