search for: vir_migrate_non_shared_inc

Displaying 4 results from an estimated 4 matches for "vir_migrate_non_shared_inc".

2017 Apr 28
1
Re: Live migration with non-shared ZFS volume
...me.qcow2'/> </disk> </disks> </domainsnapshot> This creates overlay qcow snapshot on top of my base ZFS volume 3. Transfer ZFS volume (with last snapshot) to remote host 4. Run live migration with setting XML from step 1 as DestXML and PersistXML parameter and with VIR_MIGRATE_NON_SHARED_INC flag This creates domain without snapshot on the remote host and migrates only data from qcow overlay and commits them to the ZFS base volume. What I don't like about this, is that I need to create and care about qcow image. The best solution for me would be to only create dirty block map in...
2017 Apr 04
2
Live migration with non-shared ZFS volume
...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.
2014 Nov 28
0
python migrateSetMaxSpeed not taking effect
...conn = libvirt.open('qemu:///system') domain_obj = conn.lookupByName(domain) dst='qemu+ssh://root@%s/system' % args.remote domain_obj.migrateSetMaxSpeed(40,0) new_dom = domain_obj.migrateToURI(dst,libvirt.VIR_MIGRATE_LIVE | libvirt.VIR_MIGRATE_PEER2PEER | libvirt.VIR_MIGRATE_NON_SHARED_INC | libvirt.VIR_MIGRATE_PERSIST_DEST | libvirt.VIR_MIGRATE_UNDEFINE_SOURCE, None, 0) conn.close() Also tried to specify bandwidth at migrateToUri- I still get 10 mib/s at any value... Thanks in advance!
2017 Apr 28
0
Re: Live migration with non-shared ZFS volume
...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 alr...