Re: [libvirt] vm live storage migration with snapshots

On 02/11/2015 10:08 AM, Edward Young wrote: [probably didn't need to cross-post to quite that wide of an audience, oh well] Are the snapshots based on shared storage, or local-only storage? If I understand your question correctly, you are starting with this situation: base <- mid <- active and want to make sure that on the destination, the guest still sees the same contents as 'active' on the source, whether or not the destination still sees a backing chain or just one file. Yes, but that may not be the fastest solution. That is, you would be going from: base <- mid <- active to base' where base' is the active image containing all the committed state, then migrate that file. If base is not shared, that means qemu has to migrate the entire disk state. And you also no longer have the external snapshots to revert to on the destination. Yes, that works too, and is probably faster, especially if you have out-of-band means for sharing read-only state between source and destination. In fact, if you can create yet another (temporary) external snapshot, but this time on shared storage, and have storage backends that let you instantly remap backing files to be visible into the destination, then it is as simple as: create a snapshot with shared storage destination base <- mid <- active(frozen) <- shared copy base, mid, and active to the destination live migrate using shared storage instead of doing storage migration block-commit shared back into active base <- mid <- active where the shared storage only needs to hold as much disk state as diverges during the time of the live migration. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org