qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [PULL 0/6] Migration fixes


From: Juan Quintela
Subject: [Qemu-devel] [PULL 0/6] Migration fixes
Date: Thu, 16 Mar 2017 10:01:35 +0100

Hi

This are this week fixes for Migration:
- fix calculation of dirty-pages-rate (it was being too optimistic)
- Make sure we can remove tls params for migration (Dan)
- Disable postcopy with shared memory (Dave)
- migration-block: Don't call blk_drain too much (Lidong)
- Fix failed iotests cases (QingFeng)

Please apply, Juan.

The following changes since commit 1883ff34b540daacae948f493b0ba525edf5f642:

  Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging 
(2017-03-15 18:44:05 +0000)

are available in the git repository at:

  git://github.com/juanquintela/qemu.git tags/migration/20170316

for you to fetch changes up to 8679638b0e231f97ad3456c681bf569ca7f7f6d5:

  postcopy: Check for shared memory (2017-03-16 09:02:26 +0100)

----------------------------------------------------------------
migration/next for 20170316

----------------------------------------------------------------
Chao Fan (1):
      Change the method to calculate dirty-pages-rate

Daniel P. Berrange (1):
      migration: use "" as the default for tls-creds/hostname

Dr. David Alan Gilbert (2):
      RAMBlocks: qemu_ram_is_shared
      postcopy: Check for shared memory

Lidong Chen (1):
      migration/block: Avoid invoking blk_drain too frequently

QingFeng Hao (1):
      vmstate: fix failed iotests case 68 and 91

 exec.c                    |  5 +++++
 include/exec/cpu-common.h |  1 +
 include/exec/ram_addr.h   |  5 ++++-
 migration/block.c         |  3 +++
 migration/migration.c     |  4 ++++
 migration/postcopy-ram.c  | 18 ++++++++++++++++++
 migration/ram.c           | 12 +++++-------
 migration/tls.c           |  2 +-
 migration/vmstate.c       |  8 ++++----
 qapi-schema.json          |  4 ++++
 10 files changed, 49 insertions(+), 13 deletions(-)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]