search for: vir_migrate_non_shared_inc_commit

...ot supported: pre-creation of storage targets for incremental storage migration is not supported" My question is: Is it possible to do live migration with blockcommit operation? If not, would it be hard to implement? I imagine it like I would start migration with some special parameter (e.g. VIR_MIGRATE_NON_SHARED_INC_COMMIT) which would only migrate data from qcow snapshot to destination storage. This would ensure the disk consistency and avoid useless whole disk copy. Or do you have any other idea how to solve this? BR. Daniel Kucera.

...t from this it does exactly what you want, right? > > My question is: Is it possible to do live migration with blockcommit >> operation? If not, would it be hard to implement? >> >> I imagine it like I would start migration with some special parameter >> (e.g. >> VIR_MIGRATE_NON_SHARED_INC_COMMIT) which would only migrate data from >> qcow >> snapshot to destination storage. >> >> This would ensure the disk consistency and avoid useless whole disk copy. >> >> > What would be the difference compared to what you are doing now (plus a > block commit)?...

...not supported" > So apart from this it does exactly what you want, right? >My question is: Is it possible to do live migration with blockcommit >operation? If not, would it be hard to implement? > >I imagine it like I would start migration with some special parameter (e.g. >VIR_MIGRATE_NON_SHARED_INC_COMMIT) which would only migrate data from qcow >snapshot to destination storage. > >This would ensure the disk consistency and avoid useless whole disk copy. > What would be the difference compared to what you are doing now (plus a block commit)? VIR_MIGRATE_NON_SHARED_INC should already mi...