CRIU - User contributions [en]

Main Page

2026-10-19T19:36:50Z

Avagin:

<div style="float: {{{1|right}}}">
{{Download box|left}}
[[Image:4.3.png|right|340px]]
</div>
__NOTOC__
<big>Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux.

Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a Linux software. It can freeze a running container (or an individual application) and checkpoint its state to disk. The data saved can be used to restore the application and run it exactly as it was during the time of the freeze. Using this functionality, application or container live migration, snapshots, remote debugging, and [[usage scenarios|many other things]] are now possible.

CRIU started as a project of Virtuozzo, and grew with the tremendous help from the [[community]]. It is currently used by (integrated into) OpenVZ, [[LXC]]/LXD/Incus, [[Docker]], [[Podman]], [[Kubernetes]] and [[Integration|other software]], and [[packages|packaged for many Linux distributions]].
</big>
{{Like}}
<br clear="both">

<div class="m_right">
{{News block 2}}
</div>

<div class="m_left">
== Using ==

<big>
;Getting [[packages]] for your distribution
: Or try manual [[installation]] to have CRIU on your system
</big>

;[[CLI]], [[RPC]] and [[C API]]
: Three ways to start using the C/R functionality. [[:Category:API|More info]] about APIs.

;[[Usage scenarios]]
: Ideas how criu can be used (some are crazy indeed)

;[[:Category:HOWTO]]
: Collection of real world examples of how to use CRIU. Some are complex, some are not. HOW TO dump a [[simple loop]] might be the best one to start with. Also a set of [[asciinema]] records for real-life examples.

;[https://www.criu.org/index.php?title=FAQ FAQ] & [[When C/R fails]]
: A sort of troubleshooting guide

;[[What can change after C/R]]
: CRIU cannot (yet) save and restore every single bit of tasks' state. This page describes what bits visible through standard kernel API are such.

;[[What cannot be checkpointed]]
: What an application could do to make CRIU refuse to dump it.

;[[Contacts]]
: Ways to communicate with CRIU community

</div>

<div class="m_center">
== Developing ==
If you're interested in CRIU development, please subscribe to the criu mailing list: https://lore.kernel.org/criu/ (old one is https://lists.openvz.org/mailman/listinfo/criu)

;[[Images]]
: Description of image files format

;[[Plugins]]
: CRIU can call plugins provided by people

;[[Upstream kernel commits]]
: Mainline kernel commits tracker

;[[Recent commits]]
: CRIU tool repository commits

;[[Manpages]]
: Kernel's manpages commits tracker

;[[ZDTM Test Suite]]
: Zero downtime test suite

;[[Todo|TODO]]
: Current TODO list

;[[User namespace]]
: Implementing user namespace support

;[[Postulates]]
: What to keep in mind when writing new code

;[https://coveralls.io/github/checkpoint-restore/criu Code coverage results]
: Shows how zdtm run covers the criu code paths

;[[How to submit patches]]
:

</div>

<br clear="both">
<div class="m_left">
== Under the hood ==
* [[Checkpoint/Restore]]
* [[:Category:Under the hood]]
* [[:Category:Network]]
* [[:Category:Files]]
* [[:Category:Memory]]
* [[Pending signals]]
* [[Stages of restoring]]
* [[Code blobs]]
* [[Comparison to other CR projects]]
</div>

<div class="m_center">
== External links ==
{{:Articles}}
</div>

<div class="m_right">
== Misc ==
* [[Academic Research]]
* [[Podcasts]] and other audio/video interviews
* Project [[history]]
* [[Logo]] description
* [[Events]]
* [[CRIU acronym fun]]
</div>

Download/criu

2026-10-19T19:36:09Z

Avagin: /* 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.3}}
* {{fe|criu|{{nln}}* |4.2.2}}
* {{fe|criu|{{nln}}* |4.2.1}}
* {{fe|criu|{{nln}}* |4.2}}
* {{fe|criu|{{nln}}* |4.1.1}}
* {{fe|criu|{{nln}}* |4.1}}
* {{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.

Template:Codename

2026-10-19T19:35:41Z

Avagin:

<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
| v3.18 = Silver Sandpiper
| v3.19 = Bronze Peacock
| v4.0 = CRIUDA
| v4.1 = CRISCV
| v4.1.1 = CRISCV
| v4.2 = CRIUTIBILITY
| v4.2.1 = CRIUTIBILITY
| v4.2.2 = CRIUTIBILITY
| v4.3 = CRIURBO
| 
}}</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>

Release schedule

2026-10-19T19:35:06Z

Avagin: /* 2026 */

Starting from year 2018, the fixed release schedule is no more.
A new release is made about every few months, once it feels there are enough changes.

Below you can find dates and codenames for future (if known) and past releases.

== Future releases ==

{| class="wikitable"
! Date
! Version / codename
|-
| not selected
| ... Heron
|}

== Past releases ==

=== 2026 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.3}}
{{fe|Releases table/row||4.2.2}}
{{fe|Releases table/row||4.2.1}}
|}

=== 2025 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.2}}
{{fe|Releases table/row||4.1.1}}
{{fe|Releases table/row||4.1}}
|}

=== 2024 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.0}}
|}

=== 2023 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.19|3.18}}
|}

=== 2022 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.17}}
|}

=== 2021 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.16}}
|}

=== 2020 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.15|3.14}}
|}

=== 2019 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.13|3.12}}
|}

=== 2018 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.11|3.10|3.9|3.8}}
|}

=== 2017 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.7|3.6|3.5|3.4|3.3|3.2|3.1|3.0|2.12|2.11|2.10}}
|}

=== 2016 (2.x) ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}
|}

=== Older (1.x, 0.x) ===

See
* [[Download/criu/1.x|1.x]]
* [[Download/criu/0.x|0.x]]

== Historical release schedules ==

* Starting from version 2.0 and until the end of 2017, a new release was made once a month from the stable (master) branch with whatever is there.

* Starting from version 1.3 and until the end of 2017, CRIU used the time-driven release model with strict/known future release dates.

== See also ==

* [[Download/criu]] for the list of all releases, dates, and changelogs

Template:Release date

2026-10-19T19:34:28Z

Avagin:

<includeonly>{{#switch: v{{{1}}}
| v4.3 = 19 Oct 2026
| v4.2.2 = 19 Oct 2026
| v4.2.1 = 21 Jul 2026
| v4.2 = 13 Nov 2025
| v4.1.1 = 29 Jul 2025
| v4.1 = 25 Mar 2025
| v4.0 = 20 Sep 2024
| v3.19 = 27 Nov 2023
| v3.18 = 22 Apr 2023
| 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>

Release schedule

2026-10-19T19:24:51Z

Avagin: /* 2026 */

Starting from year 2018, the fixed release schedule is no more.
A new release is made about every few months, once it feels there are enough changes.

Below you can find dates and codenames for future (if known) and past releases.

== Future releases ==

{| class="wikitable"
! Date
! Version / codename
|-
| not selected
| ... Heron
|}

== Past releases ==

=== 2026 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.3}}
{{fe|Releases table/row||4.2.1}}
|}

=== 2025 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.2}}
{{fe|Releases table/row||4.1.1}}
{{fe|Releases table/row||4.1}}
|}

=== 2024 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.0}}
|}

=== 2023 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.19|3.18}}
|}

=== 2022 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.17}}
|}

=== 2021 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.16}}
|}

