| commit | 8e84865e54cb66fd7b57bb18c312ad3d56b6e276 | |
| author | Amit Shah <amit.shah@redhat.com> | |
| Tue, 27 Jul 2010 10:19:19 +0000 (27 15:49 +0530) | ||
| committer | Aurelien Jarno <aurelien@aurel32.net> | |
| Fri, 30 Jul 2010 21:14:08 +0000 (30 23:14 +0200) | ||
| tree | 92f787601f3a9d38ba05d4e98a8ed8b707c93a40 | treesnapshot (tar.gz zip) |
| parent | 7899f799b71ab502ddc2344e4e22265f3eb663c6 | commitdiff |
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>
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>
| migration.c | diffblobblamehistory | |
| monitor.c | diffblobblamehistory | |
| qerror.c | diffblobblamehistory | |
| qerror.h | diffblobblamehistory | |
| sysemu.h | diffblobblamehistory | |
| vl.c | diffblobblamehistory |