From 90697be8896ce364456b81d3ba7eaadd10b1766e Mon Sep 17 00:00:00 2001 From: Jan Kiszka Date: Tue, 1 Dec 2009 15:19:55 +0100 Subject: live migration: Serialize vmstate saving in stage 2 The effect of this patch with current block migration is that its stage 2, ie. the first full walk-through of the block devices will be performed completely before RAM migration starts. This ensures that continuously changing RAM pages are not re-synchronized all the time while block migration is not completed. Future versions of block migration which will respect the specified downtime will generate a different pattern: After RAM migration has started as well, block migration may also continue to inject dirty blocks into the RAM stream once it detects that the number of pending blocks would extend the downtime unacceptably. Note that all this relies on the current registration order: block before RAM migration. Signed-off-by: Jan Kiszka Signed-off-by: Anthony Liguori --- savevm.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'savevm.c') diff --git a/savevm.c b/savevm.c index db44ed6..aefe052 100644 --- a/savevm.c +++ b/savevm.c @@ -1321,7 +1321,14 @@ int qemu_savevm_state_iterate(Monitor *mon, QEMUFile *f) qemu_put_byte(f, QEMU_VM_SECTION_PART); qemu_put_be32(f, se->section_id); - ret &= !!se->save_live_state(mon, f, QEMU_VM_SECTION_PART, se->opaque); + ret = se->save_live_state(mon, f, QEMU_VM_SECTION_PART, se->opaque); + if (!ret) { + /* Do not proceed to the next vmstate before this one reported + completion of the current stage. This serializes the migration + and reduces the probability that a faster changing state is + synchronized over and over again. */ + break; + } } if (ret) -- cgit v1.1