=== 2020 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.15|3.14}}
|}

=== 2019 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.13|3.12}}
|}

=== 2018 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.11|3.10|3.9|3.8}}
|}

=== 2017 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.7|3.6|3.5|3.4|3.3|3.2|3.1|3.0|2.12|2.11|2.10}}
|}

=== 2016 (2.x) ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}
|}

=== Older (1.x, 0.x) ===

See
* [[Download/criu/1.x|1.x]]
* [[Download/criu/0.x|0.x]]

== Historical release schedules ==

* Starting from version 2.0 and until the end of 2017, a new release was made once a month from the stable (master) branch with whatever is there.

* Starting from version 1.3 and until the end of 2017, CRIU used the time-driven release model with strict/known future release dates.

== See also ==

* [[Download/criu]] for the list of all releases, dates, and changelogs

Changelogs

2026-10-19T19:24:23Z

Avagin:

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.3|4.2.1|4.2|4.1.1|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}}

Template:Last version

2026-10-19T19:20:57Z

Avagin:

4.3

Download/criu/4.3

2026-10-19T19:20:38Z

Avagin:

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

=== New features ===
* Memory compression: Support for LZ4 memory page and block compression with multi-threaded decompression
* Support for AArch64 / ARM64 Guarded Control Stack (GCS)
* Parallelize memfd and anonymous shared memory content restore via async daemon (asyncd)
* Restorer: Restore VMA pages with Linux native AIO
* Add --image-io-mode option to support O_DIRECT reads/writes for pages images
* plugins/amdgpu: Support checkpoint and restore of DRM buffer objects and DMA-BUF file descriptors
* Support for Linux kernel binfmt_misc sandboxing
* Add UPDATE_INETSK hook for socket address rewrite during restore
* crit: Add offline compress and decompress commands for memory images
* criu: Add collection and restoration of timer_slack_ns per thread
* plugins/cuda: Add CUDA Driver API checkpoint backend and GPU device mapping on restore.
* service/page-xfer: Support image streaming (--stream) over RPC and incremental streamed dumps with --prev-images-dir
* criu: Support dumping and restoring inet socket UIDs
* plugins: Pass namespaced PLUGIN.NAME=VALUE options to plugins as argv
* rpc/libcriu: Expose page-server TLS options, --stream, --lazy-pages, and cgroup options in libcriu

=== Bugfixes ===
* restore: Fix exit code and wait status truncation for zombie processes
* restorer/pagemap: Detect EOF on truncated pages file to prevent infinite loops
* file-lock: Fix type confusion in broken read lease restore
* soccr: Restore TCP_REPAIR_WINDOW before TCP_SEND_QUEUE to avoid window collapse
* sk-queue: Fix SCM restore for packets containing both SCM_RIGHTS and SCM_CREDENTIALS
* sk-unix: Fix mutex deadlock on connect failure in standalone restore
* pipes: Restore pipe ownership to fix /proc/self/fd access permissions
* compel: Fix heap alignment for structs with XSAVE state
* fsnotify: Fix memory and file descriptor leaks in inotify/fanotify error paths
* pycriu: Fix self-dump failure when explicit PID is provided
* seize/compel: Always trace clone/fork/vfork on seized tasks and verify no new tasks were created during CHECKPOINT_DEVICES

=== Improvements ===
* compel/infect: Optimize task interception and stop tasks without hardware breakpoints
* restorer: Switch thread synchronization to atomic operations
* restore: Parallelize task stopping in attach_to_tasks and catch_tasks
* fsnotify: Add overlayfs directory walk fallback for inotify watches
* sockets: Support dumping and restoring ucred for Unix and Netlink sockets
* coredump: Enable coredump generation on riscv64
* contrib: Add reference client and test suite for criu-service
* docs: Major overhaul and export of "Under the Hood" architecture documentation
* ci: Consolidate test workflows, shard test suites, and add Lima-based kernel test jobs
* docs: Add CRIU image security and workload security considerations guides
* page-xfer: Support sending compressed page-server data over TLS
* cgroup: Clone /sys/fs/cgroup mount with OPEN_TREE_CLONE when dumping cgroup v2

File:4.3.png

2026-10-19T19:20:11Z

Avagin:

Template:Release date

2026-10-19T19:18:56Z

Avagin:

<includeonly>{{#switch: v{{{1}}}
| v4.3 = 19 Oct 2026
| v4.2.1 = 21 Jul 2026
| v4.2 = 13 Nov 2025
| v4.1.1 = 29 Jul 2025
| v4.1 = 25 Mar 2025
| v4.0 = 20 Sep 2024
| v3.19 = 27 Nov 2023
| v3.18 = 22 Apr 2023
| 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>

Template:Codename

2026-10-19T19:17:36Z

Avagin:

<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
| v3.18 = Silver Sandpiper
| v3.19 = Bronze Peacock
| v4.0 = CRIUDA
| v4.1 = CRISCV
| v4.1.1 = CRISCV
| v4.2 = CRIUTIBILITY
| v4.2.1 = CRIUTIBILITY
| v4.3 = CRIURBO
| 
}}</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

2026-10-19T19:16:09Z

Avagin: /* Old versions */

