Lazy migration - Revision history

Rppt: /* Lazy-pages Daemon */

2018-04-24T11:10:18Z

Lazy-pages Daemon

2018-04-17T18:57:47Z

Video: Update live demo with migration of memhog that demonstrates how the remote page faults slow down the running process.

2017-11-07T23:43:10Z

Using Lazy Migration

2017-08-18T13:39:36Z

2017-05-08T06:56:01Z

2015-02-20T18:26:39Z

2015-02-20T18:25:44Z

New page

[[Category:Plans]]
[[Category:Empty articles]]

@@ Line 19: / Line 19: @@
 The <code>lazy-pages</code> daemon is responsible for handling the task's page faults and injecting the memory pages into the task's address space. The <code>--page-server</code> option should be set so that <code>lazy-pages</code> daemon will connect to the '''src''' node. The <code>--address</code> and <code>--port</code> options should be used to define the IP address and port of the <code>dump</code> side.
-  [dst]# criu lazy-pages --page-server --address <src> --port <port>
+  [dst]# criu lazy-pages --images-dir <dir> --page-server --address <src> --port <port>
 === Restore ===

@@ Line 30: / Line 30: @@
 === Video ===
-To view an example video of using a lazy-pages, please go to https://asciinema.org/a/146427.
+To view an example video of using a lazy-pages, please go to https://asciinema.org/a/4QgtYPW9XtTngTyCX5Jsibqth
 == See also ==

← Older revision		Revision as of 23:43, 7 November 2017
Line 27:		Line 27:

	Note, that <code>lazy-pages</code> and <code>restore</code> must be run in the same working directory, or <code>--work-dir</code> option should be explicitly set.		Note, that <code>lazy-pages</code> and <code>restore</code> must be run in the same working directory, or <code>--work-dir</code> option should be explicitly set.
		+
		+	=== Video ===
		+
		+	To view an example video of using a lazy-pages, please go to https://asciinema.org/a/146427.

	== See also ==		== See also ==

@@ Line 1: / Line 1: @@
-[[Category:Plans]]
+== Overview ==
-[[Category:Empty articles]]
+Lazy, or [[wikipedia:Live_migration#Post-copy_memory_migration|post-copy memory migration]], allows to minimize application downtime. Unlike [[wikipedia:Live_migration#Pre-copy_memory_migration|pre-copy memory migration]], lazy migration does not copy the task's memory, but rather keeps the memory pages at the source node. Only the minimal task state required to start the application is copied to the destination node and the task is resumed there. When the task accesses missing memory pages, <code>criu</code> processes the page faults, transfers the required page from the source node and injects it into the running task address space.
 [[Category:Live migration]]