- 03 Aug, 2010 1 commit
-
-
Yoshiaki Tamura authored
Signed-off-by:
Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp> Signed-off-by:
Kevin Wolf <kwolf@redhat.com>
-
- 26 Jul, 2010 1 commit
-
-
Yoshiaki Tamura authored
Currently block_load() doesn't check return value of bdrv_write(), and even the destination weren't prepared to execute block migration, it proceeds and guest boots on the target. This patch fix this issue. Signed-off-by:
-
- 13 Jul, 2010 1 commit
-
-
Shahar Havivi authored
When there is no block driver associate with BlockDriverState bdrv_getlength returns -ENOMEDIUM that cause block migration to fail Signed-off-by:
Shahar Havivi <shaharh@redhat.com> Signed-off-by:
-
- 06 Jul, 2010 2 commits
-
-
Alex Williamson authored
When available, we'd like to be able to access the DeviceState when registering a savevm. For buses with a get_dev_path() function, this will allow us to create more unique savevm id strings. Signed-off-by:
Alex Williamson <alex.williamson@redhat.com> Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
-
Markus Armbruster authored
init_blk_migration_it() skips drives with type hint BDRV_TYPE_CDROM. The intention is to skip read-only drives. However, BDRV_TYPE_CDROM is only a hint. It is currently sufficent for read-only. But it's not necessary, and it may not remain sufficient. Use bdrv_is_read_only() instead. Signed-off-by:
Markus Armbruster <armbru@redhat.com> Signed-off-by:
-
- 23 Apr, 2010 1 commit
-
-
Stefan Hajnoczi authored
The bdrv_first linked list of BlockDriverStates is currently extern so that block migration can iterate the list. However, since there is already a bdrv_iterate() function there is no need to expose bdrv_first. Signed-off-by:
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> Signed-off-by:
-
- 09 Feb, 2010 3 commits
-
-
Liran Schour authored
Move to stage3 only when remaining work can be done below max downtime. Use qemu_get_clock_ns for measuring read performance. Signed-off-by:
Liran Schour <lirans@il.ibm.com> Signed-off-by:
-
Liran Schour authored
Start transfer dirty blocks during the iterative stage. That will reduce the time that the guest will be suspended Signed-off-by:
-
Liran Schour authored
blk_mig_save_bulked_block is never called with sync flag. Remove the sync flag. Calculate bulk completion during blk_mig_save_bulked_block. Remove unused constants. Signed-off-by:
-
- 06 Feb, 2010 1 commit
-
-
malc authored
dprintf is already claimed by POSIX[1], and on at least one system is implemented as a macro [1] http://www.opengroup.org/onlinepubs/9699919799/functions/dprintf.html Signed-off-by:
malc <av1474@comtv.ru>
-
- 03 Dec, 2009 18 commits
-
-
Jan Kiszka authored
No need to migrate emptiness (risking divide by zero later on). Signed-off-by:
Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by:
-
Jan Kiszka authored
Inject progress report in percentage into the block live stream. This can be read out and displayed easily on restore. Signed-off-by:
-
Jan Kiszka authored
Signed-off-by:
-
Jan Kiszka authored
Report progress of an outgoing live migration to the monitor instead of stdout. Signed-off-by:
-
Jan Kiszka authored
In order to allow proper progress reporting to the monitor that initiated the migration, forward the monitor reference through the migration layer down to SaveLiveStateHandler. Signed-off-by:
-
Jan Kiszka authored
So far progress reporting only works for the first block device. Fix this by keeping an overall sum of sectors to be migratated, calculating the sum of all processed sectors, and finally basing the progress display on those values. Signed-off-by:
-
Jan Kiszka authored
Introduce qemu_savevm_state_cancel and inject a stage -1 to cancel a live migration. This gives the involved subsystems a chance to clean up dynamically allocated resources. Namely, the block migration layer can now free its device descriptors and pending blocks. Signed-off-by:
-
Jan Kiszka authored
Signed-off-by:
-
Jan Kiszka authored
Based on the original patch by Pierre Riteau: Use a common blk_send function to transmit a block. Signed-off-by:
-
Jan Kiszka authored
Both functions share a lot of code, so make them one. Signed-off-by:
-
Jan Kiszka authored
We already save total_sectors in BlkMigDevState, let's use this value during the migration and avoid to recalculate it needlessly. Signed-off-by:
-
Jan Kiszka authored
In case we restart a migration, submitted, read_done, transferred, and print_completion need to be reinitialized to 0. Signed-off-by:
-
Jan Kiszka authored
Based on the original patch by Pierre Riteau. Signed-off-by:
-
Jan Kiszka authored
Signed-off-by:
-
Jan Kiszka authored
No need to push block_mig_state to the heap and, thus, establish an indirection. Signed-off-by:
-
Jan Kiszka authored
Move a potentially large buffer from stack to heap. Signed-off-by:
-
Jan Kiszka authored
Instead of duplicating the definition of constants or introducing trivial retrieval functions move the SECTOR constants into the public block API. This also obsoletes sector_per_block in BlkMigState. Signed-off-by:
-
Jan Kiszka authored
No functional changes. Signed-off-by:
-
- 17 Nov, 2009 2 commits
-
-
Blue Swirl authored
Signed-off-by:Blue Swirl <blauwirbel@gmail.com>
-
lirans@il.ibm.com authored
This patch introduces block migration called during live migration. Block are being copied to the destination in an async way. First the code will transfer the whole disk and then transfer all dirty blocks accumulted during the migration. Still need to improve transition from the iterative phase of migration to the end phase. For now transition will take place when all blocks transfered once, all the dirty blocks will be transfered during the end phase (guest is suspended). Changes from v4: - Global variabels moved to a global state structure allocated dynamically. - Minor coding style issues. - Poll block.c for tracking of dirty blocks instead of manage it here. Signed-off-by:
-