<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.3}}
* {{fe|criu|{{nln}}* |4.2.1}}
* {{fe|criu|{{nln}}* |4.2}}
* {{fe|criu|{{nln}}* |4.1.1}}
* {{fe|criu|{{nln}}* |4.1}}
* {{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.3

2026-10-16T18:10:36Z

Avagin: /* Improvements */

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

=== New features ===
* Memory compression: Support for LZ4 memory page and block compression with multi-threaded decompression
* Support for AArch64 / ARM64 Guarded Control Stack (GCS)
* Parallelize memfd and anonymous shared memory content restore via async daemon (asyncd)
* Restorer: Restore VMA pages with Linux native AIO
* Add --image-io-mode option to support O_DIRECT reads/writes for pages images
* plugins/amdgpu: Support checkpoint and restore of DRM buffer objects and DMA-BUF file descriptors
* Support for Linux kernel binfmt_misc sandboxing
* Add UPDATE_INETSK hook for socket address rewrite during restore
* crit: Add offline compress and decompress commands for memory images
* criu: Add collection and restoration of timer_slack_ns per thread
* plugins/cuda: Add CUDA Driver API checkpoint backend and GPU device mapping on restore.
* service/page-xfer: Support image streaming (--stream) over RPC and incremental streamed dumps with --prev-images-dir
* criu: Support dumping and restoring inet socket UIDs
* plugins: Pass namespaced PLUGIN.NAME=VALUE options to plugins as argv
* rpc/libcriu: Expose page-server TLS options, --stream, --lazy-pages, and cgroup options in libcriu

=== Bugfixes ===
* restore: Fix exit code and wait status truncation for zombie processes
* restorer/pagemap: Detect EOF on truncated pages file to prevent infinite loops
* file-lock: Fix type confusion in broken read lease restore
* soccr: Restore TCP_REPAIR_WINDOW before TCP_SEND_QUEUE to avoid window collapse
* sk-queue: Fix SCM restore for packets containing both SCM_RIGHTS and SCM_CREDENTIALS
* sk-unix: Fix mutex deadlock on connect failure in standalone restore
* pipes: Restore pipe ownership to fix /proc/self/fd access permissions
* compel: Fix heap alignment for structs with XSAVE state
* fsnotify: Fix memory and file descriptor leaks in inotify/fanotify error paths
* pycriu: Fix self-dump failure when explicit PID is provided
* seize/compel: Always trace clone/fork/vfork on seized tasks and verify no new tasks were created during CHECKPOINT_DEVICES

=== Improvements ===
* compel/infect: Optimize task interception and stop tasks without hardware breakpoints
* restorer: Switch thread synchronization to atomic operations
* restore: Parallelize task stopping in attach_to_tasks and catch_tasks
* fsnotify: Add overlayfs directory walk fallback for inotify watches
* sockets: Support dumping and restoring ucred for Unix and Netlink sockets
* coredump: Enable coredump generation on riscv64
* contrib: Add reference client and test suite for criu-service
* docs: Major overhaul and export of "Under the Hood" architecture documentation
* ci: Consolidate test workflows, shard test suites, and add Lima-based kernel test jobs
* docs: Add CRIU image security and workload security considerations guides
* page-xfer: Support sending compressed page-server data over TLS
* cgroup: Clone /sys/fs/cgroup mount with OPEN_TREE_CLONE when dumping cgroup v2

Download/criu/4.3

2026-10-16T18:09:20Z

Avagin: /* Bugfixes */

Download/criu/4.3

2026-10-16T18:07:51Z

Avagin: /* New features */

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

=== New features ===
* Memory compression: Support for LZ4 memory page and block compression with multi-threaded decompression
* Support for AArch64 / ARM64 Guarded Control Stack (GCS)
* Parallelize memfd and anonymous shared memory content restore via async daemon (asyncd)
* Restorer: Restore VMA pages with Linux native AIO
* Add --image-io-mode option to support O_DIRECT reads/writes for pages images
* plugins/amdgpu: Support checkpoint and restore of DRM buffer objects and DMA-BUF file descriptors
* Support for Linux kernel binfmt_misc sandboxing
* Add UPDATE_INETSK hook for socket address rewrite during restore
* crit: Add offline compress and decompress commands for memory images
* criu: Add collection and restoration of timer_slack_ns per thread
* plugins/cuda: Add CUDA Driver API checkpoint backend and GPU device mapping on restore.
* service/page-xfer: Support image streaming (--stream) over RPC and incremental streamed dumps with --prev-images-dir
* criu: Support dumping and restoring inet socket UIDs
* plugins: Pass namespaced PLUGIN.NAME=VALUE options to plugins as argv
* rpc/libcriu: Expose page-server TLS options, --stream, --lazy-pages, and cgroup options in libcriu

=== Bugfixes ===
* restore: Fix exit code and wait status truncation for zombie processes
* restorer/pagemap: Detect EOF on truncated pages file to prevent infinite loops
* file-lock: Fix type confusion in broken read lease restore
* soccr: Restore TCP_REPAIR_WINDOW before TCP_SEND_QUEUE to avoid window collapse
* sk-queue: Fix SCM restore for packets containing both SCM_RIGHTS and SCM_CREDENTIALS
* sk-unix: Fix mutex deadlock on connect failure in standalone restore
* pipes: Restore pipe ownership to fix /proc/self/fd access permissions
* compel: Fix heap alignment for structs with XSAVE state
* fsnotify: Fix memory and file descriptor leaks in inotify/fanotify error paths
* pycriu: Fix self-dump failure when explicit PID is provided

=== Improvements ===
* compel/infect: Optimize task interception and stop tasks without hardware breakpoints
* restorer: Switch thread synchronization to atomic operations
* restore: Parallelize task stopping in attach_to_tasks and catch_tasks
* fsnotify: Add overlayfs directory walk fallback for inotify watches
* sockets: Support dumping and restoring ucred for Unix and Netlink sockets
* coredump: Enable coredump generation on riscv64
* contrib: Add reference client and test suite for criu-service
* docs: Major overhaul and export of "Under the Hood" architecture documentation
* ci: Consolidate test workflows, shard test suites, and add Lima-based kernel test jobs

Download/criu/4.3

2026-08-29T01:45:11Z

Avagin: Created page with " right {{Release|..."

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

=== New features ===
* Memory compression: Support for LZ4 memory page and block compression with multi-threaded decompression
* Support for AArch64 / ARM64 Guarded Control Stack (GCS)
* Parallelize memfd and anonymous shared memory content restore via async daemon (asyncd)
* Restorer: Restore VMA pages with Linux native AIO
* Add --image-io-mode option to support O_DIRECT reads/writes for pages images
* plugins/amdgpu: Support checkpoint and restore of DRM buffer objects and DMA-BUF file descriptors
* Support for Linux kernel binfmt_misc sandboxing
* Add UPDATE_INETSK hook for socket address rewrite during restore
* crit: Add offline compress and decompress commands for memory images
* criu: Add collection and restoration of timer_slack_ns per thread

=== Bugfixes ===
* restore: Fix exit code and wait status truncation for zombie processes
* restorer/pagemap: Detect EOF on truncated pages file to prevent infinite loops
* file-lock: Fix type confusion in broken read lease restore
* soccr: Restore TCP_REPAIR_WINDOW before TCP_SEND_QUEUE to avoid window collapse
* sk-queue: Fix SCM restore for packets containing both SCM_RIGHTS and SCM_CREDENTIALS
* sk-unix: Fix mutex deadlock on connect failure in standalone restore
* pipes: Restore pipe ownership to fix /proc/self/fd access permissions
* compel: Fix heap alignment for structs with XSAVE state
* fsnotify: Fix memory and file descriptor leaks in inotify/fanotify error paths
* pycriu: Fix self-dump failure when explicit PID is provided

=== Improvements ===
* compel/infect: Optimize task interception and stop tasks without hardware breakpoints
* restorer: Switch thread synchronization to atomic operations
* restore: Parallelize task stopping in attach_to_tasks and catch_tasks
* fsnotify: Add overlayfs directory walk fallback for inotify watches
* sockets: Support dumping and restoring ucred for Unix and Netlink sockets
* coredump: Enable coredump generation on riscv64
* contrib: Add reference client and test suite for criu-service
* docs: Major overhaul and export of "Under the Hood" architecture documentation
* ci: Consolidate test workflows, shard test suites, and add Lima-based kernel test jobs

Category:Under the hood

2026-08-05T19:23:29Z

Avagin:

All 'Under the Hood' articles have been moved to the CRIU GitHub repo and can be found here: [https://checkpoint-restore.github.io/criu/ https://checkpoint-restore.github.io/criu/].

These articles describe reveals internals of the CRIU tool.

Google Summer of Code Ideas

2026-03-02T19:53:05Z

Avagin: /* Files on detached mounts */

Google Summer of Code (GSoC) is a global program that offers post-secondary students an opportunity to be paid for contributing to an open source project over a three month period.

This page contains project ideas for upcoming Google Summer of Code.

== Contact ==

First, make sure to go through the [[GSoC Students Recommendations]]. Once you build CRIU locally and C/R a simple process successfully, please contact the respective mentor for the idea you are interested in. For general questions feel free to send an email to the [mailto:criu@lists.linux.dev mailing list] or write in [https://gitter.im/save-restore/criu gitter].

== Project ideas ==

=== Kubernetes Operator for Automated Checkpointing ===

'''Summary:''' Extend the Checkpoint/Restore Operator with support for automated policy-based checkpointing.

The [https://github.com/checkpoint-restore/checkpoint-restore-operator Checkpoint/Restore Operator] for Kubernetes currently supports only policies and parameters that limit the number of checkpoints. This project aims to extend the current support with automated policy-based checkpointing, allowing users to define triggers for checkpoint creation, such as time-based schedules, resource thresholds (CPU, memory, I/O usage), Kubernetes events (node drain, pod eviction, preemption), and application-level signals or annotations.

'''Links:'''
* https://github.com/checkpoint-restore/checkpoint-restore-operator
* https://kubernetes.io/docs/reference/node/kubelet-checkpoint-api

'''Details:'''
* Skill level: intermediate
* Language: Go
* Expected size: 350 hours
* Mentors: Viktória Spišaková <spisakova@ics.muni.cz>, Radostin Stoyanov <rstoyanov@fedoraproject.org>, Adrian Reber <areber@redhat.com>

=== Forensic Checkpointing Framework for Kubernetes ===

Kubernetes provides a highly dynamic and ephemeral environment where workloads can start and disappear very quickly and are continuously being rescheduled across different nodes in the cluster.
One of the key challenges with forensic investigations in Kubernetes is capturing and preserving the evidence during security incidents. This project aims to address this problem by developing a framework for efficiently capturing and preserving the state of all running applications in a container at a specific point in time, along with the associated container configurations and metadata. These artifacts would allow investigators to accurately reconstruct the events, create a timeline, and analyze security incidents without impacting the running cluster. This is an important step towards enabling forensic readiness for Kubernetes, where cluster administrators proactively ensure the environments are prepared to collect and preserve evidence before a security incident occurs.

'''Links:'''
* https://github.com/checkpoint-restore/checkpointctl
* [https://fosdem.org/2026/events/attachments/F9RANH-forensic-snapshots-in-kubernetes/slides/267371/fosdem_2_4dh73ni.pdf Investigating Security Incidents with Forensic Snapshots in Kubernetes]
* [https://www.cncf.io/reports/cloud-native-security-whitepaper/ Cloud Native Security Whitepaper]
* [https://media.defense.gov/2022/Aug/29/2003066362/-1/-1/0/CTR_KUBERNETES_HARDENING_GUIDANCE_1.2_20220829.PDF Kubernetes Hardening Guide]

'''Details:'''
* Skill level: intermediate
* Language: Go
* Expected size: 350 hours
* Mentors: Lorena Goldoni <lory.goldoni@gmail.com>, Radostin Stoyanov <rstoyanov@fedoraproject.org>, Adrian Reber <areber@redhat.com>

=== Enabling Checkpoint/Restore of Rootless Containers ===

[https://rootlesscontaine.rs/ Rootless containers] are containers that can be created, run, and managed by unprivileged users. Container engines such as Podman natively support running containers in a rootless mode to improve security and usability. While checkpoint/restore functionality is already available for rootful containers and unprivileged checkpointing is possible with the <code>CAP_CHECKPOINT_RESTORE</code> capability, container engines do not yet support native checkpointing of containers running in rootless mode. This project aims to explore and address the remaining challenges required to enable unprivileged checkpoint/restore for rootless containers.

'''Links:'''
* https://github.com/checkpoint-restore/criu/pull/1930
* https://github.com/torvalds/linux/commit/124ea650d3072b005457faed69909221c2905a1f
* https://src.fedoraproject.org/rpms/criu/pull-request/10#request_diff

'''Details:'''
* Skill level: intermediate
* Language: C, Go
* Expected size: 350 hours
* Mentors: Radostin Stoyanov <rstoyanov@fedoraproject.org>, Adrian Reber <areber@redhat.com>

=== Checkpointing of POSIX message queues ===

'''Summary:''' Add support for checkpoint/restore of POSIX message queues

POSIX message queues are a widely used inter-process communication mechanism. Message queues are implemented as files on a virtual filesystem (mqueue), where a file descriptor (message queue descriptor) is used to perform operations such as sending or receiving messages. To support checkpoint/restore of POSIX message queues, we need a kernel interface (similar to [https://github.com/checkpoint-restore/criu/commit/8ce9e947051e43430eb2ff06b96dddeba467b4fd MSG_PEEK]) that would enable the retrieval of messages from a queue without removing them. This project aims to implement such an interface that allows retrieving all messages and their priorities from a POSIX message queue.

'''Links:'''
* https://github.com/checkpoint-restore/criu/issues/2285
* https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/ipc/mqueue.c
* https://www.man7.org/tlpi/download/TLPI-52-POSIX_Message_Queues.pdf

'''Details:'''
* Skill level: intermediate
* Language: C
* Expected size: 350 hours
* Mentors: Radostin Stoyanov <rstoyanov@fedoraproject.org>, Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
* Suggested by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>

=== Add support for SCM_CREDENTIALS / SCM_PIDFD and friends ===

'''Summary:''' Support for SCM_CREDENTIALS / SCM_PIDFD

SCM_CREDENTIALS and SCM_PIDFD are types of SCM (Socket-level Control Messages). They play a crucial role
in systemd and many other user space applications. This project is about adding support for these
SCMs to be properly saved and restored back with CRIU. There is an existing code in OpenVZ CRIU fork,
see [1] and [2]. Goal would be first of all to properly port this code, cover with extensive tests and
ensure that SCM_PIDFD / SO_PEERPIDFD are handled correctly. Also we expect to cover things like
SO_PASSRIGHTS and SO_PASSPIDFD.

There is some extra source of complexity here pidfds can be "stale" (see PIDFD_STALE in Linux kernel)
and we need to ensure that we properly cover those cases.

'''Links:'''
* [1] openvz-criu https://bitbucket.org/openvz/criu.ovz/history-node/918653a0a343194385592d7b50b5bd7a8fbe1cc1/criu/sk-unix.c?at=hci-dev
* [2] openvz-criu https://bitbucket.org/openvz/criu.ovz/history-node/918653a0a343194385592d7b50b5bd7a8fbe1cc1/criu/sk-queue.c?at=hci-dev
* [3] Linux kernel https://github.com/torvalds/linux/commit/5e2ff6704a275be009be8979af17c52361b79b89
* [4] Linux kernel https://github.com/torvalds/linux/commit/c679d17d3f2d895b34e660673141ad250889831f

'''Details:'''
* Skill level: intermediate / advanced
* Language: C
* Expected size: 350 hours
* Suggested by: Alexander Mikhalitsyn <alexander@mihalicyn.com>
* Mentors: Andrei Vagin <avagin@gmail.com>, Alexander Mikhalitsyn <alexander@mihalicyn.com>

=== Integrate with Live Update Orchestrator (LUO) ===

'''Summary:''' Integrate with Live Update Orchestrator (LUO)

Live Update Orchestrator (LUO) is a framework for Linux kernel
live updates (via kexec). Idea behind it is to provide kernel
and user space API to save specific system resources across
kexec reboot.

This research project explores how CRIU can be integrated with LUO.
For example, if a user is running memcached on a node, the current
approach would require a full CRIU dump, then saving the entire
process memory to disk, then followed by restoring it after the
kernel live update.

Instead, CRIU could be extended to leverage the LUO API. When instructed,
it could preserve selected memory regions directly across the kexec reboot,
avoiding a full disk dump and significantly accelerating the restore process
after the kernel update.

'''Links:'''
* [1] LUO kernel documentation https://docs.kernel.org/core-api/liveupdate.html
* [2] LUO memfd doc https://docs.kernel.org/mm/memfd_preservation.html

'''Details:'''
* Skill level: intermediate / advanced
* Language: C
* Expected size: 350 hours
* Suggested by: Andrei Vagin <avagin@gmail.com>
* Mentors: Andrei Vagin <avagin@gmail.com>, Alexander Mikhalitsyn <alexander@mihalicyn.com>

=== Optimize COW memory dumping ===

'''Summary:''' Optimize COW memory dumping

The Linux kernel memory management subsystem is highly optimized not only for performance, but also to minimize unnecessary memory consumption. A key example of this is how the kernel handles private VMAs when user space invokes the fork() system call.

Rather than duplicating the entire VMA tree along with all memory contents, the kernel creates optimized copies of inherited VMAs using the Copy-on-Write (COW) mechanism. When a process writes to a page within a COW-ed VMA, a write page fault occurs, and the kernel creates a private copy of that page before applying the modification. However, if the page is only read, no copying is performed.

This approach significantly improves fork() performance and can dramatically reduce memory usage in many workloads.

In CRIU, when dumping VMAs and their associated memory pages, this COW optimization is not currently taken into account during the dump phase. As a result, for COW-backed VMAs, CRIU may generate multiple copies of identical memory pages in the dump image.

During restore, however, CRIU explicitly handles this situation (see [1] and [2]) and attempts to reconstruct COW relationships inside the kernel. This step is critical: without it, a checkpoint/restore (C/R) cycle could lead to a substantial increase in memory consumption for the same process tree. For example, a workload that originally consumed 500 MiB could expand to 800 MiB after restore, which is clearly unacceptable.

This project aims to improve the dumping algorithm so that it avoids producing multiple unnecessary copies of identical pages belonging to COW-ed VMAs.

The project requires some understanding of Linux memory management internals and CRIU’s architecture. We strongly encourage GSoC contributors to study references [1] and [2] and experiment with the relevant code paths before applying. We are happy to answer questions and provide guidance along the way.

'''Links:'''
* [1] preparing COW VMAs https://github.com/checkpoint-restore/criu/blob/c180188db036f8ea4c08bfee28cbcdbdd52cdfc3/criu/mem.c#L878
* [2] private vma content restore cow case https://github.com/checkpoint-restore/criu/blob/c180188db036f8ea4c08bfee28cbcdbdd52cdfc3/criu/mem.c#L1219

'''Details:'''
* Skill level: intermediate / advanced
* Language: C
* Expected size: 350 hours
* Suggested by: Andrei Vagin <avagin@gmail.com>
* Mentors: Andrei Vagin <avagin@gmail.com>, Alexander Mikhalitsyn <alexander@mihalicyn.com>

== Suspended project ideas ==

Listed here are tasks that seem suitable for GSoC, but currently do not have anybody to mentor it.

=== Optimize logging engine ===

'''Summary:''' CRIU puts a lots of logs when doing its job. Logging is done with simple fprintf function. They are typically useless, but ''if'' some operation fails -- the logs are the only way to find what was the reason for failure.

At the same time the printf family of functions is known to take some time to work -- they need to scan the format string for %-s and then convert the arguments into strings. If comparing criu dump with and without logs the time difference is notable (15%-20%), so speeding the logs up will help improve criu performance.

One of the solutions to the problem might be binary logging. The problem with binary logs is the amount of efforts to convert existing logs to binary form. Preferably, the switch to binary logging either keeps existing log() calls intact, either has some automatics to convert them.

The option to keep log() calls intact might be in pre-compilation pass of the sources. In this pass each <code>log(fmt, ...)</code> call gets translated into a call to a binary log function that saves <code>fmt</code> identifier copies all the args ''as is'' into the log file. The binary log decode utility, required in this case, should then find the fmt string by its ID in the log file and print the resulting message.

'''Links:'''
* [[Better logging]]

'''Details:'''
* Skill level: intermediate
* Language: C, though decoder/preprocessor can be in any language
* Expected size: 350 hours
* Suggested by: Andrei Vagin
* Mentors: Alexander Mikhalitsyn <alexander@mihalicyn.com>

=== IOUring support ===
The io_uring Asynchronous I/O (AIO) framework is a new Linux I/O interface, first introduced in upstream Linux kernel version 5.1 (March 2019). It provides a low-latency and feature-rich interface for applications that require AIO functionality.

'''Links:'''
* https://blogs.oracle.com/linux/an-introduction-to-the-io_uring-asynchronous-io-framework
* https://github.com/axboe/liburing

'''Details:'''
* Skill level: expert (+linux kernel)
* Expected size: 350 hours

=== Add support for SPFS ===

'''Summary:''' The SPFS is a special filesystem that allows checkpoint and restore of such things as NFS and FUSE

NFS support is already implemented in Virtuozzo CRIU, but it's very beneficial to port it to mainline CRIU. The importaint part of it is the need to implement the integration of Stub-Proxy File System (SPFS) with LXC/yet_another_containers_environment.

'''Links'''
* https://github.com/checkpoint-restore/criu/issues/60
* https://github.com/checkpoint-restore/criu/issues/53
* https://github.com/skinsbursky/spfs
* https://patchwork.criu.org/series/137/

'''Details:'''
* Skill level: expert
* Language: C
* Mentor: Alexander Mikhalitsyn <alexander@mihalicyn.com>
* Suggested by: Alexander Mikhalitsyn <alexander@mihalicyn.com>

=== Anonymise image files ===

'''Summary:''' Teach [[CRIT]] to remove sensitive information from images

When reporting a BUG it may be not acceptable for the reporter to send us raw images, as they may contain sensitive data. Need to teach CRIT to "anonymise" images for publication.

List of data to shred:

* Memory contents. For the sake of investigation, all the memory contents can be just removed. Only the sizes of pages*.img files are enough.
* Paths to files. Here we should keep the paths relations to each other. The simplest way seem to be replacing file names with "random" (or sequential) strings, BUT (!) keeping an eye on making this mapping be 1:1. Note, that file paths may also sit in sk-unix.img.
* Registers.
* Process names. (But relations should be kept).
* Contents of streams, i.e. pipe/fifo data, sk-queue, tcp-stream, tty data.
* Ghost files.
* Tarballs with tmpfs-s.
* IP addresses in sk-inet-s, ip tool dumps and net*.img.

'''Links:'''
* [[Anonymize image files]]
* https://github.com/checkpoint-restore/criu/issues/360
* [[CRIT]], [[Images]]
* External links to mailing lists or web sites

'''Details:'''
* Skill level: beginner
* Language: Python

=== Add support for checkpoint/restore of CORK-ed UDP socket ===

'''Summary:''' Support C/R of corked UDP socket

There's UDP_CORK option for sockets. As man page says:
<pre>
If this option is enabled, then all data output on this socket
is accumulated into a single datagram that is transmitted when
the option is disabled. This option should not be used in
code intended to be portable.
</pre>

Currently criu refuses to dump this case, so it's effectively a bug. Supporting
this will need extending the kernel API to allow criu read back the write queue
of the socket (see [[TCP connection|how it's done]] for TCP sockets, for example). Then
the queue is written into the image and is restored into the socket (with the CORK
bit set too).

'''Notes:'''

We already had a couple (3) of tries for this problem:

* UDP_REPAIR approach didn't succeed: https://lore.kernel.org/netdev/721a2e32-c930-ad6b-5055-631b502ed11b@gmail.com/, https://lore.kernel.org/netdev/?q=udp_repair
* eBPF (CRIB) approach, socket queue iterator was not merged: https://lore.kernel.org/netdev/AM6PR03MB5848EDA002E3D7EACA7C6BDA99A52@AM6PR03MB5848.eurprd03.prod.outlook.com/, and we have general objections to CRIB approach https://lore.kernel.org/bpf/CAHk-=wjLWFa3i6+Tab67gnNumTYipj_HuheXr2RCq4zn0tCTzA@mail.gmail.com/

We still have one idea we didn't try, as UDP allows packets to be lost on the way on restore we can somehow mark the socket to drop all data before UNCORK. This way we don't really need to restore contents of UDP CORK-ed sockets send queue.

'''Links:'''
* https://github.com/checkpoint-restore/criu/issues/409
* https://github.com/criupatchwork/criu/commit/a532312
* [[Sockets]], [[TCP connection]]
* [[https://groups.google.com/forum/#!topic/comp.os.linux.networking/Uz8PYiTCZSg UDP cork explained]]

'''Details:'''
* Skill level: intermediate (+linux kernel)
* Language: C
* Expected size: 350 hours
* Mentors: Alexander Mikhalitsyn <alexander@mihalicyn.com>, Pavel Tikhomirov <ptikhomirov@virtuozzo.com>, Andrei Vagin <avagin@gmail.com>

[[Category:GSoC]]
[[Category:Development]]

Release schedule

2025-11-13T20:44:21Z

Avagin: /* 2025 */

Starting from year 2018, the fixed release schedule is no more.
A new release is made about every few months, once it feels there are enough changes.

Below you can find dates and codenames for future (if known) and past releases.

== Future releases ==

{| class="wikitable"
! Date
! Version / codename
|-
| not selected
| ... Heron
|}

== Past releases ==

=== 2025 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.2}}
{{fe|Releases table/row||4.1.1}}
{{fe|Releases table/row||4.1}}
|}

=== 2024 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.0}}
|}

=== 2023 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.19|3.18}}
|}

=== 2022 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.17}}
|}

=== 2021 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.16}}
|}

=== 2020 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.15|3.14}}
|}

