fix segfault in setting migration speed
commit0bb05eaff04d30609a98c0dae80bb5dba3e4e799
authorGlauber Costa <glommer@redhat.com>
Tue, 14 Jul 2009 22:26:51 +0000 (14 18:26 -0400)
committerAnthony Liguori <aliguori@us.ibm.com>
Thu, 16 Jul 2009 22:28:51 +0000 (16 17:28 -0500)
tree114859324a6725453f0cf49aef7c74814377e09a
parent9f6839d4b1721524a10c77768f73697cf1724ce5
fix segfault in setting migration speed

Hi,

Whoever wrote this migrate_set_speed function is totally stupid.

Any failed or completed migration keeps its state to allow probing of
migration data, but has no associated file anymore. It is, thus,
possible to crash qemu by calling migrate_set_speed after a migration
is finished (or failed, or cancelled), but before another one starts.

This patch fixes it.

Signed-off-by: Glauber Costa <glommer@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
savevm.c