CRIU - User contributions [en]

Releasing

2025-05-23T01:21:00Z

Kir: /* Wiki */ more details

This is a reminder of steps needed to roll out a new release.

== Code ==
* Fix <code>Makefile.versions</code>
* Commit: <code>git commit -m "criu: Version $version"</code>
* Merge it like any other criu changes (create a github pr, get it approved, etc)
* Tag: <code>git tag -a v$version -m '$summary'</code>
* Push: <code>git push origin v$version</code>

== Wiki ==

You can use the following as a checklist.

* Make sure ''previous version'' is listed in [[Releases#Old versions]]
* Add release metadata:
** name to [[Template:Codename]]
** date to [[Template:Release date]]
* Add an image for the new version
* Create [[Download/criu/NEWVERSION]] (for example, see [[Download/criu/{{Last version}}]])
* Bump [[Template:Last version]]
* Add new version to [[Changelogs]]
* Fixup [[Release schedule]]
** remove new version from [[Release schedule#Future releases]]
** add previous version to [[Release schedule#Past releases]]

== Announces ==

* Send an announcement to the criu mailing list.

== Packages ==

* Update the CRIU packages in [https://build.opensuse.org/project/show/devel:tools:criu Open Build Service] and [https://launchpad.net/~criu Launchpad].

[[Category: development]]

Template:Changelog

2025-05-23T01:11:51Z

Kir: remove "v. " prefix from header

== {{{1}}} ==
{{:Download/criu/{{{1}}}}}
<br clear="both"/>

Changelogs

2025-05-23T01:09:59Z

Kir: add 4.1

This page contains all the changelogs for all the released CRIU versions. This is mostly useful for doing a search.

<div class="noautonum">__TOC__</div>

{{fe|Changelog|{{nln}}|4.1|4.0|3.19|3.18|3.17.1|3.17|3.16.1|3.16|3.15|3.14|3.13|3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0|2.12.1|2.12|2.11.1|2.11|2.10|2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0|1.8|1.7.2|1.7|1.6.1|1.6|1.5.2|1.5.1|1.5|1.4|1.3.1|1.3|1.3-rc2|1.3-rc1|1.2|1.1|1.1-rc2|1.1-rc1|1.0|0.8|0.7|0.6|0.5|0.4|0.3|0.2|0.1}}

Download/criu

2025-05-22T20:56:46Z

Kir: /* Old versions */ add 4.x

<div class="noautonum">__TOC__</div>

== Latest version ==

{{:Download/criu/{{Last version}}}}

== Old versions ==

=== 4.x ===

The following [[Download/criu/4.x|4.x]] releases were made:
* {{fe|criu|{{nln}}* |4.0}}

=== 3.x ===

The following [[Download/criu/3.x|3.x]] releases were made:

* {{fe|criu|{{nln}}* |3.19|3.18|3.17.1|3.17|3.16.1|3.16|3.15|3.14|3.13|3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0}}

=== 2.x ===

The following [[Download/criu/2.x|2.x]] releases were made:

* {{fe|criu|{{nln}}* |2.12.1|2.12|2.11.1|2.11|2.10|2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}

=== 1.x ===

The following [[Download/criu/1.x|1.x]] releases were made:

* {{fe|criu|{{nln}}* |1.8|1.7.2|1.7|1.6.1|1.6|1.5.2|1.5.1|1.5|1.4|1.3.1|1.3|1.3-rc2|1.3-rc1|1.2|1.1|1.1-rc2|1.1-rc1|1.0}}

=== 0.x ===

The following [[Download/criu/0.x|0.x]] releases were made:

* {{fe|criu|{{nln}}* |0.8|0.7|0.6|0.5|0.4|0.3|0.2|0.1}}

== See also ==

* [[Changelogs]] to see all the changelogs on a single page.

Download/criu/4.x

2025-05-22T20:56:22Z

Kir: created

This page lists older (4.x) CRIU releases. For latest release, see [[Download/criu]].

<div class="noautonum">__TOC__</div>

{{fe|Changelog|{{nln}}|4.0}}

== See also ==

* [[Download/criu]] for the latest release and archives
* [[Download/criu/3.x]] for 3.x releases
* [[Download/criu/2.x]] for 2.x releases
* [[Download/criu/1.x]] for 1.x releases
* [[Download/criu/0.x]] for pre-1.x releases

Download/criu

2025-01-15T23:21:25Z

Kir: add noautonum to TOC

<div class="noautonum">__TOC__</div>

== Latest version ==

{{:Download/criu/{{Last version}}}}

== Old versions ==

=== 3.x ===

The following [[Download/criu/3.x|3.x]] releases were made:

* {{fe|criu|{{nln}}* |3.19|3.18|3.17.1|3.17|3.16.1|3.16|3.15|3.14|3.13|3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0}}

=== 2.x ===

The following [[Download/criu/2.x|2.x]] releases were made:

* {{fe|criu|{{nln}}* |2.12.1|2.12|2.11.1|2.11|2.10|2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}

=== 1.x ===

The following [[Download/criu/1.x|1.x]] releases were made:

* {{fe|criu|{{nln}}* |1.8|1.7.2|1.7|1.6.1|1.6|1.5.2|1.5.1|1.5|1.4|1.3.1|1.3|1.3-rc2|1.3-rc1|1.2|1.1|1.1-rc2|1.1-rc1|1.0}}

=== 0.x ===

The following [[Download/criu/0.x|0.x]] releases were made:

* {{fe|criu|{{nln}}* |0.8|0.7|0.6|0.5|0.4|0.3|0.2|0.1}}

== See also ==

* [[Changelogs]] to see all the changelogs on a single page.

Changelogs

2025-01-15T23:10:04Z

Kir: added missing 3.16.1 release

This page contains all the changelogs for all the released CRIU versions. This is mostly useful for doing a search.

<div class="noautonum">__TOC__</div>

{{fe|Changelog|{{nln}}|4.0|3.19|3.18|3.17.1|3.17|3.16.1|3.16|3.15|3.14|3.13|3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0|2.12.1|2.12|2.11.1|2.11|2.10|2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0|1.8|1.7.2|1.7|1.6.1|1.6|1.5.2|1.5.1|1.5|1.4|1.3.1|1.3|1.3-rc2|1.3-rc1|1.2|1.1|1.1-rc2|1.1-rc1|1.0|0.8|0.7|0.6|0.5|0.4|0.3|0.2|0.1}}

Download/criu/3.x

2025-01-15T23:06:58Z

Kir: ffix

This page lists older (3.x) CRIU releases. For latest release, see [[Download/criu]].

With 3.x, we've finally split [[Compel]] from the rest of the CRIU and also added support for 32-bit tasks on x86-64 platform.

<div class="noautonum">__TOC__</div>

{{fe|Changelog|{{nln}}|3.19|3.18|3.17.1|3.17|3.16.1|3.16|3.15|3.14|3.13|3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0}}

== See also ==

* [[Download/criu]] for the latest release and archives
* [[Download/criu/2.x]] for 2.x releases
* [[Download/criu/1.x]] for 1.x releases
* [[Download/criu/0.x]] for pre-1.x releases

Download/criu/3.x

2025-01-15T23:06:33Z

Kir: Add missing 3.x releases

This page lists older (3.x) CRIU releases. For latest release, see [[Download/criu]].

With 3.x, we've finally split [[Compel]] from the rest of the CRIU and also added support for 32-bit tasks on x86-64 platform.

<div class="noautonum">__TOC__</div>

* {{fe|Changelog|{{nln}}|3.19|3.18|3.17.1|3.17|3.16.1|3.16|3.15|3.14|3.13|3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0}}

== See also ==

* [[Download/criu]] for the latest release and archives
* [[Download/criu/2.x]] for 2.x releases
* [[Download/criu/1.x]] for 1.x releases
* [[Download/criu/0.x]] for pre-1.x releases

Download/criu

2025-01-15T23:05:14Z

Kir: /* 3.x */ added all missing 3.x releases

== Latest version ==

{{:Download/criu/{{Last version}}}}

== Old versions ==

=== 3.x ===

The following [[Download/criu/3.x|3.x]] releases were made:

* {{fe|criu|{{nln}}* |3.19|3.18|3.17.1|3.17|3.16.1|3.16|3.15|3.14|3.13|3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0}}

=== 2.x ===

The following [[Download/criu/2.x|2.x]] releases were made:

* {{fe|criu|{{nln}}* |2.12.1|2.12|2.11.1|2.11|2.10|2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}

=== 1.x ===

The following [[Download/criu/1.x|1.x]] releases were made:

* {{fe|criu|{{nln}}* |1.8|1.7.2|1.7|1.6.1|1.6|1.5.2|1.5.1|1.5|1.4|1.3.1|1.3|1.3-rc2|1.3-rc1|1.2|1.1|1.1-rc2|1.1-rc1|1.0}}

=== 0.x ===

The following [[Download/criu/0.x|0.x]] releases were made:

* {{fe|criu|{{nln}}* |0.8|0.7|0.6|0.5|0.4|0.3|0.2|0.1}}

== See also ==

* [[Changelogs]] to see all the changelogs on a single page.

Download/criu/3.18

2023-10-19T22:24:49Z

Kir: rm extra vertical whitespace

[[Image:3.18.jpg|400px|right]]
{{Release|3.18}}

=== New features ===
* Allow CRIU to be used as non-root
* Add SIGTSTP support
* Add opt to skip file r/w/x check on restore

=== Bugfixes ===
* Many fixes here and there

=== Improvements ===
* cgroup2: Dump cgroup controllers of every threads in a process
* save IP_FREEBIND option for SOCK_RAW sockets also
* support IP_PKTINFO and IPV6_RECVPKTINFO options
* Implement hw breakpoint for arm64 platform
* Set only used XFEATURE_* in xstate_bv
* Checkpoint and restore some global properties
* A checkpoint optimization for highly sparse ghost files (--ghost-fiemap)

Releasing

2023-04-19T16:08:26Z

Kir:

This is a reminder of steps needed to roll out a new release.

== Code ==
* Fix <code>Makefile.versions</code>
* Commit: <code>git commit -m "criu: Version $version"</code>
* Merge it like any other criu changes (create a github pr, get it approved, etc)
* Tag: <code>git tag -a v$version -m '$summary'</code>
* Push: <code>git push origin v$version</code>

== Wiki ==

* Make sure ''previous version'' is listed in [[Releases#Old versions]]
* Add release metadata:
** name to [[Template:Codename]]
** date to [[Template:Release date]]
* Create [[Download/criu/VERSION]]
* Bump [[Template:Last version]]
* Add new version to [[Changelogs]]
* Fixup [[Release schedule]]
** remove new version from [[Release schedule#Future releases]]
** add previous version to [[Release schedule#Past releases]]

== Announces ==

* Send an announcement to the criu mailing list.

[[Category: development]]

Template:Codename

2022-07-12T00:22:59Z

Kir: added 3.17.1 codename (same as 3.17)

<includeonly>{{#switch: v{{{1}}}
| v2.1 = Steel Lapwing
| v2.2 = Carbon Nightingale
| v2.3 = Wooden Duck
| v2.4 = Marble Lark
| v2.5 = Concrete Oriole
| v2.6 = Paper Crane
| v2.7 = Rubber Owl
| v2.8 = Bronze Siskin
| v2.9 = Silk Tit
| v2.10 = Brass Waxwing
| v2.11 = Acrylic Bullfinch
| v2.12 = Vulcanite Rook
| v3.0 = Basalt Wagtail
| v3.1 = Graphene Swift
| v3.2 = Tin Hoopoe
| v3.3 = Crystal Pelican
| v3.4 = Cobalt Swan
| v3.5 = Clay Jay
| v3.6 = Alabaster Finch
| v3.7 = Vinyl Magpie
| v3.8 = Snow Bunting
| v3.8.1 = Snow Bunting
| v3.9 = Sand Martin
| v3.10 = Granite Eagle
| v3.11 = Glass Flamingo
| v3.12 = Ice Penguin
| v3.13 = Silicon Willet
| v3.14 = Platinum Peacock
| v3.15 = Titanium Falcon
| v3.16 = Petrified Puffin
| v3.16.1 = Petrified Puffin
| v3.17 = Radiant Redstart
| v3.17.1 = Radiant Redstart
| 
}}</includeonly><noinclude>

This template is used to get the codename of a specified release. If there is no codename, empty string is produced.

== Usage ==

<pre><nowiki>{{Codename|VERSION}}</nowiki></pre>

== Examples ==

{| class="wikitable"
! Markup
! Result
|-
| <pre><nowiki>{{Codename|3.3}}</nowiki></pre>
| {{Codename|3.3}}
|-
| <pre><nowiki>{{Codename|2.1}}</nowiki></pre>
| {{Codename|2.1}}
|-
| <pre><nowiki>{{Codename|2.0}}</nowiki></pre>
| {{Codename|2.0}}
|}

== See also ==

* [[Release schedule]] for future codenames
* [[Template:Release date]]
* [[Template:criu]]
* [[Template:Release]]
* [[Template:Latest release]]

</noinclude>

Template:Release date

2022-07-12T00:18:39Z

Kir: added v to newest entries

<includeonly>{{#switch: v{{{1}}}
| v3.17.1 = 23 Jun 2022
| v3.17 = 5 May 2022
| v3.16.1 = 14 Oct 2021
| v3.16 = 22 Sep 2021
| v3.15 = 03 Nov 2020
| v3.14 = 29 Apr 2020
| v3.13 = 11 Sep 2019
| v3.12 = 25 Apr 2019
| v3.11 = 06 Nov 2018
| v3.10 = 10 Jul 2018
| v3.9 = 21 May 2018
| v3.8.1 = 29 Mar 2018
| v3.8 = 13 Mar 2018
| v3.7 = 19 Dec 2017
| v3.6 = 23 Oct 2017
| v3.5 = 27 Sep 2017
| v3.4 = 21 Aug 2017
| v3.3 = 18 Jul 2017
| v3.2.1 = 28 Jun 2017
| v3.2 = 19 Jun 2017
| v3.1 = 22 May 2017
| v3.0 = 24 Apr 2017
| v2.12.1 = 27 Mar 2017
| v2.12 = 8 Mar 2017
| v2.11.1 = 17 Feb 2017
| v2.11 = 13 Feb 2017
| v2.10 = 16 Jan 2017
| v2.9 = 12 Dec 2016
| v2.8 = 14 Nov 2016
| v2.7 = 17 Oct 2016
| v2.6 = 12 Sep 2016
| v2.5 = 15 Aug 2016
| v2.4 = 11 Jul 2016
| v2.3 = 14 Jun 2016
| v2.2 = 16 May 2016
| v2.1 = 11 Apr 2016
| v2.0 = 7 Mar 2016
| v1.8 = 7 Dec 2015
| v1.7.2 = 28 Oct 2015
| v1.7 = 7 Sep 2015
| v1.6.1 = 12 Aug 2015
| v1.6 = 1 Jun 2015
| v1.5.2 = 28 Apr 2015
| v1.5.1 = 31 Mar 2015
| v1.5 = 2 Mar 2015
| v1.4 = 1 Dec 2014
| v1.3.1 = 12 Sep 2014
| v1.3 = 1 Sep 2014
| v1.3-rc2 = 18 Jun 2014
| v1.3-rc1 = 25 Apr 2014
| v1.2 = 26 Feb 2014
| v1.1 = 28 Jan 2014
| v1.1-rc2 = 20 Jan 2014
| v1.1-rc1 = 30 Dec 2013
| v1.0 = 25 Nov 2013
| v0.8 = 18 Oct 2013
| v0.7 = 3 Sep 2013
| v0.6 = 1 Jul 2013
| v0.5 = 30 Apr 2013
| v0.4 = 20 Feb 2013
| v0.3 = 11 Dec 2012
| v0.2 = 20 Sep 2012
| v0.1 = 23 Jul 2012
| 
}}</includeonly><noinclude>

This template is used to get the date of a specified release.

== Usage ==

<pre><nowiki>{{Release date|VERSION}}</nowiki></pre>

Examples:

{| class="wikitable"
! Markup
! Result
|-
| <pre><nowiki>{{Release date|2.10}}</nowiki></pre>
| {{Release date|2.10}}
|-
| <pre><nowiki>{{Release date|2.1}}</nowiki></pre>
| {{Release date|2.1}}
|-
| <pre><nowiki>{{Release date|1.3-rc1}}</nowiki></pre>
| {{Release date|1.3-rc1}}
|-
| <pre><nowiki>{{Release date|0.1}}</nowiki></pre>
| {{Release date|0.1}}
|}

== See also ==
* [[Template:Codename]]
* [[Template:Release]]

</noinclude>

Mount-v2

2022-04-27T05:04:25Z

Kir: /* Links */ make a list

Mount-v2 CRIU algorithm

== Introduction ==

After we've merged MOVE_MOUNT_SET_GROUP feature to mainstream linux v5.15 [https://github.com/torvalds/linux/commit/9ffb14ef61bab83fa818736bf3e7e6b6e182e8e2 torvalds/linux@9ffb14e] now we can use it to restore sharing groups of mounts without the need to care about inheriting those groups when create mounts, we can just set sharing groups at later stage and before that construct mount trees with private mounts.

Restoring propagation right with conservative approach of both creating mounts and inheriting propagation groups looks like mission impossible task for us due to many problems:

* Criu knows nothing about the initial history or order of mount tree creation;
* Propagation can create tons of mounts;
* Propagation may change parent mounts for existing mount tree;
* "Mount trap" - propagation may cover initial mount;
* "Non-uniform" propagation - there are different tricks with mount order and temporary children-"lock" mounts, which create mount trees which can't be restored without those tricks;
* "Cross-namespace" sharing groups creation need to be ordered with mount namespace creation right;
* Sharing groups vs mount tree order inversion can be very complex to restore and require multiple auxiliary. (see example below)

See my talks about it on Linux Plumbers Conference:
* [https://www.linuxplumbersconf.org/event/7/contributions/640/ CRIU mounts migration: problems and solutions]
* [https://linuxplumbersconf.org/event/11/contributions/923/ Mount-v2 CRIU migration engine: status update]

And here is the example of order inversion where multiple temporary mounts needed to achieve the result:
[[File:Mounts-inverse-order-example.gif|none|link=|Mounts-inverse-order-example.gif]]

== Mount-v2 description ==

New mount-v2 algorithm is integrated deeply in the original one, so that dumping of mounts is done exactly the same for original mount engine and new one. So mount-v2 series has preparatory steps related to bindmount detection, external mounts detection and helper mounts handling to make the original mount code more robust, to make it easier to reuse it in mount-v2.

==== Plain mountpoints ====

One of main differences of mount-v2 comparing to original is that mounts are initially created "plain", for instance if we had '''MOUNT''' with '''mnt_id=1000''' and '''ns_mountpoint="/mount/point/path"''', original mount engine would originally mount this '''MOUNT''' in the mount tree to '''<criu_root_yard>/<mntns>/mount/point/path''' so that if this mount had '''PARENT''' mount with '''mnt_id=999''' and '''ns_mountpoint="/mount/point"''' corresponding mount for '''PARENT''' would be created in '''<criu_root_yard>/<mntns>/mount/point''' thus restoring parent-child relationship between them initially. For mount-v2 '''MOUNT''' would be first mounted to '''<criu_root_yard>/mnt-1000''' and '''PARENT''' would be mounted to '''<criu_root_yard>/mnt-999''' so that on the first stage we only create mounts and then on separate second stage handle the tree assembling separately. This way we can have useful heuristics like on the second stage we can create overmounts after mounts they overmount, and on the first stage we can create external mounts before their bindmounts and these two do not clinch with each other.

But it is not so simple actually because we do not want to rewrite all the code for instance for restoring mount content or restoring ghost and remap files, which used mountpoint paths in "tree" format. So in all places where it does not matter (where we do not access <criu_root_yard>/<mntns>/... paths) we switched from using mount_info->mountpoint to mount_info->ns_mountpoint and in all places where we actually needed "tree" format paths we replace them with service_mountpoint() helper which would return "tree" paths for original mount engine and "plain" paths for mount-v2. This way we can safely switch from one to another.

==== Resolving sharing groups ====

Just after reading mounts from images in read_mnt_ns_img() when mount-v2 is enabled we have an additional step to collect sharing group information from mounts and turn it to sharing groups forest graph (resolve_shared_mounts_v2). First, we just walk over all mounts and create sharing group for each mount with unique shared_id + master_id pair, also we sew all mounts to corresponding sharing group with same id pair. Second, we walk over all sharing groups which has non-zero master_id and lookup the corresponding parent sharing groups and connect them with a tree.

There is also a case when master_id is non-zero but there is no corresponding parent sharing group, this means that outside of dumped container there is mount with matching shared_id - external slavery detected. For this case we just collect sibling sharing groups in list with empty parent link. Also we detect source path from which the master_id would be inherited either from some mountpoint-external mount or from root container mount.

==== Actual restore of mounts ====

Actual restore of mounts in original mount engine starts with prepare_mnt_ns() function, when mount-v2 is enabled we pass controll from it to prepare_mnt_ns_v2() instead. It consists of several stages:

1) We pre-create mount namespaces for each restored mount namespace in pre_create_mount_namespaces(). These namespaces appear almost empty: they contain tmpfs as their root, they have root yard path created in it with another tmpfs mounted in it, and"namespace" path for assembling tree of mounts in it created in corresponding subdirectory of root yard mount. Surely we also save nsfs fds to each mount namespace to be able to reenter them later.

2) In populate_mnt_ns_v2() we reuse mnt_tree_for_each() walk over mount tree from original mount engine and so we walk mounts in tree order with addition of temporary skipping mounts and their descendants with can_mount_now_v2() in case they depend from other mounts, restarting the walk for them later. The can_mount_now_v2() is basically skipping mounts which should be restored as bindmounts but their source is not ready yet, this is true for bindmounts of root, external or plugin mounts or non-fsroot mounts.

3) In the mentioned walk over mounts forest in do_mount_one_v2() we determine if the newly created mount is directory one or a file one in detect_is_dir(), we just open its mountpoint path relative to parent "plain" mountpoint and do stat. That's why it is important to use mnt_tree_for_each() as it insures that parent is already "plain" mounted.

4) In the mentioned walk over mounts forest in do_mount_one_v2() we create "plain" mountpoint for a new mount, empty file or directory based on the previous step.

5) In the mentioned walk over mounts forest in do_mount_one_v2() we actually create new mount, either we create completely new mount or device-external in do_new_mount_v2() if it's supported, or bind container root mount in do_mount_root_v2() from the still visible host mount tree, or bind mountpoint-external mount in do_bind_mount_v2() and similarly bind any mount for which superblock is already created by other mount beforehand and we can just bind it in do_bind_mount_v2(). These functions act similar to ones in original mount engine but simplified as they don't need to care about inheriting sharing groups.

6) The do_bind_mount_v2() is improved to do bindmount via open_tree() + move_mount() with flags allowing not to traverse symlinks or autofs mounts.

7) Also we cross-namespace bindmount the newly created mount to restored mount namespace to the same "plain" mountpoint in do_mount_in_right_mntns(). So that we initially have a mount which would be visible after restore, this would be required in future to be able to restore bindmounted unix sockets on the right mount.

8) Now after the walk we don't plan to do bindmounts anymore so we set unbindable flags on mounts.

9) Next we assemble mount trees in each restored mount namespace in assemble_mount_namespaces() by again reusing move_mount_to_tree() to have tree order of moving mounts into proper places in mount tree. Also we open fds on the mountpoint: one mp_fd_id before moving and another mnt_fd_id after, so that we can access files on each mount later from final mntns via those fds.

10) Finally we do restore sharing groups on the assembled mount forest in restore_mount_sharing_options(). It walks each root sharing group and their descendants with dfs tree walk. It creates sharing for the first mount in the sharing group and then sets the same sharing on all other mounts in this group.

Sharing creation for first mount is two step:

a) If mount has master_id we either copy shared_id from parent sharing group or from external source and then make mount slave thus converting it to right master_id.
b) Next if mount has shared_id we just make us shared, creating right shared_id.

We need to use userns_call() for MOVE_MOUNT_SET_GROUP to have all right permissions for copying sharing (move_mount_set_group()). Also we need to resolve external paths given by user to their actual mountpoint, we do so with openat2(RESOLVE_NO_XDEV) in resolve_mountpoint, this also only works from userns_call().

11) We remove sources of deleted mounts making them actually deleted (from "service" mount namespace), as moving deleted mounts is not allowed and just to simplify things we do it at the last step.

==== Links ====

* "Virtuozzo" (original) version (using non-mainstream kernel interface): [[Mounts-v2-Virtuozzo|Mounts-v2-Virtuozzo]] It actually has cool features we don't have in mainstream yet, for instance - nested pidns proc handling, this feature requires nested pidns support beforehand.

* MOVE_MOUNT_SET_GROUP kernel feature: [https://github.com/torvalds/linux/commit/9ffb14ef61bab83fa818736bf3e7e6b6e182e8e2 torvalds/linux@9ffb14e]

* Mount-v2 PR to criu: [https://github.com/checkpoint-restore/criu/pull/1721 #1721]

[[Category: Under the hood]]

Template:Codename

2022-04-27T04:59:08Z

Kir: Add a name for 3.8.1

<includeonly>{{#switch: v{{{1}}}
| v2.1 = Steel Lapwing
| v2.2 = Carbon Nightingale
| v2.3 = Wooden Duck
| v2.4 = Marble Lark
| v2.5 = Concrete Oriole
| v2.6 = Paper Crane
| v2.7 = Rubber Owl
| v2.8 = Bronze Siskin
| v2.9 = Silk Tit
| v2.10 = Brass Waxwing
| v2.11 = Acrylic Bullfinch
| v2.12 = Vulcanite Rook
| v3.0 = Basalt Wagtail
| v3.1 = Graphene Swift
| v3.2 = Tin Hoopoe
| v3.3 = Crystal Pelican
| v3.4 = Cobalt Swan
| v3.5 = Clay Jay
| v3.6 = Alabaster Finch
| v3.7 = Vinyl Magpie
| v3.8 = Snow Bunting
| v3.8.1 = Snow Bunting
| v3.9 = Sand Martin
| v3.10 = Granite Eagle
| v3.11 = Glass Flamingo
| v3.12 = Ice Penguin
| v3.13 = Silicon Willet
| v3.14 = Platinum Peacock
| v3.15 = Titanium Falcon
| v3.16 = Petrified Puffin
| v3.16.1 = Petrified Puffin
| v3.17 = Radiant Redstart
| 
}}</includeonly><noinclude>

This template is used to get the codename of a specified release. If there is no codename, empty string is produced.

== Usage ==

<pre><nowiki>{{Codename|VERSION}}</nowiki></pre>

== Examples ==

{| class="wikitable"
! Markup
! Result
|-
| <pre><nowiki>{{Codename|3.3}}</nowiki></pre>
| {{Codename|3.3}}
|-
| <pre><nowiki>{{Codename|2.1}}</nowiki></pre>
| {{Codename|2.1}}
|-
| <pre><nowiki>{{Codename|2.0}}</nowiki></pre>
| {{Codename|2.0}}
|}

== See also ==

* [[Release schedule]] for future codenames
* [[Template:Release date]]
* [[Template:criu]]
* [[Template:Release]]
* [[Template:Latest release]]

</noinclude>

Download/criu

2022-04-27T04:57:31Z

Kir: added 3.16 to past releases

== Latest version ==

{{:Download/criu/{{Last version}}}}

== Old versions ==

=== 3.x ===

The following [[Download/criu/3.x|3.x]] releases were made:

* {{fe|criu|{{nln}}* |3.16|3.15|3.14|3.13|3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0}}

=== 2.x ===

The following [[Download/criu/2.x|2.x]] releases were made:

* {{fe|criu|{{nln}}* |2.12.1|2.12|2.11.1|2.11|2.10|2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}

=== 1.x ===

The following [[Download/criu/1.x|1.x]] releases were made:

* {{fe|criu|{{nln}}* |1.8|1.7.2|1.7|1.6.1|1.6|1.5.2|1.5.1|1.5|1.4|1.3.1|1.3|1.3-rc2|1.3-rc1|1.2|1.1|1.1-rc2|1.1-rc1|1.0}}

=== 0.x ===

The following [[Download/criu/0.x|0.x]] releases were made:

* {{fe|criu|{{nln}}* |0.8|0.7|0.6|0.5|0.4|0.3|0.2|0.1}}

== See also ==

* [[Changelogs]] to see all the changelogs on a single page.

Template:Dl

2021-09-23T16:41:54Z

Kir: fixed link to criu 2.x

<includeonly>{{#ifexpr: {{#sub:{{{1}}}|0|1}} >= 3 | [[github:checkpoint-restore/criu/archive/v{{{1}}}/criu-{{{1}}}.tar.gz | criu-{{{1}}}.tar.gz]] | [[dl:criu/criu-{{{1}}}.tar.bz2|criu-{{{1}}}.tar.bz2]] }}</includeonly><noinclude>

This produces a download link for a given version.

* for releases < 3, it links to download.openvz.org (interwiki <code>dl:</code>), and uses tar.bz2.
* for releases >= 3, it links to github.org (interwiki <code>github:</code>), and uses tar.gz.

== Examples ==

{| class="wikitable"
! Wiki code !! Result
|-
| <code><nowiki>{{Dl|2.3}}</nowiki></code> || {{Dl|2.3}}
|-
| <code><nowiki>{{Dl|3.14}}</nowiki></code> || {{Dl|3.14}}
|-
|}
</noinclude>

Template:Dl

2021-09-23T16:40:54Z

Kir: fixed to use github.com/checkpoint-restore/criu/archive/vXXX/criu-XXX.tar.gz instead of codeload. This fixes the file name when using wget.

<includeonly>{{#ifexpr: {{#sub:{{{1}}}|0|1}} >= 3 | [[github:checkpoint-restore/criu/archive/v{{{1}}}/criu-{{{1}}}.tar.gz | criu-{{{1}}}.tar.gz]] | [[dl:criu/criu-{{{1}}}.tar.bz2|criu-{{{1}}}.tar.bz2]] }}</includeonly><noinclude>

This produces a download link for a given version.

* for releases < 3, it links to download.openvz.org (interwiki <code>dl:</code>), and uses tar.bz2.
* for releases >= 3, it links to github.org (interwiki <code>github:</code>), and uses tar.gz.

== Examples ==

{| class="wikitable"
! Wiki code !! Result
|-
| <code><nowiki>{{Dl|2.3.1}}</nowiki></code> || {{Dl|2.3.1}}
|-
| <code><nowiki>{{Dl|3.14}}</nowiki></code> || {{Dl|3.14}}
|-
|}
</noinclude>

Template:Git release

2021-09-22T22:02:17Z

Kir: fix double slash

[[github:checkpoint-restore/criu/releases/tag/{{{1}}}|{{{1}}}]]

Template:Dl

2021-09-22T21:59:16Z

Kir: use codeload.github.com for 3.x; add documentation

<includeonly>{{#ifexpr: {{#sub:{{{1}}}|0|1}} >= 3 | [[gh-codeload:checkpoint-restore/criu/tar.gz/refs/tags/v{{{1}}} | criu-{{{1}}}.tar.gz]] | [[dl:criu/criu-{{{1}}}.tar.bz2|criu-{{{1}}}.tar.bz2]] }}</includeonly><noinclude>

This produces a download link for a given version.

* for releases < 3, it links to download.openvz.org (interwiki <code>dl:</code>), and uses tar.bz2.
* for releases >= 3, it links to codeload.github.org (interwiki <code>gh-codeload:</code>), and uses tar.gz.

== Examples ==

{| class="wikitable"
! Wiki code !! Result
|-
| <code><nowiki>{{Dl2|2.3.1}}</nowiki></code> || {{Dl2|2.3.1}}
|-
| <code><nowiki>{{Dl2|3.14}}</nowiki></code> || {{Dl2|3.14}}
|-
|}
</noinclude>

Template:Dl2

2021-09-22T21:58:23Z

Kir: polish; improve docs

Template:Dl2

2021-09-22T21:55:08Z

Kir: use interwiki prefix

{{#ifexpr: {{#sub:{{{1}}}|0|1}} >= 3 | [[gh-codeload:checkpoint-restore/criu/tar.gz/refs/tags/v{{{1}}} | criu-{{{1}}}.tar.gz]] | [[dl:criu/criu-{{{1}}}.tar.bz2|criu-{{{1}}}.tar.bz2]] }}<noinclude>

This produces a download link for a given version.

== Examples ==

{| class="wikitable"
! Wiki code !! Result
|-
| <code><nowiki>{{Dl2|2.3.1}}</nowiki></code> || {{Dl2|2.3.1}}
|-
| <code><nowiki>{{Dl2|3.14}}</nowiki></code> || {{Dl2|3.14}}
|-
|}
</noinclude>

Template:Dl2

2021-09-22T21:50:43Z

Kir: fix

{{#ifexpr: {{#sub:{{{1}}}|0|1}} >= 3 | [[https://codeload.github.com/checkpoint-restore/criu/tar.gz/refs/tags/v{{{1}}}{{|}}criu-{{{1}}}.tar.gz]] | [[dl:criu/criu-{{{1}}}.tar.bz2|criu-{{{1}}}.tar.bz2]] }}<noinclude>

This produces a download link for a given version.

== Examples ==

{| class="wikitable"
! Wiki code !! Result
|-
| <code><nowiki>{{Dl2|2.3.1}}</nowiki></code> || {{Dl2|2.3.1}}
|-
| <code><nowiki>{{Dl2|3.14}}</nowiki></code> || {{Dl2|3.14}}
|-
|}
</noinclude>

Template:Dl2

2021-09-22T21:48:50Z

Kir: redirect 3.x downloads to github

{{#ifexpr: {{#sub:{{{1}}}|0|1}} >= 3 | [[https://codeload.github.com/checkpoint-restore/criu/tar.gz/refs/tags/v{{{1}}}|criu-{{{1}}}.tar.gz]] | [[dl:criu/criu-{{{1}}}.tar.bz2|criu-{{{1}}}.tar.bz2]] }}<noinclude>

This produces a download link for a given version.

== Examples ==

{| class="wikitable"
! Wiki code !! Result
|-
| <code><nowiki>{{Dl2|2.3.1}}</nowiki></code> || {{Dl2|2.3.1}}
|-
| <code><nowiki>{{Dl2|3.14}}</nowiki></code> || {{Dl2|3.14}}
|-
|}
</noinclude>

API compliance

2021-08-08T15:42:10Z

Kir: nit

This page brings together 3 APIs we have

== Actions ==
{| class="wikitable sortable"
! [[Usage|CLI]]
! [[RPC]]
! [[C_API|C library]]
! comment
|-
| dump || CRIU_REQ_TYPE__DUMP || criu_dump ||
|-
| pre-dump || CRIU_REQ_TYPE__PRE_DUMP || criu_dump_iters ||
|-
| restore || CRIU_REQ_TYPE__RESTORE || criu_restore, criu_restore_child ||
|-
| show || || || Deprecated. The [[CRIT]] tool should be used instead
|-
| check || CRIU_REQ_TYPE__CHECK || criu_check ||
|-
| cpuinfo dump || CRIU_REQ_TYPE__CPUINFO_DUMP || ||
|-
| cpuinfo check || CRIU_REQ_TYPE__CPUINFO_CHECK || ||
|-
| exec || || ||
|-
| page-server || CRIU_REQ_TYPE__PAGE_SERVER || ||
|-
| service || || ||
|-
| dedup || || ||
|}

== Options ==
{| class="wikitable sortable"
! [[Usage|CLI]]
! [[RPC]]
! [[C_API|C library]]
! comment
|-
|"tree" || pid || criu_set_pid ||
|-
|"leave-stopped" || || ||
|-
|"leave-running" || leave_running || criu_set_leave_running ||
|-
|"restore-detached" || || || tasks always restore detached in RPC/lib
|-
|"restore-sibling" || rst_sibling || || For [[RPC]] -- in swrk mode only
|-
|"daemon" || || || only for page server in RPC/lib
|-
|"images-dir" || images_dir_fd || criu_set_images_dir_fd ||
|-
|"work-dir" || work_dir_fd || criu_set_work_dir_fd ||
|-
|"log-file" || log_file || criu_set_log_file ||
|-
|"root" || root || criu_set_root ||
|-
|"ext-unix-sk" || ext_unix_sk || criu_set_ext_unix_sk ||
|-
|"tcp-established" || tcp_established || criu_set_tcp_established ||
|-
|"log-pid" || || ||
|-
|"evasive-devices" || evasive_devices || criu_set_evasive_devices ||
|-
|"veth-pair" || veths || criu_add_veth_pair ||
|-
|"action-script" || notify_scripts || criu_set_notify_cb || see article about [[action scripts]]
|-
|"link-remap" || link_remap || criu_set_link_remap ||
|-
|"shell-job" || shell_job || criu_set_shell_job ||
|-
|"file-locks" || file_locks || criu_set_file_locks ||
|-
|"page-server" || ps || ||
|-
|"address" || ps.address || ||
|-
|"port" || ps.port || ||
|-
|"pidfile" || ps.pid || || page-server pid returned for RPC
|-
|"prev-images-dir" || parent_img || criu_set_parent_images ||
|-
|"ms" || || || "Check" only
|-
|"feature" || || || "Check" only
|-
|"track-mem" || track_mem || criu_set_track_mem ||
|-
|"auto-dedup" || auto_dedup || criu_set_auto_dedup ||
|-
|"libdir" || || || not clear how to do it in RPC
|-
|"cpu-cap" || cpu_cap || criu_set_cpu_cap ||
|-
|"force-irmap" || force_irmap || criu_set_force_irmap ||
|-
|"exec-cmd" || exec_cmd || criu_set_exec_cmd ||
|-
|"manage-cgroups" || manage_cgroups || criu_set_manage_cgroups ||
|-
|"cgroup-root" || cg_root || criu_add_cg_root ||
|-
|"inherit-fd" || inherit_fd || || For [[RPC]] -- in swrk mode only
|-
|"skip-mnt" || || ||
|-
|"ext-mount-map" || ext_mnt/auto_ext_mnt || criu_add_ext_mount/criu_set_auto_ext_mount ||
|-
|"enable-fs" || || ||
|-
|"enable-external-sharing" || ext_sharing || criu_set_ext_sharing ||
|-
|"enable-external-masters" || ext_masters || criu_set_ext_masters ||
|-
| || pidfd_store_sk || criu_set_pidfd_store_sk || see [[Pidfd store]]
|-
|"network-lock" || network_lock || criu_set_network_lock ||
|-
|"help" || || ||
|-
|"version" || || ||
|-
|"pid" || || || obsoleted
|-
|"namespaces" || || || obsoleted
|-
|"close" || || || hidden and obsoleted
|-
|"contents" || || || deprecated (for show)
|-
|"file" || || || deprecated (for show)
|-
|"fields" || || || deprecated (for show)
|}

[[Category: API]]
[[Category: Outdated]]

CLI/opt/--network-lock

2021-08-08T15:36:18Z

Kir: use definition list; fix a link

Set the method to be used for network locking/unlocking. Locking is done to ensure that tcp packets are dropped between dump and restore. This is done to avoid the kernel sending RST when a packet arrives destined for the dumped process.

Currently two methods are available:
;<b>iptables</b>
: Use iptables rules to drop the packets. This is the default if 'method' is not specified.
;<b>nftables</b>
: Use nftables rules to drop the packets.

For more information: [[TCP connection#Checkpoint and restore TCP connection]]

[[Category:CLI]]

TCP connection

2021-08-08T15:31:35Z

Kir: use template:opt

This page describes how we handle established TCP connections.

== TCP repair mode in kernel ==

The <code>TCP_REPAIR</code> socket option was added to the kernel 3.5 to help with C/R for TCP sockets.

When this option is used, the socket is switched into a special mode, in which any action performed on it
does not result in anything defined by an appropriate protocol actions, but rather directly puts the socket
into the state that the socket is expected to be in at the end of a successfully finished operation.

For example, calling <code>connect()</code> on a repaired socket just changes its state to <code>ESTABLISHED</code>,
with the peer address set as requested.
The <code>bind()</code> call forcibly binds the socket to a given address (ignoring any potential conflicts).
The <code>close()</code> call closes the socket without any transient <code>FIN_WAIT</code>/<code>TIME_WAIT</code>/etc states,
socket is silently killed.

=== Sequences ===

To restore the connection properly, bind() and connect() is not enough. One also needs to restore the
TCP sequence numbers. To do so, the <code>TCP_REPAIR_QUEUE</code> and <code>TCP_QUEUE_SEQ</code> options were introduced.

The former one selects which queue (input or output) will be repaired and the latter gets/sets the sequence. Note
setting the sequence is only possible on CLOSE-d socket.

=== Packets in queue ===

When set the queue to repair as described above, one can call recv or send syscalls on a repaired socket. Both calls
result on peeking or poking data from/to the respective queue. This sounds funny, but yes, for repaired socket one
can receve the outgoing and send the incoming queues. Using the <code>MSG_PEEK</code> flag for <code>recv()</code> is required.

=== Options ===

There are 4 options that are negotiated by the socket at the connecting stage. These are

* mss_clamp -- the maximum size of the segment peer is ready to accept
* snd _scale -- the scale factor for a window
* sack -- whether selective acks are permitted or not
* tstamp -- whether timestamps on packets are supported

All four can be read with <code>getsockopt()</code> calls to a socket and in order to restore them the <code>TCP_REPAIR_OPTIONS</code> sockoption is introduced.

== Timestamp ==
"The sender's timestamp clock is used as a source of monotonic non-decreasing values to stamp the segments"(rfc7323). The Linux kernel uses the jiffies counter as the tcp timestamp.

<code>#define tcp_time_stamp ((__u32)(jiffies))</code>

We add the <code>TCP_TIMESTAMP</code> options to be able to compensate a difference between jiffies counters, when a connection is migrated on another host. When a connection is dumped, criu calls <code>getsockopt(TCP_TIMESTAMP)</code> to get a current timestamp, then on restore it calls <code>setsockopt(TCP_TIMESTAMP)</code> to set this timestamp as a starting point.

== Checkpoint and restore TCP connection ==

With the above sockoptions dumping and restoring TCP connection becomes possible. The criu just reads the socket
state and restores it back letting the protocol resurrect the data sequence.

One thing to note here — while the socket is closed between dump and restore the connection should be "locked", i.e.
no packets from peer should enter the stack, otherwise the RST will be sent by a kernel. In order to do so a simple
netfilter rule is configured that drops all the packets from peer to a socket we're dealing with. This rule sits
in the host netfilter tables after the criu dump command finishes and it should be there when you issue the
criu restore one. The locking method can be specified using the {{opt|--network-lock}} option.

Another thing to note is -- on restore there should be available the IP address, that was used by the connection.
This is automatically so if restore happens on the same box as dump. In case of hand-made live migration the
IP address should be copied too.

That said, the command line option {{opt|--tcp-established}} should be used when calling criu to explicitly state, that the
caller is aware of this "transitional" state of the netfilter.

In case the target process lives in NET namespace the connection locking happens the other way. Instead of
per-connection iptables rules the "network-lock"/"network-unlock" [[action scripts]] are called so that the user
could isolate the whole netns from network. Typically this is done by downing the respective veth pair end.

== States ==
=== TCP_SYN_SENT ===
There is only one difference with TCP_ESTABLISHED, we have to restore a socket and disable the repair mode before calling <code>connect()</code>. The kernel will send a one syn-sent packet with the same initial sequence number and sets the TCP_SYN_SENT state for the socket.

=== Half-closed sockets ===
A socket is half-closed when it sent or received a fin packet. These sockets are in one for these states: TCP_FIN_WAIT1, TCP_FIN_WAIT2, TCP_CLOSING, TCP_LAST_ACL, TCP_CLOSE_WAIT. To restore these states, we restore a socket into the TCP_ESTABLISHED state and then we call shutfown(SHUT_WR), if a socket has sent a fin packet and we send a fake fin packet, if a socket has received it before. For example, if we want to restore the TCP_FIN_WAIT1 state, we have to call shutfown(SHUT_WR) and we can send a fake ack to the fin packet to restore the TCP_FIN_WAIT2 state.

== See also ==
* [[Simple TCP pair]]
* [[TCP repair TODO]]
* [[CLI/opt/--tcp-close|Dropping the connection]]

== External links ==
* http://lwn.net/Articles/495304/

[[Category:Under the hood]]
[[Category:Sockets]]
[[Category: Editor help needed]]

CLI/opt/--lazy-pages

2021-06-15T20:56:11Z

Kir: fix a typo

The <code>--lazy-pages</code> option may be used with <code>dump</code>, <code>restore</code> and <code>page-server</code> actions.
Specifying this option enables functionality necessary for [[Userfaultfd|lazy memory restore]] and [[Lazy migration]].

The actual meaning of the <code>--lazy-pages</code> option depends what <code>criu</code> actions has been called with that option.

== Dump ==
Perform the dump procedure without writing memory pages into the image files and prepare to service page requests over the network.

When <code>dump</code> runs in this mode it presumes that [[CLI/cmd/lazy-pages|<code>lazy-pages</code>]] daemon will connect to it and fetch memory pages in order to lazily inject them into the restored process address space.

This option is intended for [[Lazy migration|post-copy (lazy) migration]] and should be used in conjunction with <code>restore</code> with appropriate options.

== Restore ==
Restore the processes without filling out the entire memory contents.

When this option is used, <code>restore</code> sets up the infrastructure required to fill memory pages either on demand when the process accesses them or in the background without stopping the restored process.

This option requires running [[CLI/cmd/lazy-pages|<code>lazy-pages</code>]] daemon.

== Page server ==
Serve local memory dump to a remote [[CLI/cmd/lazy-pages|<code>lazy-pages</code>]] daemon.

In this mode the <code>page-server</code> reads local memory dump and allows the remote <code>lazy-pages</code> daemon to request memory pages in random order.

Packages

2021-03-24T18:33:38Z

Kir: rm pkgs.org link as it's not working (and when you do a manual search not a lot of distros are found -- repology works better)

This page summarizes our knowledge about CRIU packages in various Linux distributions.

== Specific distributions ==

=== AltLinux ===
* http://packages.altlinux.org/crtools

=== Arch ===
* https://aur.archlinux.org/packages/criu/

As of '''2018-09-12''' the kernel package '''linux''' has CONFIG_CHECKPOINT_RESTORE enabled. The kernel package '''linux-lts''' has CONFIG_CHECKPOINT_RESTORE '''disabled'''.

=== CentOS ===
* https://git.centos.org/rpms/criu/releases
* https://copr.fedorainfracloud.org/coprs/adrian/criu-el7/

=== CoreOS ===
* https://github.com/coreos/coreos-overlay/tree/master/sys-process/criu

=== Debian ===
* https://tracker.debian.org/pkg/criu

=== Fedora ===
* https://apps.fedoraproject.org/packages/criu

=== Gentoo ===
* http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/criu/

=== Kali ===
* http://pkg.kali.org/pkg/criu

=== Mageia ===
* http://madb.mageia.org/package/show/application/0/name/criu

=== OpenSUSE ===
* https://build.opensuse.org/package/show/openSUSE:Factory/criu#

=== Ubuntu ===
* https://launchpad.net/ubuntu/+source/criu
* https://launchpad.net/~criu/+archive/ubuntu/ppa

== External links ==

* [https://repology.org/project/criu/versions repology.org: search CRIU package in various Linux distributions]
* [https://qa.debian.org/popcon.php?package=criu Popularity contest statistics for criu]

Packages

2021-03-24T18:31:30Z

Kir: moved distros to a sub-section; formatting changes

This page summarizes our knowledge about CRIU packages in various Linux distributions.

== Specific distributions ==

=== AltLinux ===
* http://packages.altlinux.org/crtools

=== Arch ===
* https://aur.archlinux.org/packages/criu/

As of '''2018-09-12''' the kernel package '''linux''' has CONFIG_CHECKPOINT_RESTORE enabled. The kernel package '''linux-lts''' has CONFIG_CHECKPOINT_RESTORE '''disabled'''.

=== CentOS ===
* https://git.centos.org/rpms/criu/releases
* https://copr.fedorainfracloud.org/coprs/adrian/criu-el7/

=== CoreOS ===
* https://github.com/coreos/coreos-overlay/tree/master/sys-process/criu

=== Debian ===
* https://tracker.debian.org/pkg/criu

=== Fedora ===
* https://apps.fedoraproject.org/packages/criu

=== Gentoo ===
* http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/criu/

=== Kali ===
* http://pkg.kali.org/pkg/criu

=== Mageia ===
* http://madb.mageia.org/package/show/application/0/name/criu

=== OpenSUSE ===
* https://build.opensuse.org/package/show/openSUSE:Factory/criu#

=== Ubuntu ===
* https://launchpad.net/ubuntu/+source/criu
* https://launchpad.net/~criu/+archive/ubuntu/ppa

== External links ==

* [https://repology.org/project/criu/versions repology.org: search CRIU package in various Linux distributions]
* [http://pkgs.org/search/criu pkgs.org: search CRIU package in various Linux distributions]
* [https://qa.debian.org/popcon.php?package=criu Popularity contest statistics for criu]

Packages

2021-03-24T18:07:18Z

Kir: added link to repology

This page summarizes our knowledge about CRIU packages in various Linux distributions.

== AltLinux ==
: http://packages.altlinux.org/crtools

== Arch ==
: https://aur.archlinux.org/packages/criu/

As of '''2018-09-12''' the kernel package '''linux''' has CONFIG_CHECKPOINT_RESTORE enabled. The kernel package '''linux-lts''' has CONFIG_CHECKPOINT_RESTORE '''disabled'''.

== CentOS ==
: https://git.centos.org/rpms/criu/releases
: https://copr.fedorainfracloud.org/coprs/adrian/criu-el7/

== CoreOS ==
: https://github.com/coreos/coreos-overlay/tree/master/sys-process/criu

== Debian ==
: https://tracker.debian.org/pkg/criu

== Fedora ==
: https://apps.fedoraproject.org/packages/criu

== Gentoo ==
: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/criu/

== Kali ==
: http://pkg.kali.org/pkg/criu

== Mageia ==
: http://madb.mageia.org/package/show/application/0/name/criu

== OpenSUSE ==
: https://build.opensuse.org/package/show/openSUSE:Factory/criu#

== Ubuntu ==
: https://launchpad.net/ubuntu/+source/criu
: https://launchpad.net/~criu/+archive/ubuntu/ppa

== See also ==

* [https://repology.org/project/criu/versions repology.org: search CRIU package in various Linux distributions]
* [http://pkgs.org/search/criu pkgs.org: search CRIU package in various Linux distributions]
* [https://qa.debian.org/popcon.php?package=criu Popularity contest statistics for criu]

MediaWiki:Sidebar

2021-02-13T03:50:00Z

Kir:

* navigation
** mainpage|mainpage-description
** recentchanges-url|recentchanges
** randompage-url|randompage
** helppage|help
* SEARCH
* TOOLBOX
* LANGUAGES

* News
** https://twitter.com/__criu__|Twitter
** http://www.youtube.com/c/OpenVZorg|YouTube

* External resources
** https://github.com/checkpoint-restore/criu|Github / source code
** https://github.com/checkpoint-restore/criu/issues|Issues / bugs
** https://ci.openvz.org/view/CRIU/|Mr. Jenkins
** https://www.openhub.net/p/criu|Open Hub
** http://openvz.org/|OpenVZ

Articles

2020-11-14T03:42:28Z

Kir: shrink the list for main page

<noinclude>This is a collection of external articles regarding the CRIU project, sorted by date.

</noinclude>
* 2020-04-30, [https://dl.acm.org/doi/abs/10.1145/3342195.3387555 Balancing efficiency and fairness in heterogeneous GPU clusters for deep learning]
* 2020-03-17, [https://www.ssrg.ece.vt.edu/papers/vee20-h-container.pdf Edge Computing -- the Case for Heterogeneous-ISA Container Migration]
* 2019-10-03, [https://dl.acm.org/citation.cfm?id=3357542 Fast In-Memory CRIU for Docker Containers]
* 2019-09-24, [https://ieeexplore.ieee.org/document/8916436 Using Container Migration for High Performance Computing (HPC) Workloads Resilience]
* 2019-09-11, [https://arxiv.org/pdf/1909.04945.pdf Performance Estimation of Container-BasedCloud-to-Fog Offloading]

<includeonly>: '''[[Articles|More external articles...]]'''</includeonly><noinclude>

* 2019-07-16, [https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=8754197 FastContainer: A Homeostatic System Architecture High-speed Adapting Execution Environment Changes]
* 2019-07-11, [https://ieeexplore.ieee.org/abstract/document/8814504 Exploring Potential for Non-Disruptive Vertical Auto Scaling and Resource Estimation in Kubernetes]
* 2019-07, University of Twente: [https://essay.utwente.nl/78342/1/coenen_MA_EEMCS.pdf Increasing Availability of the AEPU by Improving the Update Process]
* 2019-05-25, [https://dl.acm.org/citation.cfm?id=3303978 Replayable Execution Optimized for Page Sharing for a Managed Runtime Environment]
* 2019-04-29, Binghamton University: [http://www.cs.binghamton.edu/~huilu/pubs/mWarp.pdf mWarp: Accelerating Intra-Host Live Container Migration via Memory Warping]
* 2019-04-10, [https://lisas.de/~adrian/posts/2019-Apr-10-criu-and-selinux.html CRIU and SELinux]
* 2019-03-27, [https://www.mdpi.com/1424-8220/19/7/1488/pdf Container Migration in the Fog: A Performance Evaluation]
* 2019-03-25, [https://dl.acm.org/citation.cfm?id=3313947 Checkpointing and Migration of IoT Edge Functions]
* 2019-03-24, Future University Hakodate: [https://doi.asiabsdcon.org/10.25263/asiabsdcon2019/p07a Yet Another Container Migration on FreeBSD]
* 2019-03-09, [https://link.springer.com/article/10.1007/s10586-019-02920-6 Provenance-based fault tolerance technique recommendation for cloud-based scientific workflows: a practical approach]
* 2019-02-26, Georgia Institute of Technology / Peking University: [https://www.ndss-symposium.org/wp-content/uploads/2019/02/ndss2019_05A-3_Duan_paper.pdf Automating Patching of Vulnerable Open-Source Software Versions in Application Binaries]
* 2019-01-30, University West: [https://www.researchgate.net/publication/330798282_Evaluating_Distributed_MPI_Checkpoint_and_Restore_using_Docker_Containers_and_CRIU Evaluating Distributed MPI Checkpoint and Restore using Docker Containers and CRIU]
* 2018-12, University of Lille: [https://tel.archives-ouvertes.fr/tel-02011337/document Flexible Framework for Elasticity in Cloud Computing]
* 2018-12, Arizona State University: [https://search.proquest.com/openview/ef9070310256fe9ec9a663ebde537b36/1 Concurrent Checkpointing for Embedded Real-Time Systems]
* 2018-11-08, [https://lisas.de/~adrian/posts/2018-Nov-08-criu-configuration-files.html CRIU configuration files]
* 2018-11-06, [https://www.redhat.com/en/blog/using-criu-upgrade-vpn-servers-kernel-without-dropping-connections Using CRIU to upgrade a VPN server's kernel without dropping connections]
* 2018-10-13, [https://dl.acm.org/citation.cfm?id=3290626 Linux Process Tree Reconstruction Using The Attributed Grammar-Based Tree Transformation Model]
* 2018-10-10, [https://podman.io/blogs/2018/10/10/checkpoint-restore.html Adding checkpoint/restore support to Podman]
* 2018-09-15, [https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8539562 Stateful Container Migration employing Checkpoint-based Restoration for Orchestrated Container Clusters]
* 2018-09-07, [https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8502659 Container Live Migration for Latency Critical Industrial Applications on Edge Computing]
* 2018-08-15, University of Maryland: [https://drum.lib.umd.edu/bitstream/handle/1903/20499/CS-TR-5056.pdf Fast and Service-preserving Recovery from Malware Infections Using CRIU]
* 2018-07-31, [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6131214/ Hot-starting software containers for STAR aligner]
* 2018-07-07, Moscow Institute of Physics and Technology: [https://pdfs.semanticscholar.org/9ac4/f8ab4fd0492bfdc503831f60a5ce3d1d50a5.pdf?_ga=2.17262585.1140385641.1554239661-2109847679.1554239661 Using CRIU with HPC Containers: Field Experience]
* 2018-06-28, University of Aberdeen: [https://link.springer.com/chapter/10.1007/978-3-030-02465-9_13 Efficient Live Migration of Linux Containers]
* 2018-03-24, [https://www.smitechow.com/2018/03/compile-criu-on-centos-6.html Compile CRIU on CentOS 6]
* 2017-12-06, [https://lisas.de/~adrian/posts/2017-Dec-06-optimizing-live-container-migration-in-lxd.html Optimizing live container migration in LXD]
* 2017-10-12, Red Hat Blog: [http://rhelblog.redhat.com/2017/10/12/container-migration-around-the-world/ Container Migration Around The World]
* 2017-07-19, Red Hat Blog: [https://www.redhat.com/en/blog/how-can-process-snapshotrestore-help-save-your-day How can process snapshot/restore help save your day?]
* 2017-06-29, University West, Sweden: [http://www.diva-portal.org/smash/record.jsf?pid=diva2%3A1144045&dswid=4414 Distributed Checkpointing with Docker Containers in High Performance Computing]
* 2017-06-06, [https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=7980161 Voyager: Complete Container State Migration]
* 2017-06-06, Selectel Blog: [https://blog.selectel.com/managing-containers-runc/ Managing Containers in runC]
* 2016-12-16, University of Lisbon: [http://www.gsd.inesc-id.pt/~pjpf/ALMA-middleware-2016.pdf ALMA – GC-assisted JVM Live Migration for Java Server Applications]
* 2016-07-20, Red Hat KnowledgeBase: [https://access.redhat.com/articles/2455211 CRIU - Checkpoint/Restore in user space]
* 2016-07-20, LWN.net: [https://lwn.net/SubscriberLink/694593/4d6291b3f727791a/ Quality in open source: testing CRIU]
* 2016-06-22, Usenix: [https://www.usenix.org/conference/atc16/technical-sessions/presentation/kashyap Instant OS Updates via Userspace Checkpoint-and-Restart]
* 2016-05-04: [http://lisas.de/~adrian/?p=1183 Lazy Process Migration]
* 2015-12-31, [http://kimh.github.io/blog/jp/criu/experiment-to-suspend-and-resume-docker-container-with-criu-jp/ Use the CRIU Docker container of stop / resume to the challenge]
* 2015-12-31, [http://blog.codeship.com/how-containers-will-change-the-game-server-hosting-industry/ How Containers Will Change the Game Server Hosting Industry]
* 2015-09-21, [http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/ Checkpoint and restore Docker container with CRIU]
* 2015-09-21, [https://blog.docker.com/2015/09/dolly-demo-linuxcon-runc/ Dolly Demo at LinuxCon: Rapid cloning of existing services with runC]
* 2015-09-10, [http://blog.tonicdev.com/2015/09/10/time-traveling-in-node.js-notebooks.html Time Traveling in Node.js Notebooks]
* 2015-01-01, [http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/openstack-at-cisco/linux-containers-white-paper-cisco-red-hat.pdfLinux Containers: Why They’re in Your Future and What Has to Happen First]
* 2015-07-01, [https://kubernetes.io/blog/2015/07/how-did-quake-demo-from-dockercon-work/ How did the Quake demo from DockerCon Work?]
* 2015-05-06, [https://insights.ubuntu.com/2015/05/06/live-migration-in-lxd/ Live Migration in LXD] Ubuntu Insignts
* 2015-04-22, TuxDiary [http://tuxdiary.com/2015/04/22/dump-debug-resume-process-criu/ Dump, debug, resume process with criu]
* 2014-12-12, Symposium on Information and Communication Systems (SInCom 2014) [https://lisas.de/~adrian/proceedingsSInCom2014.pdf Checkpoint/Restore in User-Space with Open MPI]
* 2014-09-31, [http://www.reuters.com/article/wa-parallels-idUSnBw035202a+100+BSW20141103 Parallels Surpasses One Million Deployed Virtual Containers]
* 2014-08-01, ADMIN magazine: [http://www.admin-magazine.com/Archive/2014/22/Save-and-Restore-Linux-Processes-with-CRIU Save and Restore Linux Processes with CRIU]
* 2014-02-15, OCCAM Reproduce: [http://heirman.net/papers/reproduce2014.pdf Efficient, Accurate and Reproducible Simulation of Multi-Threaded Workloads] ([http://www.occamportal.org/slides/reproduce/reproduce14_slides_05.pdf slides])
* 2013-11-25, Phoronix: [http://www.phoronix.com/scan.php?page=news_item&px=MTUyNjE Checkpoint-Restore Hits v1.0: Freeze Your Linux Apps]
* 2013-11-25, LWN: [http://lwn.net/Articles/574918/ A note about 1.0]
* 2013-10-29, LWN: [http://lwn.net/Articles/572125/ Kernel summit report]
* 2013-02-01, A blog [http://www.anchor.com.au/blog/2013/02/overview-of-checkpoint-and-restore-live-migrating-processes-on-a-linux-system/ post] upon LCA-2013 talk.
* 2013-01-09, LWN: [http://lwn.net/Articles/531939/ Checkpoint/restore and signals]
* 2012-11-20, LWN: [http://lwn.net/Articles/525675/ LCE: Checkpoint/restore in user space: are we there yet?]
* 2012-07-24, OpenVZ blog: [http://openvz.livejournal.com/42414.html CRtools 0.1 released!]
* 2012-05-01, LWN: [http://lwn.net/Articles/495304/ TCP connection repair]
* 2012-02-26, The International Symposium on Grids and Clouds (ISGC) [https://lisas.de/~adrian/ISGC-2012_031.pdf Pos (isgc 2012) 031 live process migration for load balancing and/or fault tolerance]
* 2012-01-31, LWN: [http://lwn.net/Articles/478111/ Preparing for user-space checkpoint/restore]
* 2011-07-19, LWN: [http://lwn.net/Articles/452184/ Checkpoint/restart (mostly) in user space]

=== In Russian ===
* 13.05.2016, Habrahabr: [https://habrahabr.ru/post/283504/ Особенности тестирования технологии C/R в Linux]
* 09.03.2016, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=44015 Выпуск CRIU 2.0, системы для сохранения и восстановления состояния процессов в Linux]
* 18.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43539 CRIU, путь от вызывающей непонимание разработки до интеграции в Red Hat Enterprise Linux]
* 09.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43489 Выпуск CRIU 1.8, системы для сохранения и восстановления состояния процессов в Linux]
* 09.09.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42939 Выпуск CRIU 1.7, системы для сохранения и восстановления состояния процессов в Linux]
* 25.08.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42850 Проект OpenVZ анонсировал новый компонент для миграции Linux контейнеров - P.Haul]
* 27.05.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42315 Статус интеграции проектов CRIU и Docker]
* 25.11.2013, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=38519 Анонс выхода 1.0]
* 28.04.2015, Типичный программист: [http://tproger.ru/interview/pavel-emelyanov/ Разработка ядра Linux — это общение в клубе по интересам]
* 22.04.2013, Habrahabr: [http://habrahabr.ru/post/177499/ В преддверии очередного релиза CRIU]
* 04.03.2013, IT-computer: [http://www.it-computer.com/osvaivaem-sistemu-zamorozki-processov-criu Осваиваем систему заморозки процессов CRIU]
* 28.09.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34958 CRIU 0.2 release]
* 05.11.2013, Xakep: [https://xakep.ru/2013/11/05/criu-manual/ Осваиваем систему заморозки процессов CRIU]
* 15.08.2013, Habrahabr: [http://habrahabr.ru/company/parallels/blog/190066/ «Разработка ядра Linux — это общение в клубе по интересам»]
* 01.10.2012, YaC 2012: [http://events.yandex.ru/events/yac/2012/talks/352/ больше, чем живая миграция для Linux контейнеров]
* 24.07.2012, Habrahabr: [http://habrahabr.ru/post/148413/ CRIU — новый амбициозный проект для сохранения и восстановления состояния процессов]
* 24.07.2012, Ru-OpenVZ blog: [http://ru-openvz.livejournal.com/5753.html Вышел первый релиз CRtools, версия 0.1]
* 24.07.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34408 Первый релиз CRtools, утилиты для заморозки и восстановления состояния процессов в Linux]
* 24.07.2012, LOR: [http://www.linux.org.ru/news/kernel/8021514 Вышел первый релиз CRtools, версия 0.1]
* Копипаста о v0.1 "CRIU / CRtools 0.1 — создание контрольных точек Linux-приложений и восстановление с них": [http://rosinvest.com/novosti/949423 Rosinvest], [http://www.nixp.ru/news/11854.html NIXP] [http://pcnews.ru/top/news/day/criu-crtools-linux-openvz-checkpoint-restore-in-userspace-cpt-system-90-10-lxc-org-398305.html PCNews]
</noinclude>

BPF Maps

2020-11-14T03:37:51Z

Kir: formatting

BPF maps are kernel objects which store data (used by BPF programs) in the form of key-value pairs. Applications access BPF maps using file descriptors. C/R of BPF maps involves serializing their ''meta-data'' and ''data'':

: '''Meta-data''' - This includes information such as map type, key size, value size, etc. CRIU obtains this information from the proc filesystem and using the <code>bpf</code> system call with argument <code>BPF_OBJ_GET_INFO_BY_FD</code>.

: '''Data''' - This is the map's contents, i.e. the actual key-value pairs. CRIU relies on batch operations to read (<code>BPF_MAP_LOOKUP_BATCH</code>) key-value pairs from maps during the checkpoint stage and to write (<code>BPF_MAP_UPDATE_BATCH</code>) them during the restore phase.

== Support for BPF Maps ==

CRIU currently supports C/R of the following BPF map types:

* BPF_MAP_TYPE_HASH
* BPF_MAP_TYPE_ARRAY

== To-Do ==

* C/R of BTF (BPF Type Format) information
* C/R of other kinds of BPF maps

== External Links ==
* [https://www.kernel.org/doc/html/latest/bpf/index.html BPF Documentation]
* [https://blogs.oracle.com/linux/notes-on-bpf-1 Notes on BPF]
* [https://www.collabora.com/news-and-blog/blog/2019/04/05/an-ebpf-overview-part-1-introduction/ An eBPF Overview]

[[Category: Under the hood‏‎]]

Download/criu/3.13

2020-11-04T00:03:10Z

Kir: added willet image

[[Image:Willet.png|200px|right]]

[[Image:Willet_texas_april2003_1_1280.png|400px|right]]
{{Release|3.13}}

=== New features ===
* VDSO: arm32 support
* Add TLS support for [[page server]] communications
* "Ignore" mode for {{Opt|--manage-cgroups}}
* Restore SO_BROADCAST option for inet [[sockets]]

=== Bugfixes ===
* Auxiliary events were left in inotify queues
* Lazy-pages daemon didn't detect stack pages and surrounders properly and marked them as "lazy"
* Memory and resource leakage fixes detected by coverity, cppcheck and clang

=== Improvements ===
* Use gettimeofday() directly from vdso for restore timings
* Reformat all .py code into pep8 style

Download/criu/3.15

2020-11-03T23:59:37Z

Kir: cgroup2 -> cgroups v2

[[Image:3.15.jpg|400px|right]]
{{Release|3.15}}

=== New features ===
* Introduced criu-image-streamer (also see https://github.com/checkpoint-restore/criu-image-streamer).
* Added MIPS support.
* Allow checkpointing out of existing PID namespace and restoring into existing PID namespace.
* Added additional file validation mechanisms (buildid in addition to filesize).
* Added support to checkpoint and restore BPF hash maps (BPF_MAP_TYPE_HASH) and array maps (BPF_MAP_TYPE_ARRAY).
* Initial cgroups v2 support

=== Bugfixes ===
* Many fixes here and there

=== Improvements ===
* Additional libcriu interfaces (orphan_pts_master, version, FD handling)
* Use the new mount API

Packages

2020-07-07T18:39:18Z

Kir: fix centos link

This page summarizes our knowledge about CRIU packages in various Linux distributions.

== AltLinux ==
: http://packages.altlinux.org/crtools

== Arch ==
: https://aur.archlinux.org/packages/criu/

As of '''2018-09-12''' the kernel package '''linux''' has CONFIG_CHECKPOINT_RESTORE enabled. The kernel package '''linux-lts''' has CONFIG_CHECKPOINT_RESTORE '''disabled'''.

== CentOS ==
: https://git.centos.org/rpms/criu/releases
: https://copr.fedorainfracloud.org/coprs/adrian/criu-el7/

== CoreOS ==
: https://github.com/coreos/coreos-overlay/tree/master/sys-process/criu

== Debian ==
: https://tracker.debian.org/pkg/criu

== Fedora ==
: https://apps.fedoraproject.org/packages/criu

== Gentoo ==
: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/criu/

== Kali ==
: http://pkg.kali.org/pkg/criu

== Mageia ==
: http://madb.mageia.org/package/show/application/0/name/criu

== OpenSUSE ==
: https://build.opensuse.org/package/show/openSUSE:Factory/criu#

== Ubuntu ==
: https://launchpad.net/ubuntu/+source/criu
: https://launchpad.net/~criu/+archive/ubuntu/ppa

== See also ==

* [http://pkgs.org/search/criu Search CRIU package in various Linux distributions]
* [https://qa.debian.org/popcon.php?package=criu Popularity contest statistics for criu]

Template:Codename

2020-04-21T03:01:51Z

Kir: added 3.14

<includeonly>{{#switch: v{{{1}}}
| v2.1 = Steel Lapwing
| v2.2 = Carbon Nightingale
| v2.3 = Wooden Duck
| v2.4 = Marble Lark
| v2.5 = Concrete Oriole
| v2.6 = Paper Crane
| v2.7 = Rubber Owl
| v2.8 = Bronze Siskin
| v2.9 = Silk Tit
| v2.10 = Brass Waxwing
| v2.11 = Acrylic Bullfinch
| v2.12 = Vulcanite Rook
| v3.0 = Basalt Wagtail
| v3.1 = Graphene Swift
| v3.2 = Tin Hoopoe
| v3.3 = Crystal Pelican
| v3.4 = Cobalt Swan
| v3.5 = Clay Jay
| v3.6 = Alabaster Finch
| v3.7 = Vinyl Magpie
| v3.8 = Snow Bunting
| v3.9 = Sand Martin
| v3.10 = Granite Eagle
| v3.11 = Glass Flamingo
| v3.12 = Ice Penguin
| v3.13 = Silicon Willet
| v3.14 = Platinum Peacock
| 
}}</includeonly><noinclude>

This template is used to get the codename of a specified release. If there is no codename, empty string is produced.

== Usage ==

<pre><nowiki>{{Codename|VERSION}}</nowiki></pre>

== Examples ==

{| class="wikitable"
! Markup
! Result
|-
| <pre><nowiki>{{Codename|3.3}}</nowiki></pre>
| {{Codename|3.3}}
|-
| <pre><nowiki>{{Codename|2.1}}</nowiki></pre>
| {{Codename|2.1}}
|-
| <pre><nowiki>{{Codename|2.0}}</nowiki></pre>
| {{Codename|2.0}}
|}

== See also ==

* [[Release schedule]] for future codenames
* [[Template:Release date]]
* [[Template:criu]]
* [[Template:Release]]
* [[Template:Latest release]]

</noinclude>

Template:Codename

2020-04-21T03:01:09Z

Kir: rm 3.2.1 (patch releases does not have codenames)

<includeonly>{{#switch: v{{{1}}}
| v2.1 = Steel Lapwing
| v2.2 = Carbon Nightingale
| v2.3 = Wooden Duck
| v2.4 = Marble Lark
| v2.5 = Concrete Oriole
| v2.6 = Paper Crane
| v2.7 = Rubber Owl
| v2.8 = Bronze Siskin
| v2.9 = Silk Tit
| v2.10 = Brass Waxwing
| v2.11 = Acrylic Bullfinch
| v2.12 = Vulcanite Rook
| v3.0 = Basalt Wagtail
| v3.1 = Graphene Swift
| v3.2 = Tin Hoopoe
| v3.3 = Crystal Pelican
| v3.4 = Cobalt Swan
| v3.5 = Clay Jay
| v3.6 = Alabaster Finch
| v3.7 = Vinyl Magpie
| v3.8 = Snow Bunting
| v3.9 = Sand Martin
| v3.10 = Granite Eagle
| v3.11 = Glass Flamingo
| v3.12 = Ice Penguin
| v3.13 = Silicon Willet
| 
}}</includeonly><noinclude>

This template is used to get the codename of a specified release. If there is no codename, empty string is produced.

== Usage ==

<pre><nowiki>{{Codename|VERSION}}</nowiki></pre>

== Examples ==

{| class="wikitable"
! Markup
! Result
|-
| <pre><nowiki>{{Codename|3.3}}</nowiki></pre>
| {{Codename|3.3}}
|-
| <pre><nowiki>{{Codename|2.1}}</nowiki></pre>
| {{Codename|2.1}}
|-
| <pre><nowiki>{{Codename|2.0}}</nowiki></pre>
| {{Codename|2.0}}
|}

== See also ==

* [[Release schedule]] for future codenames
* [[Template:Release date]]
* [[Template:criu]]
* [[Template:Release]]
* [[Template:Latest release]]

</noinclude>

Download/criu/3.14

2020-04-21T02:59:01Z

Kir: more links

{{Release|3.14}}

=== New features ===
* C/R of memfd memory mappings and file descriptors.
* Add time namespace support.
* Add the [[Optimizing_pre_dump_algorithm|read pre-dump mode which uses process_vm_readv]].
* Add {{Opt|--cgroup-yard}} option
* Add support of the cgroup v2 freezer.
* Add support of opened O_PATH fds.

=== Bugfixes ===
* Fix C/R ia32 processes on AMD {{Bug|398}}
* Fix cross-compilation
* Many fixes here and there

=== Improvements ===
* Use clone3() with set_tid to restore processes
* Clean up compel headers.
* Use the new mount API

Podman

2020-04-20T23:09:40Z

Kir: /* Container Live Migration */ there was no 3.12.1 (officially)

This article describes the status of CRIU integration with [https://podman.io/ Podman], and how to use it.

== Container Checkpoint/Restore ==

Podman supports checkpointing and restoring since version 0.10.1 (October 2018). This initial support only supports checkpointing and restoring containers on the same host:

# podman run -d --name looper busybox /bin/sh -c \
'i=0; while true; do echo $i; i=$(expr $i + 1); sleep 1; done'

You can verify that the container is running by observing its logs:

# podman logs -l

Or by running <code>podman ps</code>.

If you do this a few times you will notice that the integers are increasing. Now the container can be checkpointed:

# podman container checkpoint -l

Once the container is checkpointed it will be no longer visible in <code>podman ps</code>.

The following command can be used to restore the container:

# podman container restore -l

Using <code>podman logs -l</code> or <code>podman ps</code> it can be verified that the container was restored and that it continued running from the point in time when it was checkpointed.

This requires at least CRIU 3.11.

There is one recording demonstrating Podman's checkpoint/restore support:

* https://asciinema.org/a/205183

== Container Live Migration ==

To be actually able to migrate a container from one system to another at least Podman version 1.4.0 (June 2019) is required. With version 1.4.0 Podman is now able to export a complete checkpoint which can then be transferred:

# podman run -d --name looper busybox /bin/sh -c \
'i=0; while true; do echo $i; i=$(expr $i + 1); sleep 1; done'
# podman container checkpoint -l --export=/tmp/chkpt.tar.gz
# scp /tmp/chkpt.tar.gz <destination-host>:/tmp

Once the checkpoint archive has been transferred to the destination system the container can there be restored from the checkpoint archive:

# podman container restore --import=/tmp/chkpt.tar.gz

Now the container continues to run from the same point where it was previously checkpointed on the source system.

From a checkpoint archive it is also possible to restore multiple copies of a container with different names:

# podman container restore --import=/tmp/chkpt.tar.gz -n looper1
# podman container restore --import=/tmp/chkpt.tar.gz -n looper2
# podman container restore --import=/tmp/chkpt.tar.gz -n looper3

Each of these restored containers will be running from the point in time the container was checkpointed.

One important limitation is that the container cannot modify the file-system. If a container modifies the file-system, these modified directories either have to be mounted into the container (<code>-v</code>) or these directories have to be marked as <code>--tmpfs</code>.

This requires at least CRIU 3.12 (3.13 for full SELinux support).

There are two recordings demonstrating Podman's container migration feature:

* https://asciinema.org/a/249918
* https://asciinema.org/a/249922

Download/criu/3.13

2020-04-20T23:05:38Z

Kir: /* Bugfixes */

[[Image:Willet.png|200px|right]]

{{Release|3.13}}

=== New features ===
* VDSO: arm32 support
* Add TLS support for [[page server]] communications
* "Ignore" mode for {{Opt|--manage-cgroups}}
* Restore SO_BROADCAST option for inet [[sockets]]

=== Bugfixes ===
* Auxiliary events were left in inotify queues
* Lazy-pages daemon didn't detect stack pages and surrounders properly and marked them as "lazy"
* Memory and resource leakage fixes detected by coverity, cppcheck and clang

=== Improvements ===
* Use gettimeofday() directly from vdso for restore timings
* Reformat all .py code into pep8 style

Download/criu

2020-04-20T23:04:28Z

Kir: there's no 3.12.1

== Latest version ==

{{:Download/criu/{{Last version}}}}

== Old versions ==

=== 3.x ===

The following [[Download/criu/3.x|3.x]] releases were made:

* {{fe|criu|{{nln}}* |3.12|3.11|3.10|3.9|3.8.1|3.8|3.7|3.6|3.5|3.4|3.3|3.2.1|3.2|3.1|3.0}}

=== 2.x ===

The following [[Download/criu/2.x|2.x]] releases were made:

* {{fe|criu|{{nln}}* |2.12.1|2.12|2.11.1|2.11|2.10|2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}

=== 1.x ===

The following [[Download/criu/1.x|1.x]] releases were made:

* {{fe|criu|{{nln}}* |1.8|1.7.2|1.7|1.6.1|1.6|1.5.2|1.5.1|1.5|1.4|1.3.1|1.3|1.3-rc2|1.3-rc1|1.2|1.1|1.1-rc2|1.1-rc1|1.0}}

=== 0.x ===

The following [[Download/criu/0.x|0.x]] releases were made:

* {{fe|criu|{{nln}}* |0.8|0.7|0.6|0.5|0.4|0.3|0.2|0.1}}

== See also ==

* [[Changelogs]] to see all the changelogs on a single page.

Template:Net-next.git

2020-03-27T01:00:33Z

Kir: update URL, rm <code>

[https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id={{{1}}} net-next: {{{1}}}]

Template:Torvalds.git

2020-03-27T00:58:25Z

Kir: update URL, rm <code>

[https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id={{{1}}} torvalds: {{{1}}}]

External bind mounts

2020-03-25T19:55:40Z

Kir: don't make "Sharing" the subsection of "old days"; minor English fixes

__TOC__

One of typical external resources when dumping a container (especially LXC/Docker) is a mount point whose root sits outside of the container's root. This situation was intended to be resolved using [[plugins]] but turned out to be common enough to introduce a built-in way of handling it.

== What is external bind mount ==

The way to create such is simple as

mkdir /root
mount --bind /foo /root/bar
chroot /root

This is it. From now on, the /bar file is a mountpoint whose root (the source) is not accessible directly.

If you look at the /proc/$pid/mountinfo file of a task seeing such you would see smth like

11 23 8:3 /root / ... - ext4 /dev/sda1 ...
23 34 8:3 /foo /bar ... - ext4 /dev/sda1 ...

The columns 4 and 5 are root and mountpoint respectively. You can see, that the / is /root file from /dev/sda1 device and /bar file is a mountpoint with the root being /foo file from the same device.

== How to teach CRIU to dump them ==

By default CRIU doesn't dump such mountpoints, because there's no way CRIU will be able to restore it -- the root of these mounts is out of scope of what CRIU dumped. In the logs you would see a message like

34:/bar doesn't have a proper root mount

which means the mountpoint /bar has inaccessible root.

To dump and restore them there's the <code>--external mnt[KEY]:VAL</code> option that sets up external mounts root mapping.

On dump, KEY is a mountpoint inside container, and corresponding VAL is a string that will be written into the image as mountpoint's root value.

On restore, KEY is the value from the image (VAL from dump), and the VAL is the path on host that will be bind-mounted into container (to the mountpoint path from image).

For example, if we want to dump the task above we should call

criu dump ... --external mnt[/bar]:barmount

The word <code>barmount</code> is an arbitrary identifier, that will be put in the image file instead of the original root path

criu show -f mountpoints.img -F mnt_id,root,mountpoint
mnt_id: 0x22 root: barmount mountpoint: /bar

On restore we should tell CRIU where to bind mount the <code>barmount</code> from like this

criu restore ... --external mnt[barmount]:/foo

With this CRIU will bind mount the /foo into proper mountpoint.

== Auto detection ==

In case one wants CRIU to autodetect and dump all the external bind mounts, and there is no need to change host mount points on restore, one can use a special syntax:

criu dump ... --external mnt[]:''flags''

Note here is nothing inside square brackets, and the optional <code>:''flags''</code> argument can contain the following characters:

; <code>m</code>
: Also enable dumping of external master mounts (as in <code>mount --make-slave</code>)
; <code>s</code>
: Also enable dumping of external shared mounts (as in <code>mount --make-shared</code>)

By default, neither master nor shared external mounts are not dumped (if found, dump is aborted). Note if <code>''flags''</code> are not given, semicolon is optional.

=== Examples ===

criu dump ... --external 'mnt[]'

Auto-detect and dump all external bind mounts.

criu dump ... --external 'mnt[]:s'

Auto-detect and dump all external bind mounts, including the shared ones.

criu dump ... --external 'mnt[]:sm'

Auto-detect and dump all external bind mounts, including the shared and the master ones.

== Sharing ==

External bindmounts can both have internal/external sharing. Please see the example:

# Preparation
unshare -m --propagation private
mkdir /external_mount_sharing_test
mount -t tmpfs tmpfs /external_mount_sharing_test/
mount --make-private /external_mount_sharing_test/
cd /external_mount_sharing_test
# Source of external mount
mkdir external_mount
mount -t tmpfs tmpfs-external external_mount/
mount --make-shared external_mount/
cat /proc/$$/mountinfo | grep external
# 811 755 0:60 / /external_mount_sharing_test rw,relatime - tmpfs tmpfs rw
# 812 811 0:62 / /external_mount_sharing_test/external_mount rw,relatime shared:290 - tmpfs tmpfs-external rw

# Switch to CT mntns
unshare -m --propagation unchanged sh
mkdir root
mount -t tmpfs tmpfs-root root/
mkdir root/external_sharing root/internal_sharing root/proc

# Create external mount
mount --bind external_mount/ root/external_sharing
mount --bind external_mount/ root/internal_sharing
mount --make-private root/internal_sharing
mount --make-shared root/internal_sharing

# More preparations
mount --bind /proc root/proc
cd root
mkdir bin lib64
SH=$(which sh)
cp $SH bin
cp $(ldd $SH | grep "/lib64" | sed 's/^.*$\/lib64\S*$\s.*$/\1/') lib64
CAT=$(which cat)
cp $CAT bin
cp $(ldd $CAT | grep "/lib64" | sed 's/^.*$\/lib64\S*$\s.*$/\1/') lib64
PATH=$PATH:/bin
chroot . sh
cat /proc/$$/mountinfo
# 843 841 0:63 / / rw,relatime - tmpfs tmpfs-root rw
# 861 843 0:62 / /external_sharing rw,relatime shared:290 - tmpfs tmpfs-external rw
# 898 843 0:62 / /internal_sharing rw,relatime shared:349 - tmpfs tmpfs-external rw
# 899 843 0:5 / /proc rw,nosuid,nodev,noexec,relatime - proc proc rw

Mounts 812 (on the host) and 861 (in a container) have the same sharing (shared group) - external sharing and mount 898 has it's own local shared group - internal sharing.

Before [https://github.com/checkpoint-restore/criu/pull/906 #906] we were detecting this external/internal sharing state for auto-detected external mounts only, but we need it for manual external mounts too. Moreover, this also applies to manual external slave mounts they can be external/internal slaves too.

So we detect that the mount is from external sharing if in mount namespace of CRIU there are mounts of the same shared group and also we detect that the mount is from external slavery if there is no master mount for it in CT mount namespaces.

== Old days ==

For now the same behavior is configured with the <code>--ext-mount-map KEY:VAL</code> option. Soon this option will be [[deprecation|deprecated]].

[[Category:HOWTO]]
[[Category:External]]

News/events

2020-03-12T06:54:33Z

Kir: added br, removed vertical whitespace

<noinclude> __NOTOC__


This page collects into about events criu takes part in.

<startFeed/></noinclude>
== FOSDEM 2020 ==
[[Image:Fosdem.png|left|100px|link=]]

'''Feburary 1, 2020, Brussels, Belgium'''

[https://fosdem.org/2020/schedule/event/containers_live_migration/ Container Live Migration]

--[[User:Rppt]] 19:22, 28 February 2020‎ (UTC)
<br clear="both">

== Linux Plumbers Conference 2019 ==
[[Image:Linuxplumbers.png|left|100px|link=]]

'''September 9-11, Lisbon, Portugal'''

[https://linuxplumbersconf.org/event/4/contributions/508/ Update on Task Migration at Google Using CRIU]

[https://linuxplumbersconf.org/event/4/contributions/472/ CRIU and the PID dance]

[https://linuxplumbersconf.org/event/4/contributions/513/ CRIU: Reworking vDSO proxification, syscall restart]

[https://linuxplumbersconf.org/event/4/contributions/478/ Secure Image-less Container Migration]

--[[User:Avagin]] 14:05, 23 Aug 2019 (UTC)
<br clear="both">

== Google Summer of Code 2019 ==
[[Image:gsoc.png|left|100px|link=]]

'''Mar-Sep 2019'''

[https://summerofcode.withgoogle.com/organizations/6333591376625664/ Google Summer of Code]

--[[User:Avagin]] 21:32, 26 Feb 2019 (PST)
<br clear="both">

<noinclude><endFeed/>

== See also ==
* [[News/events/past|Past events]]

</noinclude>

News/events

2020-03-12T06:53:12Z

Kir: signed the entry (Rppt: it is required so that RSS is properly generated with dates etc)

<noinclude> __NOTOC__


This page collects into about events criu takes part in.

<startFeed/></noinclude>
== FOSDEM 2020 ==
[[Image:Fosdem.png|left|100px|link=]]

'''Feburary 1, 2020, Brussels, Belgium'''

[https://fosdem.org/2020/schedule/event/containers_live_migration/ Container Live Migration]

--[[User:Rppt]] 19:22, 28 February 2020‎ (UTC)

== Linux Plumbers Conference 2019 ==
[[Image:Linuxplumbers.png|left|100px|link=]]

'''September 9-11, Lisbon, Portugal'''

[https://linuxplumbersconf.org/event/4/contributions/508/ Update on Task Migration at Google Using CRIU]

[https://linuxplumbersconf.org/event/4/contributions/472/ CRIU and the PID dance]

[https://linuxplumbersconf.org/event/4/contributions/513/ CRIU: Reworking vDSO proxification, syscall restart]

[https://linuxplumbersconf.org/event/4/contributions/478/ Secure Image-less Container Migration]

--[[User:Avagin]] 14:05, 23 Aug 2019 (UTC)
<br clear="both">

== Google Summer of Code 2019 ==
[[Image:gsoc.png|left|100px|link=]]

'''Mar-Sep 2019'''

[https://summerofcode.withgoogle.com/organizations/6333591376625664/ Google Summer of Code]

--[[User:Avagin]] 21:32, 26 Feb 2019 (PST)

<br clear="both">

<noinclude><endFeed/>

== See also ==
* [[News/events/past|Past events]]

</noinclude>

CLI/opt/--cgroup-yard

2020-02-05T22:53:42Z

Kir: redirect to a specific option description

#REDIRECT:[[CGroups#External_CGroup_yard]]