=== 2019 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.13|3.12}}
|}

=== 2018 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.11|3.10|3.9|3.8}}
|}

=== 2017 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.7|3.6|3.5|3.4|3.3|3.2|3.1|3.0|2.12|2.11|2.10}}
|}

=== 2016 (2.x) ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}
|}

=== Older (1.x, 0.x) ===

See
* [[Download/criu/1.x|1.x]]
* [[Download/criu/0.x|0.x]]

== Historical release schedules ==

* Starting from version 2.0 and until the end of 2017, a new release was made once a month from the stable (master) branch with whatever is there.

* Starting from version 1.3 and until the end of 2017, CRIU used the time-driven release model with strict/known future release dates.

== See also ==

* [[Download/criu]] for the list of all releases, dates, and changelogs

Template:Release date

2025-11-13T20:43:46Z

Avagin:

<includeonly>{{#switch: v{{{1}}}
| v4.2 = 13 Nov 2025
| v4.1.1 = 29 Jul 2025
| v4.1 = 25 Mar 2025
| v4.0 = 20 Sep 2024
| v3.19 = 27 Nov 2023
| v3.18 = 22 Apr 2023
| 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>

Download/criu

2025-11-13T20:42:58Z

Avagin: /* 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.1.1}}
* {{fe|criu|{{nln}}* |4.1}}
* {{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.

Template:Last version

2025-11-13T20:41:50Z

Avagin:

4.2

Template:Codename

2025-11-08T05:46:16Z

Avagin:

<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
| v3.18 = Silver Sandpiper
| v3.19 = Bronze Peacock
| v4.0 = CRIUDA
| v4.1 = CRISCV
| v4.1.1 = CRISCV
| v4.2 = CRIUTIBILITY
| 
}}</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>

File:4.2.jpg

2025-11-08T05:42:20Z

Avagin:

Download/criu/4.2

2025-11-06T03:55:53Z

Avagin: Created page with " right {{Release|..."

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

=== New features ===
* plugins/amdgpu: Implement parallel restore
* Handle processes with uprobes vma

=== Bugfixes ===
* criu/compel: fix compilation on musl/arm64
* pagemap: change PagemapEntry.nr_pages to uint64 to support huge mappings
* pagemap: prevent integer overflow in pagemap_len
* Relax ELF magic check to support MIPS libraries
* Fix: getsockopt usage for SO_PASSCRED/SO_PASSSEC on Linux 6.16

=== Improvements ===
* ci: consolidate aarch64 tests on GitHub runners
* cr-service: Refactor RPC config parsing
* Many improvements in pycriu

Release schedule

2025-07-29T21:24:12Z

Avagin: /* 2025 */

Starting from year 2018, the fixed release schedule is no more.
A new release is made about every few months, once it feels there are enough changes.

Below you can find dates and codenames for future (if known) and past releases.

== Future releases ==

{| class="wikitable"
! Date
! Version / codename
|-
| not selected
| ... Heron
|}

== Past releases ==

=== 2025 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.1.1}}
{{fe|Releases table/row||4.1}}
|}

