On Tue, Oct 9, 2012 at 9:36 AM, Grzegorz Dwornicki <gd1100@xxxxxxxxx> wrote: > I have a question to you guys. Is it possible to use code from live > migration of KVM VMs to migrate other process? As far as I can tell, no. most of the virtualization facililites of KVM are implemented in the kernel, but they're managed by a 'normal' process (sometimes called qemu-kvm, sometimes just kvm). Is this userspace process that implements it's own migration feature. to do that, one running qemu-kvm (proc A) instance connects with a just-started instance (proc B). proc A first sends all the configuration information, so B sets itself identically. then all RAM data is transferred (iteratively, to 'catch up' with the still-running VM). finally, proc A suspends the running VM, finishes the last modified RAM data and all the CPU state. now proc B is identical to A, and both are suspended, and then, proc B is unsuspended and notifies proc A, which just exits. if you want to do that for arbitrary 'normal' processes, you'd have to implement that in the kernel; but KVM doesn't do that. As Paolo mentions, there are other projects that do similar things. OpenVZ is one; LXC does it too. I'd start with LXC, since it's a standard part of the kernel (just like KVM), and supported by many common utilities. -- Javier -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
