1. 06 11月, 2015 1 次提交
  2. 05 11月, 2015 8 次提交
  3. 04 11月, 2015 5 次提交
    • M
      migration: fix analyze-migration.py script · 96e5c9bc
      Mark Cave-Ayland 提交于
      Commit 61964 "Add configuration section" broke the analyze-migration.py script
      which terminates due to the unrecognised section. Fix the script by parsing
      the contents of the configuration section directly into a new
      ConfigurationSection object (although nothing is done with it yet).
      Signed-off-by: NMark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
      Reviewed-by: Juan Quintela <quintela@redhat.com>al3
      Signed-off-by: Juan Quintela <quintela@redhat.com>al3
      96e5c9bc
    • L
      migration: code clean up · 6ad2a215
      Liang Li 提交于
      Just clean up code, no behavior change.
      Signed-off-by: NLiang Li <liang.z.li@intel.com>
      Reviewed-by: Juan Quintela <quintela@redhat.com>al3
      Reviewed-by: Amit Shah <amit.shah@redhat.com>al3
      Signed-off-by: Juan Quintela <quintela@redhat.com>al3
      6ad2a215
    • L
      migration: rename cancel to cleanup in SaveVMHandles · d1a8548c
      Liang Li 提交于
      'cleanup' seems more appropriate than 'cancel'.
      Signed-off-by: NLiang Li <liang.z.li@intel.com>
      Reviewed-by: Juan Quintela <quintela@redhat.com>al3
      Reviewed-by: Amit Shah <amit.shah@redhat.com>al3
      Signed-off-by: Juan Quintela <quintela@redhat.com>al3
      d1a8548c
    • L
      migration: rename qemu_savevm_state_cancel · ea7415fa
      Liang Li 提交于
      The function qemu_savevm_state_cancel is called after the migration
      in migration_thread, it seems strange to 'cancel' it after completion,
      rename it to qemu_savevm_state_cleanup looks better.
      Signed-off-by: NLiang Li <liang.z.li@intel.com>
      Reviewed-by: Juan Quintela <quintela@redhat.com>al3
      Reviewed-by: Amit Shah <amit.shah@redhat.com>al3
      Signed-off-by: Juan Quintela <quintela@redhat.com>al3
      ea7415fa
    • L
      migration: defer migration_end & blk_mig_cleanup · 94f5a437
      Liang Li 提交于
      Because of the patch 3ea3b7fa9af067982f34b of kvm, which introduces a
      lazy collapsing of small sptes into large sptes mechanism, now
      migration_end() is a time consuming operation because it calls
      memroy_global_dirty_log_stop(), which will trigger the dropping of small
      sptes operation and takes about dozens of milliseconds, so call
      migration_end() before all the vmsate data has already been transferred
      to the destination will prolong VM downtime. This operation should be
      deferred after all the data has been transferred to the destination.
      
      blk_mig_cleanup() can be deferred too.
      
      For a VM with 8G RAM, this patch can reduce the VM downtime about 30 ms.
      Signed-off-by: NLiang Li <liang.z.li@intel.com>
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Reviewed-by: Juan Quintela <quintela@redhat.com>al3
      Reviewed-by: Amit Shah <amit.shah@redhat.com>al3
      Signed-off-by: Juan Quintela <quintela@redhat.com>al3
      94f5a437
  4. 03 11月, 2015 26 次提交