=== 2024 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.0}}
|}

=== 2023 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.19|3.18}}
|}

=== 2022 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.17}}
|}

=== 2021 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.16}}
|}

=== 2020 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.15|3.14}}
|}

=== 2019 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.13|3.12}}
|}

=== 2018 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.11|3.10|3.9|3.8}}
|}

=== 2017 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.7|3.6|3.5|3.4|3.3|3.2|3.1|3.0|2.12|2.11|2.10}}
|}

=== 2016 (2.x) ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}
|}

=== Older (1.x, 0.x) ===

See
* [[Download/criu/1.x|1.x]]
* [[Download/criu/0.x|0.x]]

== Historical release schedules ==

* Starting from version 2.0 and until the end of 2017, a new release was made once a month from the stable (master) branch with whatever is there.

* Starting from version 1.3 and until the end of 2017, CRIU used the time-driven release model with strict/known future release dates.

== See also ==

* [[Download/criu]] for the list of all releases, dates, and changelogs

Template:Last version

2025-07-29T21:23:41Z

Avagin:

4.1.1

Download/criu/4.1.1

2025-07-29T21:23:09Z

Avagin:

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

=== Bugfixes ===
* resolving the mount namespace restore issue caused by [https://github.com/torvalds/linux/commit/12f147ddd6de the kernel change].

Download/criu/4.1.1

2025-07-29T21:22:52Z

Avagin: Created page with " right {{Release|..."

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

=== Bugfixes ===
* resolving the mount namespace restore issue caused by [https://github.com/torvalds/linux/commit/12f147ddd6de the kernel change].

Template:Codename

2025-07-29T21:17:26Z

Avagin:

<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
| v3.18 = Silver Sandpiper
| v3.19 = Bronze Peacock
| v4.0 = CRIUDA
| v4.1 = CRISCV
| v4.1.1 = CRISCV
| 
}}</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

