Changes

When performing [[live migration]], CRIU puts image files with applications' memory on a storage user provides. If the images with applications' memory are too big, this will result in big delays, due to the need to copy this data several times. Other than this, in some situations it would be desirable to avoid using the storage at all not to increase the load on it. This article describes how one can do [[live migration]] without putting images on disk, step by steps.

When performing [[live migration]], CRIU puts image files with applications' memory on a storage user provides. If the images with applications' memory are too big, this will result in big delays, due to the need to copy this data several times. Other than this, in some situations it would be desirable to avoid using the storage at all not to increase the load on it. This article describes how one can do [[live migration]] without putting images on disk, step by step.

== The process ==

== The process ==

  dst# criu page-server --images-dir <dir> --port <port>

  dst# criu page-server --images-dir <dir> --port <port>

Now, page server will wait for incoming connections to write the applications memory to the <code><dir></code>. When doing [[iterative migration]], you can make page server to automatically drop duplicated pages by using <code>--auto-dedup</code> option. See the [[incremental dumps]] article for details.

Now, page server will wait for incoming connections to write the applications' memory to the <code><dir></code>. When doing [[iterative migration]], you can make page server to automatically drop duplicated pages by using <code>--auto-dedup</code> option. See the [[incremental dumps]] article for details.

=== criu dump ===

=== criu dump ===