From df4b1024526cae3479da3492d6371fd4a7324a03 Mon Sep 17 00:00:00 2001 From: Juan Quintela Date: Wed, 8 Oct 2014 10:58:10 +0200 Subject: migration: create new section to store global state This includes a new section that for now just stores the current qemu state. Right now, there are only one way to control what is the state of the target after migration. - If you run the target qemu with -S, it would start stopped. - If you run the target qemu without -S, it would run just after migration finishes. The problem here is what happens if we start the target without -S and there happens one error during migration that puts current state as -EIO. Migration would ends (notice that the error happend doing block IO, network IO, i.e. nothing related with migration), and when migration finish, we would just "continue" running on destination, probably hanging the guest/corruption data, whatever. Signed-off-by: Juan Quintela Reviewed-by: Dr. David Alan Gilbert --- include/migration/migration.h | 1 + 1 file changed, 1 insertion(+) (limited to 'include/migration') diff --git a/include/migration/migration.h b/include/migration/migration.h index afba233..86df6cc 100644 --- a/include/migration/migration.h +++ b/include/migration/migration.h @@ -197,4 +197,5 @@ size_t ram_control_save_page(QEMUFile *f, ram_addr_t block_offset, void ram_mig_init(void); void savevm_skip_section_footers(void); +void register_global_state(void); #endif -- cgit v1.1