2025-07-29T21:16:31Z

Avagin:

<includeonly>{{#switch: v{{{1}}}
| v4.1.1 = 29 Jul 2025
| v4.1 = 25 Mar 2025
| v4.0 = 20 Sep 2024
| v3.19 = 27 Nov 2023
| v3.18 = 22 Apr 2023
| 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>

Main Page

2025-03-26T01:35:27Z

Avagin:

<div style="float: {{{1|right}}}">
{{Download box|left}}
[[Image:4.1.jpg|right|340px]]
</div>
__NOTOC__
<big>Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux.

Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a Linux software. It can freeze a running container (or an individual application) and checkpoint its state to disk. The data saved can be used to restore the application and run it exactly as it was during the time of the freeze. Using this functionality, application or container live migration, snapshots, remote debugging, and [[usage scenarios|many other things]] are now possible.

CRIU started as a project of Virtuozzo, and grew with the tremendous help from the [[community]]. It is currently used by (integrated into) OpenVZ, [[LXC]]/LXD, [[Docker]], [[Podman]], and [[Integration|other software]], and [[packages|packaged for many Linux distributions]].
</big>
{{Like}}
<br clear="both">

<div class="m_right">
{{News block 2}}
</div>

<div class="m_left">
== Using ==

<big>
;Getting [[packages]] for your distribution
: Or try manual [[installation]] to have CRIU on your system
</big>

;[[CLI]], [[RPC]] and [[C API]]
: Three ways to start using the C/R functionality. [[:Category:API|More info]] about APIs.

;[[Usage scenarios]]
: Ideas how criu can be used (some are crazy indeed)

;[[:Category:HOWTO]]
: Collection of real world examples of how to use CRIU. Some are complex, some are not. HOW TO dump a [[simple loop]] might be the best one to start with. Also a set of [[asciinema]] records for real-life examples.

;[https://www.criu.org/index.php?title=FAQ FAQ] & [[When C/R fails]]
: A sort of troubleshooting guide

;[[What can change after C/R]]
: CRIU cannot (yet) save and restore every single bit of tasks' state. This page describes what bits visible through standard kernel API are such.

;[[What cannot be checkpointed]]
: What an application could do to make CRIU refuse to dump it.

;[[Contacts]]
: Ways to communicate with CRIU community

</div>

<div class="m_center">
== Developing ==
If you're interested in CRIU development, please subscribe to the criu mailing list: https://lore.kernel.org/criu/ (old one is https://lists.openvz.org/mailman/listinfo/criu)

;[[Images]]
: Description of image files format

;[[Plugins]]
: CRIU can call plugins provided by people

;[[Upstream kernel commits]]
: Mainline kernel commits tracker

;[[Recent commits]]
: CRIU tool repository commits

;[[Manpages]]
: Kernel's manpages commits tracker

;[[ZDTM Test Suite]]
: Zero downtime test suite

;[[Todo|TODO]]
: Current TODO list

;[[User namespace]]
: Implementing user namespace support

;[[Postulates]]
: What to keep in mind when writing new code

;[https://coveralls.io/github/checkpoint-restore/criu Code coverage results]
: Shows how zdtm run covers the criu code paths

;[[How to submit patches]]
:

</div>

<br clear="both">
<div class="m_left">
== Under the hood ==
* [[Checkpoint/Restore]]
* [[:Category:Under the hood]]
* [[:Category:Network]]
* [[:Category:Files]]
* [[:Category:Memory]]
* [[Pending signals]]
* [[Stages of restoring]]
* [[Code blobs]]
* [[Comparison to other CR projects]]
</div>

<div class="m_center">
== External links ==
{{:Articles}}
</div>

<div class="m_right">
== Misc ==
* [[Academic Research]]
* [[Podcasts]] and other audio/video interviews
* Project [[history]]
* [[Logo]] description
* [[Events]]
* [[CRIU acronym fun]]
</div>

Template:Last version

2025-03-26T01:33:53Z

Avagin:

4.1

Release schedule

2025-03-26T01:33:35Z

Avagin:

Starting from year 2018, the fixed release schedule is no more.
A new release is made about every few months, once it feels there are enough changes.

Below you can find dates and codenames for future (if known) and past releases.

== Future releases ==

{| class="wikitable"
! Date
! Version / codename
|-
| not selected
| ... Heron
|}

== Past releases ==

=== 2025 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.1}}
|}

=== 2024 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.0}}
|}

