It's not taken as a dump file. It uses the standard libvirt migration
where it connects to the libvirt daemon on the destination and streams
the state.
You should be able to take state snapshots of the vm manually like
you'd normally do with libvirt on the hypervisor (I'm sure there's a
virsh comm
Can anyone explain or point me to some resources on how CloudStack performs
live migration of VMs with KVM? I need to know how the memory is taken as a
dump file and restored on another machine during migration. Can we
intercept and take the memory dump to store wherever we want? So that we
can res
