summaryrefslogtreecommitdiff
path: root/migration.c
diff options
context:
space:
mode:
authorAmit Shah <amit.shah@redhat.com>2010-07-27 15:49:19 +0530
committerAurelien Jarno <aurelien@aurel32.net>2010-07-30 23:14:08 +0200
commit8e84865e54cb66fd7b57bb18c312ad3d56b6e276 (patch)
tree92f787601f3a9d38ba05d4e98a8ed8b707c93a40 /migration.c
parent7899f799b71ab502ddc2344e4e22265f3eb663c6 (diff)
migration: Accept 'cont' only after successful incoming migration
When a 'cont' is issued on a VM that's just waiting for an incoming migration, the VM reboots and boots into the guest, possibly corrupting its storage since it could be shared with another VM running elsewhere. Ensure that a VM started with '-incoming' is only run when an incoming migration successfully completes. A new qerror, QERR_MIGRATION_EXPECTED, is added to signal that 'cont' failed due to no incoming migration has been attempted yet. Reported-by: Laine Stump <laine@redhat.com> Signed-off-by: Amit Shah <amit.shah@redhat.com> Reviewed-by: Luiz Capitulino <lcapitulino@redhat.com> Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Diffstat (limited to 'migration.c')
-rw-r--r--migration.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/migration.c b/migration.c
index 650eb78d26..a160462dfa 100644
--- a/migration.c
+++ b/migration.c
@@ -67,6 +67,8 @@ void process_incoming_migration(QEMUFile *f)
qemu_announce_self();
DPRINTF("successfully loaded vm state\n");
+ incoming_expected = false;
+
if (autostart)
vm_start();
}