=== 2023 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.19|3.18}}
|}

=== 2022 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.17}}
|}

=== 2021 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.16}}
|}

=== 2020 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.15|3.14}}
|}

=== 2019 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.13|3.12}}
|}

=== 2018 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.11|3.10|3.9|3.8}}
|}

=== 2017 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.7|3.6|3.5|3.4|3.3|3.2|3.1|3.0|2.12|2.11|2.10}}
|}

=== 2016 (2.x) ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}
|}

=== Older (1.x, 0.x) ===

See
* [[Download/criu/1.x|1.x]]
* [[Download/criu/0.x|0.x]]

== Historical release schedules ==

* Starting from version 2.0 and until the end of 2017, a new release was made once a month from the stable (master) branch with whatever is there.

* Starting from version 1.3 and until the end of 2017, CRIU used the time-driven release model with strict/known future release dates.

== See also ==

* [[Download/criu]] for the list of all releases, dates, and changelogs

Download/criu/4.1

2025-03-26T01:26:23Z

Avagin:

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

=== New features ===
* RISC-V Support
* PIDFD Support
* arm64: C/R PAC keys

=== Bugfixes ===
* vdso: handle vvar_vclock vma-s
* seize: Take --timeout option into account when freezing processes
* net: use unique lock chain names (nftables)
* Fixes here and there.

=== Improvements ===
* CUDA Enhancements
* Allow setting the default network locking backend
* Enable coredump generation for aarch64 and arm
* vdso: switch from DT_HASH to DT_GNU_HASH

File:4.1.jpg

2025-03-26T01:26:09Z

Avagin:

Download/criu/4.1

2025-03-26T01:24:39Z

Avagin:

[[Image:v4.1.jpg|400px|right]]
{{Release|4.1}}

=== New features ===
* RISC-V Support
* PIDFD Support
* arm64: C/R PAC keys

=== Bugfixes ===
* vdso: handle vvar_vclock vma-s
* seize: Take --timeout option into account when freezing processes
* net: use unique lock chain names (nftables)
* Fixes here and there.

=== Improvements ===
* CUDA Enhancements
* Allow setting the default network locking backend
* Enable coredump generation for aarch64 and arm
* vdso: switch from DT_HASH to DT_GNU_HASH

File:V4.1.jpg

2025-03-26T01:24:10Z

Avagin:

Download/criu/4.1

2025-03-26T00:39:58Z

Avagin: Created page with " right {{Release|..."

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

=== New features ===
* RISC-V Support
* PIDFD Support
* arm64: C/R PAC keys

=== Bugfixes ===
* vdso: handle vvar_vclock vma-s
* seize: Take --timeout option into account when freezing processes
* net: use unique lock chain names (nftables)
* Fixes here and there.

=== Improvements ===
* CUDA Enhancements
* Allow setting the default network locking backend
* Enable coredump generation for aarch64 and arm
* vdso: switch from DT_HASH to DT_GNU_HASH

Template:Release date

2025-03-26T00:30:08Z

Avagin:

<includeonly>{{#switch: v{{{1}}}
| v4.1 = 25 Mar 2025
| v4.0 = 20 Sep 2024
| v3.19 = 27 Nov 2023
| v3.18 = 22 Apr 2023
| 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>

Template:Codename

2025-03-26T00:29:22Z

Avagin:

<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
| v3.18 = Silver Sandpiper
| v3.19 = Bronze Peacock
| v4.0 = CRIUDA
| v4.1 = CRISCV
| 
}}</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>

