Changes

When doing a [[live migration]] of a process from one host to another a common question is -- how to deal with the different IP address on the destination host. Although the correct answer would be -- use containers, moving a service onto different IP address might make sense. This article describes how to do it.

When doing a [[live migration]] of a process from one host to another a common question is -- how to deal with the different IP address on the destination host. Although the correct answer would be to use containers, moving a service onto different IP address might make sense. This article describes how to do it.

{{Note|This is not yet implemented in CRIU: [https://github.com/xemul/criu/issues/211]}}

{{Note|This is not yet implemented in CRIU: [https://github.com/checkpoint-restore/criu/issues/211]}}

== Problem ==

== Problem ==

=== Listening sockets ===

=== Listening sockets ===

If your server is bound to 0.0.0.0 (INADDR_ANY) then migration would "just work" there's no IP address that would mismatch. If your server is bound to some device, then you'll have to change the binding IP address. Right now this can be done by editing the [[images]], in particular, all PF_INET sockets sit in inetsk.img image and [[CRIT]] can be used to modify one.

If your server is bound to 0.0.0.0 (INADDR_ANY) then migration would "just work" there's no IP address that would mismatch. If your server is bound to some device, then you'll have to change the binding IP address. Right now this can be done by editing the [[images]], in particular, all PF_INET sockets sit in files.img image and [[CRIT]] can be used to modify one.

=== In-flight connections ===

=== In-flight connections ===