Contacts

2025-02-07T04:55:47Z

Avagin:

There are many ways to contact CRIU community. This page contains official accounts in social networks and another points of connect.

* [https://github.com/checkpoint-restore GitHub checkpoint-restore project]
* [https://gitter.im/save-restore/CRIU Gitter] (Also reachable via Matrix: [https://matrix.to/#/#save-restore_CRIU:gitter.im #save-restore_CRIU:gitter.im])
* [https://twitter.com/__criu__ CRIU twitter]
* [https://www.youtube.com/channel/UCeXb0oWYd7ZE-44TrTSWxmg Youtube channel]
* [https://lore.kernel.org/criu/ Mailing list]
* IRC channels on Freenode:
** [https://webchat.freenode.net/?channels=#criu #criu] - developers talks. Logs are [https://botbot.me/freenode/criu/ available].
** [https://webchat.freenode.net/?channels=#criu-commit-bot #criu-commit-bot] - commits to CRIU source code repository
** [https://webchat.freenode.net/?channels=#criu-ci #criu-ci] - status of CI jobs from Jenkins

== See also ==

* [https://openvz.org/Contacts OpenVZ contacts]

[[Category: Communication]]

Main Page

2024-09-22T03:43:17Z

Avagin:

<div style="float: {{{1|right}}}">
{{Download box|left}}
[[Image:4.0.c.jpg|right|340px]]
</div>
__NOTOC__
<big>Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux.

Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a Linux software. It can freeze a running container (or an individual application) and checkpoint its state to disk. The data saved can be used to restore the application and run it exactly as it was during the time of the freeze. Using this functionality, application or container live migration, snapshots, remote debugging, and [[usage scenarios|many other things]] are now possible.

CRIU started as a project of Virtuozzo, and grew with the tremendous help from the [[community]]. It is currently used by (integrated into) OpenVZ, [[LXC]]/LXD, [[Docker]], Podman, and [[Integration|other software]], and [[packages|packaged for many Linux distributions]].
</big>
{{Like}}
<br clear="both">

<div class="m_right">
{{News block 2}}
</div>

<div class="m_left">
== Using ==

<big>
;Getting [[packages]] for your distribution
: Or try manual [[installation]] to have CRIU on your system
</big>

;[[CLI]], [[RPC]] and [[C API]]
: Three ways to start using the C/R functionality. [[:Category:API|More info]] about APIs.

;[[Usage scenarios]]
: Ideas how criu can be used (some are crazy indeed)

;[[:Category:HOWTO]]
: Collection of real world examples of how to use CRIU. Some are complex, some are not. HOW TO dump a [[simple loop]] might be the best one to start with. Also a set of [[asciinema]] records for real-life examples.

;[https://www.criu.org/index.php?title=FAQ FAQ] & [[When C/R fails]]
: A sort of troubleshooting guide

;[[What can change after C/R]]
: CRIU cannot (yet) save and restore every single bit of tasks' state. This page describes what bits visible through standard kernel API are such.

;[[What cannot be checkpointed]]
: What an application could do to make CRIU refuse to dump it.

;[[Contacts]]
: Ways to communicate with CRIU community

</div>

<div class="m_center">
== Developing ==
If you're interested in CRIU development, please subscribe to the criu mailing list: https://lists.openvz.org/mailman/listinfo/criu

;[[Images]]
: Description of image files format

;[[Plugins]]
: CRIU can call plugins provided by people

;[[Upstream kernel commits]]
: Mainline kernel commits tracker

;[[Recent commits]]
: CRIU tool repository commits

;[[Manpages]]
: Kernel's manpages commits tracker

;[[ZDTM Test Suite]]
: Zero downtime test suite

;[[Todo|TODO]]
: Current TODO list

;[[User namespace]]
: Implementing user namespace support

;[[Postulates]]
: What to keep in mind when writing new code

;[https://coveralls.io/github/checkpoint-restore/criu Code coverage results]
: Shows how zdtm run covers the criu code paths

;[[How to submit patches]]
:

</div>

<br clear="both">
<div class="m_left">
== Under the hood ==
* [[Checkpoint/Restore]]
* [[:Category:Under the hood]]
* [[:Category:Network]]
* [[:Category:Files]]
* [[:Category:Memory]]
* [[Pending signals]]
* [[Stages of restoring]]
* [[Code blobs]]
* [[Comparison to other CR projects]]
</div>

<div class="m_center">
== External links ==
{{:Articles}}
</div>

<div class="m_right">
== Misc ==
* [[Academic Research]]
* [[Podcasts]] and other audio/video interviews
* Project [[history]]
* [[Logo]] description
* [[Events]]
* [[CRIU acronym fun]]
</div>

Release schedule

2024-09-22T03:41:52Z

Avagin: /* Past releases */

Starting from year 2018, the fixed release schedule is no more.
A new release is made about every few months, once it feels there are enough changes.

Below you can find dates and codenames for future (if known) and past releases.

== Future releases ==

{| class="wikitable"
! Date
! Version / codename
|-
| not selected
| ... Heron
|}

== Past releases ==

=== 2024 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||4.0}}
|}

=== 2023 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.19|3.18}}
|}

=== 2022 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.17}}
|}

=== 2021 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.16}}
|}

=== 2020 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.15|3.14}}
|}

=== 2019 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.13|3.12}}
|}

=== 2018 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.11|3.10|3.9|3.8}}
|}

=== 2017 ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||3.7|3.6|3.5|3.4|3.3|3.2|3.1|3.0|2.12|2.11|2.10}}
|}

=== 2016 (2.x) ===

{| class="wikitable sortable"
! Date
! Version / codename
{{fe|Releases table/row||2.9|2.8|2.7|2.6|2.5|2.4|2.3|2.2|2.1|2.0}}
|}

=== Older (1.x, 0.x) ===

See
* [[Download/criu/1.x|1.x]]
* [[Download/criu/0.x|0.x]]

== Historical release schedules ==

* Starting from version 2.0 and until the end of 2017, a new release was made once a month from the stable (master) branch with whatever is there.

* Starting from version 1.3 and until the end of 2017, CRIU used the time-driven release model with strict/known future release dates.

== See also ==

* [[Download/criu]] for the list of all releases, dates, and changelogs

Template:Last version

2024-09-22T03:41:02Z

Avagin:

4.0

Download/criu/4.0

2024-09-21T09:33:21Z

Avagin:

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

=== New features ===
* Shadow stack support
* CUDA plugin: Introduced a plugin to support checkpointing and restoring NVIDIA CUDA applications.

=== Bugfixes ===
* cgroup: Add support for restoring a thread in a correct v1 cgroup
* mem: fix some VMAs being incorrectly mapped wtih PROT_WRITE
* criu: fix a fatal failure if nft doesn't work
* net: Fix TOCTOU race condition in unix_conf_op
* pagemap-cache: handle short reads
* Fixes here and there.

=== Improvements ===
* Pagemap cache: Added support for PAGEMAP_SCAN ioctl
* zdtm: Added tests for IP_TTL restore
* irmap: hardcode some more interesting paths
* util: use close_range when it's supported
* Fixes and improvements in amdgpu-plugin

Download/criu/4.0

2024-09-21T09:09:32Z

Avagin:

File:4.0.c.jpg

2024-09-21T09:08:56Z

Avagin:

File:4.0.b.jpg

2024-09-21T09:02:29Z

Avagin: