CRIU - User contributions [en]

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:

File:4.0.a.jpg

2024-09-21T09:01:45Z

Avagin:

Download/criu/4.0

2024-09-21T09:01:15Z

Avagin:

[[Image:4.0.a.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 ===
* Fixes here and there.

=== Improvements ===
* Pagemap cache: Added support for PAGEMAP_SCAN ioctl

File:4.0.jpg

2024-09-21T08:59:40Z

Avagin:

Download/criu/4.0

2024-09-21T08:37:47Z

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

[[Image:4.0.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 ===
* Fixes here and there.

=== Improvements ===
* Pagemap cache: Added support for PAGEMAP_SCAN ioctl

Changelogs

2024-09-21T08:28:38Z

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.0|3.19|3.18|3.17.1|3.17|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:Codename

2024-09-21T08:27:56Z

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
| 
}}</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

2024-09-21T08:04:25Z

Avagin:

<includeonly>{{#switch: v{{{1}}}
| 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>

Changelogs

2024-09-21T08:00:44Z

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}}|3.19|3.18|3.17.1|3.17|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}}

News/events

2024-09-19T14:58:41Z

Avagin:

<noinclude> __NOTOC__


This page collects into about events criu takes part in.

<startFeed/></noinclude>

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

'''18-20 Sep 2024, [https://lpc.events/event/18/sessions/193/#20240919 Containers and Checkpoint/Restore Microconference]

Other talks:
* [https://lpc.events/event/18/contributions/1729/ Userspace memory persistence over kexec]
* [https://lpc.events/event/18/contributions/1812/ Checkpoint/Restore In eBPF (CRIB)]

<br clear="both">

<noinclude><endFeed/>

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

</noinclude>

News/events/past

2024-09-19T14:52:47Z

Avagin:

{{Note|this page lists events that has happened already, kept here just for historical reasons. For future events, see [[News/events]].}}
__TOC__

== CloudNativeSecurityCon North America 2024 ==
[[Image:CloudNativeSecurityCon.png|left|200px|link=]]

'''June 27, 2024, Seattle, Washington'''

[https://sched.co/1dCVs End-to-End Encryption for Container Checkpointing in Kubernetes]

== Open Source Summit North America 2024 ==
[[Image:oss-na.png|left|200px|link=]]

'''April 17, 2024, Seattle, Washington'''

[https://sched.co/1aPu9 Investigating Checkpoint and Restore for GPU-Accelerated Containers]

== NVIDIA GTC 2024 ==
[[Image:nvidia-gtc.png|left|150px|link=]]

'''March 21, 2024, San Jose, CA'''

[https://www.nvidia.com/gtc/posters/#/session/1705106137731001cNAN Achieving K8S and Public Cloud Operational Efficiency using a New Checkpoint/Restart Feature for GPUs]

== KubeCon EU 2024 ==
[[Image:Kubecon.png|left|150px|link=]]

'''March 22, 2024, Paris, France'''

[https://sched.co/1YeP3 The Party Must Go on - Resume Pods After Spot Instance Shut Down]

[https://sched.co/1YeT4 Enabling Coordinated Checkpointing for Distributed HPC Applications]

== FOSDEM 2024 ==
[[Image:Fosdem.png|left|100px|link=]]

'''February 3, 2024, Brussels, Belgium'''

[https://fosdem.org/2024/schedule/event/fosdem-2024-3454-zeroing-and-the-semantic-gap-between-host-and-guest/ Zeroing and the semantic gap between host and guest]

[https://fosdem.org/2024/schedule/event/fosdem-2024-1855-forensic-container-checkpointing-and-analysis/ Forensic container checkpointing and analysis]

<br clear="both">

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

'''13 Nov 2023, [https://lpc.events/event/17/sessions/162/ Containers and Checkpoint/Restore Microconference]

[https://lpc.events/event/17/contributions/1572/ Introducing PAGEMAP_SCAN IOCTL for Windows syscalls translation and CRIU]

[https://lpc.events/event/17/contributions/1570/ Fuse mounts recovery and Checkpoint/Restore]

[https://lpc.events/event/17/contributions/1568/ Protecting Sensitive Data in Container Checkpoints]

<br clear="both">

== Open Source Summit Europe 2023 ==
[[Image:Osseu.png|left|100px|link=]]

'''Sept 20, 2023, Bilbao, Spain'''

[https://osseu2023.sched.com/event/1OGi9/digital-forensics-with-container-checkpointing-daniel-simionato-javier-martinez-sysdig Digital Forensics with Container Checkpointing]

<br clear="both">

== GopherCon India 2023 ==
[[Image:Gopher-india.jpg|left|50px|link=https://gopherconindia.org/]]

'''Sept 9, 2023, Pune, India'''

[https://www.youtube.com/watch?v=UGQgcIz9xGc Container checkpoints with Go and CRIU]

<br clear="both">

== LSDS Seminar ==
[[Image:Lsds-logo.jpg|left|200px|link=https://lsds.doc.ic.ac.uk/]]

'''March 9, 2023, Imperial College London'''

[https://lsds.doc.ic.ac.uk/content/transparent-container-checkpointing-and-rollback-recovery-kubernetes-open-challenges-and Transparent Container Checkpointing and Rollback-Recovery with Kubernetes: Open Challenges and Research Directions]

<br clear="both">

== FOSDEM 2023 ==
[[Image:Fosdem.png|left|100px|link=]]

'''February 4, 2023, Brussels, Belgium'''

[https://fosdem.org/2023/schedule/event/container_kubernetes_criu/ Kubernetes and Checkpoint/Restore]

<br clear="both">

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

'''14 Sep 2022, [https://lpc.events/event/16/sessions/136/ Containers and Checkpoint/Restore Microconference]

[https://lpc.events/event/16/contributions/1241/ Restoring process trees with child-sub-reapers, nested pid-namespaces and inherit-only resources]

[https://lpc.events/event/16/contributions/1242/ Unprivileged CRIU]

[https://lpc.events/event/16/contributions/1243/ Bringing up FUSE mounts C/R support]

== stackconf 2022 ==
[[Image:stackconf.png|left|200px|link=]]

'''Jul 19, Berlin

[https://stackconf.eu/talks/kubernetes-and-checkpoint-restore/ Kubernetes and Checkpoint/Restore]

== KubeCon + CloudNativeCon North America 2021 ==
[[Image:kubecon-2021.png|left|200px|link=]]

'''October 11-15, Los Angeles, California

[https://youtu.be/BXVyszsbYmg Container Checkpoint/Restore at Scale for Fast Pod Startup Time]

<br clear="both">

== X.Org Developer Conference 2021 ==

'''September 15, [https://youtu.be/uTZISTjqy9Q online on the wider Internet]

[https://indico.freedesktop.org/event/1/contributions/18/ Fast Checkpoint Restore for AMD GPUs with CRIU]

<br clear="both">

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

'''20 Sep 2021, [https://linuxplumbersconf.org/event/11/sessions/101/#20210920 Containers and Checkpoint/Restore Microconference] ([https://www.youtube.com/watch?v=SKyxugj8rxE video recording])

[https://linuxplumbersconf.org/event/11/contributions/891/ Fast Checkpoint Restore for GPUs]

[https://linuxplumbersconf.org/event/11/contributions/923/ Mount-v2 CRIU migration engine: status update]

[https://linuxplumbersconf.org/event/11/contributions/924/ Alternative ways to extract information about processes]

== Container Plumbing Days 2021 ==
[[Image:Container_plumbing_days.svg|left|100px]]

'''March 09, 2021, virtual'''

[https://containerplumbing.org/sessions/containerm Container Migration News]

--[[User:Adrian]] 16:10, 11 March 2021 (UTC)
<br clear="both">

== DevConf.cz 2021 ==
[[Image:Devconf17.svg|left|100px]]

'''February 19, 2021, virtual'''

[https://devconfcz2021.sched.com/event/gmId/container-live-migration Container Live Migration]

--[[User:Adrian]] 16:10, 11 March 2021 (UTC)
<br clear="both">

== Open Source Summit Europe 2020 ==
[[Image:Osseu.png|left|100px|link=]]

'''Oct 26, 2020, Virtual'''

[https://osseu2020.sched.com/event/eCDH/container-live-migration-adrian-reber-red-hat Container Live Migration]

--[[User:Adrian]] 16:10, 11 March 2021 (UTC)
<br clear="both">

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

'''August 24-28, [https://linuxplumbersconf.org/event/7/ online on the wider Internet]

[https://linuxplumbersconf.org/event/7/contributions/641/ Fast checkpointing with criu-image-streamer]

[https://linuxplumbersconf.org/event/7/contributions/642/ FastFreeze: Unprivileged checkpoint/restore for containerized applications]

[https://linuxplumbersconf.org/event/7/contributions/640/ CRIU mounts migration: problems and solutions]

[https://linuxplumbersconf.org/event/7/contributions/643/ Checkpoint-restoring containers with Docker inside]
<br clear="both">

== Phoronix news ==
[[Image:phoronix.png|left|100px|link=]]

'''August 4, 2020, online'''

[https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.9-Checkpoint-Restore Checkpoint/Restore Of Unprivileged Processes Sent In For Linux 5.9]
<br clear="both">

== DevOops 2020 ==
[[Image:Devoops.svg|left|100px|link=]]

'''July 10, 2020, online'''

[https://devoops-moscow.ru/en/2020/msk/talks/2eyl2ebmmix5ovx9imqhu9/ Container live migration with Podman and CRIU]

--[[User:Adrian]] 16:10, 11 March 2021 (UTC)
<br clear="both">

== OpenShift Twitch 2020 ==
[[Image:Openshift.jpg|left|50px|link=]]

'''June 20, 2020, online'''

[https://www.youtube.com/watch?v=-7DgNxyuz_o Container Migration and CRIU Details]

--[[User:Adrian]] 16:10, 11 March 2021 (UTC)
<br clear="both">

== 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">

== Tübix 2019 ==
[[Image:tuex.png|left|100px|link=]]

'''Jul 06, 2019, Tübingen, Germany'''

Adrian Reber [https://www.tuebix.org/2019/programm/adrian-reber-container-live-migration/ Container Live Migration]
<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]

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

'''Nov 13-15 , 2018, Vancouver, BC, Canada'''

[https://linuxplumbersconf.org/event/2/contributions/202/ Time Namespaces]

[https://linuxplumbersconf.org/event/2/contributions/207/ Another year with CRIU: News from the developers]

[https://linuxplumbersconf.org/event/2/contributions/205/ News from academia: FatELF, RDMA and CRIU]

[https://linuxplumbersconf.org/event/2/contributions/135/ Remote page faults over RDMA]

[https://linuxplumbersconf.org/event/2/contributions/209/ Task Migration at Google Using CRIU]

[https://linuxplumbersconf.org/event/2/contributions/210/ Securely Migrating Untrusted Workloads with CRIU]

[https://linuxplumbersconf.org/event/2/contributions/69/ Task Migration at Scale Using CRIU]

--[[User:Radostin]] 14:05, 18 Nov 2018 (UTC)
<br clear="both">

== Open Source Summit Europe 2018 ==
[[Image:Osseu17.png|left|100px|link=]]

'''Oct 24, 2018, Edinburgh, UK'''

[https://osseu18.sched.com/event/FxYI/to-kill-or-to-checkpoint-that-is-the-question-mike-rapoport-ibm-adrian-reber-red-hat To Kill, or to Checkpoint - That is the Question]

--[[User:Adrian]] 09:46, 29 September 2018 (UTC)
<br clear="both">

== Serverless meetup, Moscow ==
[[Image:Meetup.svg|left|100px|link=]]

'''Oct 18, 2018, Moscow'''

[https://www.meetup.com/ru-RU/moscow-serverless/events/255386528/ Задержки при вызове serverless функций: как формируются, на что влияют и как ими управлять], Владимир Порохов, Swifty Cloud

--[[User:Xemul]] 11:55, 17 October 2018 (UTC)
<br clear="both">

== FOSDEM 2018 ==
[[Image:Fosdem.png|left|100px|link=]]

'''Feburary 4, 2018, Brussels, Belgium'''

[https://fosdem.org/2018/schedule/event/containers_containing_memory/ Containers devroom]
* Containing container memory -- Mike Rapoport

--[[User:Avagin|Andrey Vagin]] 22:48, 31 Jan 2018 (PST)

== Open Source Summit EU 2017 ==

[[Image:Osseu17.png|left|100px|link=]]

'''Oct 23, 2017, Prague, Czech Republic'''

Mike Rapoport and Adrian Reber [http://sched.co/BxIG will talk about live migration]

--[[User:Xemul]] 12:00, 23 Aug 2017 (MSK)
<br clear="both">

== SECR 2017 ==

[[Image:Secr17logo.png|left|100px|link=]]

'''Oct 20, 2017, St. Petersburg, Russia'''

Pavel Begunkov will talk about [http://2017.secr.ru/lang/en/program/submitted-presentations/checkpointrestore-of-file-locks-from-userspace-in-linux file locks] checkpoint and restore.

--[[User:Xemul]] 13:30, 12 Sep 2017 (MSK)
<br clear="both">

== Open Source Summit NA 2017 ==

[[Image:OSS_na_white_0.png|left|100px|link=]]

'''Sep 11, 2017, Los Angeles, USA'''

Michael Holzheu [http://sched.co/BDpJ will talk] about CRIU on IBM mainframes.

--[[User:Xemul]] 14:00, 29 Jun 2017 (MSK)
<br clear="both">

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

'''Sep 13-15, 2017, Los Angeles, CA, USA'''

[https://linuxplumbersconf.org/2017/ocw/events/LPC2017/tracks/637 Checkpoint-Restore microconf]

--[[User:Xemul]] 18:20, 9 Aug 2017 (MSK)
<br clear="both">

== Systor 2017 ==

[[Image:Systor_2017.png|left|100px|link=]]

'''May 22-24, 2017, Haifa, Israel'''

[https://systor17posters.hotcrp.com/paper/8?cap=08aenKqSiwS9bA Accepted paper] about post-copy live migration from Mike Rapoport and Joel Nider

--[[User:Xemul]] 15:40, 21 Apr 2017 (MSK)
<br clear="both">

== SCALE 15x ==

[[Image:scale 15x logo.png|left|100px|link=]]

'''March 2-5, 2017, Pasadena, CA, USA'''

Kir Kolyshkin talked about some uncommon ways to use CRIU. [https://www.youtube.com/watch?v=7PKMctKf2JQ&t=18058 Video recording].

--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 20:57, 13 February 2017 (UTC)

== DevConf.cz 2017 ==
[[Image:Devconf17.svg|left|100px]]

'''January 27-29, 2017, Brno, Czech Republic'''

[https://devconf.cz/schedule.html Decreasing container downtime during migration] by Adrian Reber. (the devconf site is not URL-friendly these days, go to Day-3 tab and check 11AM talks)

--[[User:Xemul]] 9:20, 12 Jan 2016 (MSG)
<br clear="both">

== 2d1o podcast (rus) ==
'''Dec 22, 2016, On-Air'''

[https://www.2d1o.ru/episodes/s01e03.html 2d1o podcast] invited Pavel Emelyanov to talk about Live migration (of Docker containers).

--[[User:Xemul]] 11:00, 9 Jan 2017 (MSK)
<br clear="both">

== Middleware 2016 ==
'''Dec 12-16, 2016, Trento, Italy'''

Rodrigo Bruno gave a talk about Live Migrating JVM workloads using CRIU. Search for 'ALMA' on the [http://2016.middleware-conference.org/program/overall/ schedule page] :)

--[[User:Xemul]] 15:00, 19 Dec 2016 (MSK)
<br clear="both">

== Linux Piter ==
[[Image:Linuxpiter.png|left|100px|link=]]

'''Nov 11-12, 2016, St. Petersburg, Russia'''

Tycho Andersen will talk about [http://www.it-events.com/ru/events/6997#tabs-programm live migration in LXD]

--[[User:Xemul]] 11:30, 12 Oct 2016 (MSK)
<br clear="both">

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

'''Nov 2-4, 2016, Santa Fe, NM, USA'''

[http://wiki.linuxplumbersconf.org/2016:checkpoint-restart Checkpoint-Restore micro-conference] within the [http://www.linuxplumbersconf.org/2016/ bigger event]

--[[User:Xemul]] 21:50, 25 Apr 2016 (MSK)
<br clear="both">

== OpenStack summit 2016 ==
[[Image:OpenStack_Summit.png|left|100px|link=]]

'''Oct 25-28, 2016, Barcelona, Spain'''

Phil Estes talks about [https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15091/live-container-migration-on-openstack live container migration in OpenStack]

--[[User:Xemul]] 13:00, 25 Oct 2016 (MSK)
<br clear="both">

== Linux kernel meetup in Tel-Aviv ==

'''July 12, 2016, Tel-Aviv Israel'''

Mike Rapoport will deliver [http://www.meetup.com/Tel-Aviv-Yafo-Linux-Kernel-Meetup/events/232058698/?gj=te1&rv=te1 a talk about UserfaultFD and lazy migration].

--[[User:Xemul]] 12:50, 24 Jun 2016 (MSK)
<br clear="both">

== OSC'16 ==
[[Image:Oscfinal.png|left|100px|link=]]
'''June 22, 2016, Nürnberg, Germany'''

Takashi Iwai [https://media.ccc.de/v/896-exploring-criu Exploring CRIU]

--[[User:Xemul]] 16:15, 27 Jun 2016 (MSK)
<br clear="both">

== USENIX ATC'16 ==
[[Image:Usenix-logo.jpg|left|100px|link=]]

'''June 22-24, 2016, Denver, CO, USA'''

Sanidhya Kashyap will present [https://www.usenix.org/conference/atc16/technical-sessions/presentation/kashyap KuP] -- an instant OS updater using CRIU

--[[User:Xemul]] 11:30, 25 Apr 2016 (MSK)
<br clear="both"/>

== Black belt tech @ DockerCon 2016 ==

[[Image:Dockercon16.png|left|100px|link=]]

'''June 19-21, 2016, Seattle, WA, USA'''

Ross Boucher will talk about [https://blog.docker.com/2016/04/black-belt-talks-dockercon-2016/ Cloning running services with Docker and CRIU]

--[[User:Xemul]] 14:30, 13 Apr 2016 (MSK)
<br clear="both">

== Tuebingen 2016 ==
'''Jun 11, 2016, Tübingen, Germany'''

Adrian Reber [http://www.tuebix.org/2016/programm/adrian-reber-container-migration-using-criu-and-lxc/ will presend] the [[Userfaultfd]] and lazy migration.

--[[User:Xemul]] 14:15, 7 Jun 2016 (MSK)
<br clear="both">

== Systor 2016 ==

[[Image:Systor2016.jpg|left|100px|link=]]

'''Jun 6-8, 2016, Haifa, Israel'''

[http://www.systor.org/2016/accepted.html Accepted paper] about containers live migration from Mike Rapoport

--[[User:Xemul]] 20:15, 6 May 2016 (MSK)
<br clear="both">

== DevConf.cz 2016 ==
[[Image:Devconf.cz-logo.png|left|100px|link=]]

'''February 5, 2016, Brno, Czech Republic'''

[https://devconfcz2016.sched.org/event/5lzL/live-migrating-a-container-pros-cons-and-gotchas Live migrating a container: pros, cons and gotchas] by Pavel Emelyanov

--[[User:Xemul]] 9:20, 12 Jan 2016 (MSG)
<br clear="both">

== FOSDEM 2016 ==
[[Image:Fosdem.png|left|100px|link=]]

'''January 30, 2016, Brussels, Belgium'''

[https://www.fosdem.org/2016/schedule/track/containers_and_process_isolation/ Containers devroom]
* Using p.haul to migrate containers -- Tycho Andersen
* New horizons for the CRIU project -- Pavel Emelyanov

--[[User:Xemul]] 00:45, 19 December 2015 (MSK)
<br clear="both">

== LinuxMeetup Nizhny Novgorod 2016 ==
'''January 22, 2016, Nizhny Novgorod, Russia'''

[https://mdday.timepad.ru/event/279578/ И овцы целы, и волки сыты: как перезапустить проблемное приложение и одновременно отладить его] -- Pavel Emelyanov

--[[User:Xemul]] 13:00, 29 December 2015 (MSK)
<br clear="both">

== Linux Piter 2015 ==
[[Image:Tux.png|left|100px|link=]]

'''November 21, 2015, Saint Petersburg, Russia'''

[http://www.it-sobytie.ru/events/4868 Живая миграция контейнеров: плюсы, минусы, подводные камни] -- Pavel Emelyanov

--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 07:24, 26 August 2015 (EDT)
<br clear="both">

== DockerCon 2015 ==
[[Image:DockerCon15.png|left|100px|link=]]

'''November 16-17, 2015, Barcelona, Spain'''

Talk about live migration of containers -- [http://europe-2015.dockercon.com/speakers Pavel Emelyanov]

-- [[User:Xemul|Xemul]] 15:00, 1 October 2015 (MSK)
<br clear="both">

== ContainerDays NYC 2015 ==
[[Image:2015-nyc-logo.png|left|100px|link=]]

'''October 30, 2015, New York, U.S.A.'''

[http://dynamicinfradays.org/events/2015-nyc/programme.html#criu CRIU: Time and Space Travel for Linux Containers] -- by Kirill Kolyshkin

--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 00:43, 14 September 2015 (EDT)
<br clear="both">

== Двенадцатая конференция разработчиков свободных программ ==
[[Image:Altlinux-logo.gif|left|100px|link=]]

'''October 16-18, 2015, Kaluga, Russia'''

[http://www.altlinux.ru/news/archive/2015/08/item/743/ Живая миграция контейнеров: плюсы, минусы, подводные камни] -- Pavel Emelyanov

--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 08:17, 1 October 2015 (EDT)
<br clear="both">

== OpenVZ meetup ==
[[Image:Yandex.png|left|100px|link=]]

'''September 19, 2015, Moscow, Russia'''

[https://events.yandex.ru/events/yagosti/19-september-2015-linux/ Встреча разработчиков Linux-контейнеров]

* Живая миграция контейнеров: плюсы, минусы, подводные камни -- Павел Емельянов
* CRIU: ускорение запуска PHP в CloudLinux OS -- Руслан Купреев

--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 06:19, 28 August 2015 (EDT)
<br clear="both">

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

'''August 19-21, 2015, Seattle, WA, USA'''

[http://wiki.linuxplumbersconf.org/2015:ckptrestart C/R miniconf]

--[[User:Xemul|Xemul]] ([[User talk:Xemul|talk]]) 16:30, 9 February 2015 (MSK)
<br clear="both">

== DevZen podcast ==
[[Image:Devzen.jpg|left|100px|link=]]

'''July 17, 2015, on air'''

Pavel Emelyanov and Kirill Gorcunov will talk about CRIU.

[http://devzen.ru/ DevZen podcast]

--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 09:10, 3 July 2015 (EDT)
<br clear="both">

== LVEE 2015 ==
[[File:Logo_lvee_2015.svg|left|100px|link=]]

'''25-28 June 2015, Grodno, Belarus'''

[http://lvee.org/ru/conference_registrations/LVEE%202015 О том как маленький open-source проект меняет жизнь большой компании]

Pavel Emelyanov will talk about CRIU community (in Russian).

--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 08:08, 1 July 2015 (EDT)
<br clear="both">

== OS Day 2015 ==
[[File:Os-day-logo.png|left|100px|link=]]

'''9-10 June 2015, Kazan, Russia'''

[http://osday.org/emelyanov.html#speaker Консервирование процессов в домашних условиях]

Pavel Emelyanov will talk about CRIU's recent achievements and use-cases (in Russian).

--[[User:Xemul]] (19 May 2015 (MSK))
<br clear="both"/>

== ContainerDays 2015 ==
[[File:Logo-ContainerDays.png|left|100px|link=]]
'''June 5-6 2015, Boston, MA, USA'''

Kir Kolyshkin from OpenVZ project will give a talk [http://dynamicinfradays.org/events/2015-boston/programme.html#nproblems "N Problems of Linux Containers...and Some Solutions"] mentioning CRIU in it.

--[[User:Xemul]] (4 Jun 2015)
<br clear="both">

== DevOps Дефлопе ==
[[File:Deflope.png|left|100px|link=]]

'''June 2015, On Air'''

[http://devopsdeflope.ru/ DevOps Дефлопе - Русскоязычный подкаст о DevOps]

Andrew Vagin talks about integration CRIU and Docker and how checkpointing of processes can help in DevOps (in Russian).

--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 08:26, 14 May 2015 (EDT)
<br clear="both">

== FLOSS Weekly 2015 ==
[[Image:Floss-weekly.jpg|left|100px|link=]]

'''April 29, 2015, 8:30am PDT (15:30 GMT), live on air'''

[http://twit.tv/show/floss-weekly/334 Episode about CRIU]

--[[User:Sergey Bronnikov|SergeyB]] ([[User talk:Sergey Bronnikov|talk]]) 09:35, 8 April 2015 (EDT)
<br clear="both">

== FOSDEM 2015 ==
[[Image:Fosdem.png|left|100px|link=]]

'''February 1, 2015, Brussels, Belgium'''

[https://fosdem.org/2015/schedule/event/livemigration/ Live migration for containers is around the corner] -- Andrew Vagin

--[[User:Avagin|Andrey Vagin]] 10:20, 13 January 2015 (EST)
<br clear="both">

== Docker Meet-Up ==

'''October 29, 2014, Moscow, Russia'''

[http://www.meetup.com/DevOps-Moscow-in-Russian/events/214753582/ Talk about CRIU and Docker] -- Pavel Emelyanov<noinclude>

--[[User:Xemul|Pavel Emelyanov]] 19:30, 23 Oct 2014 (MSK)
<br clear="both">

== Linux Plumbers ==
[[Image:Linuxplumbers.png|left|100px|link=]]
'''October 15-17, 2014, Dusseldorf, Germany'''

[http://www.linuxplumbersconf.org/2014/an-in-depth-look-containers-microconference/ CRIU discussion at Containers mini-conf ] -- Pavel Emelyanov

--[[User:Xemul|Xemul]] ([[User talk:Xemul|talk]]) 11:35, 23 October 2014 (EDT)
<br clear="both">

== Docker Meetup ==

'''September 17, 2014, Mountain View, CA, USA'''

[http://www.meetup.com/Docker-Mountain-View/events/204603722/ Docker MV Meetup #3 at Google] -- Saied Kazemi [https://speakerdeck.com/saied/experimental-docker-checkpoint-and-restore-with-criu talked] about Docker + CRIU

--[[User:Xemul|Xemul]] ([[User talk:Xemul|talk]]) 03:26, 19 September 2014 (EDT)
<br clear="both">

== Open WG Talk ==
[[Image:Content_wg_talk.png|left|100px|link=]]

'''Friday, July 18, 2014, Minsk, Belarus'''

[https://www.eventbrite.com/e/open-wg-talk-2-linux-container-virtualization-tickets-12189971533?fb_action_ids=705517169505083&fb_action_types=og.likes&fb_source=feed_opengraph&action_object_map=%7B%22705517169505083%22%3A753726634669877%7D&action_type_map=%7B%22705517169505083%22%3A%22og.likes%22%7D&action_ref_map=%5B%5D Open WG Talk #2 (Linux container virtualization)] -- Andrey Vagin

--[[User:Avagin|Avagin]] ([[User talk:Avagin|talk]]) 10:58, 7 July 2014 (EDT)
<br clear="both"/>

== Texas Linux Fest 2014 ==

[[Image:Txlf2014.png|left|100px|link=]]

'''June 13-14, 2014, Austin, Texas, US'''

[http://texaslinuxfest.org/content/criu-time-and-space-travel-service-linux-apps CRIU: time and space travel service for Linux apps] -- Kir Kolyshkin

--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 11:52, 6 June 2014 (EDT)
<br clear="both"/>

== Docker Meetup ==

'''March 26, 2014, Tel Aviv, Israel'''

[http://www.meetup.com/Docker-Tel-Aviv/ Linux Containers and the Future Cloud] -- Rami Rosen

--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 12:50, 24 March 2014 (EDT)

<br clear="both">

== Haifux (LUG) ==
[[Image:Haifux.png|left|100px|link=]]

'''March 17, 2014, Haifa, Israel'''

[http://haifux.org/lectures/320/ Linux Containers and the Future Cloud] -- Rami Rosen

--[[User:Rami|Rami]] 03:23, 23 Feb 2014 (PST)
<br clear="both">

== SCALE 12x talk ==
[[Image:Scale_12x_dodecahedron.png|left|100px]]

'''Feb 23, 2014, Los Angeles'''

[http://www.socallinuxexpo.org/scale12x/presentations/seven-problems-linux-containers Seven problems of Linux Containers] -- Kir Kolyshkin

--[[User:Xemul|Xemul]] 13:00, 22 Feb 2014 (MSK)
<br clear="both">

== Moscow Virtualization Meetup ==

'''15 Feb, 2014, Moscow, Russia'''

[http://tech.yandex.ru/events/yagosti/msk-feb-2014/talks/1655/ CRIU 1.0 What is next?]

--[[User:Avagin|Avagin]] ([[User talk:Avagin|talk]]) 05:55, 30 January 2014 (EST)
<br clear="both">

== Hangout-on-Air ==
[[Image:Hoa.png|left|100px|link=]]

'''18:00, 7 Feb, 2014, Online'''

[https://plus.google.com/events/cfj8rg61m1uj6ns3pf6dd8f8me0 CRIU hopes and fears]

--[[User:Xemul|Xemul]] 10:00, 30 Jan 2014 (MSK)
<br clear="both">

== Linux Kernel Summit ==
[[Image:Logo_lks_black.png|left|100px|link=]]

'''October 23-25, 2013, Edinburgh, UK'''

A quick talk about CRIU project status. -- Pavel Emelyanov

--[[User:Xemul|Xemul]] 10:00, 25 Oct 2013 (MSK)
<br clear="both">

== LinuxCon Europe ==
[[Image:LinuxCon-logo.jpg|left|100px|link=]]

'''October 21-23, 2013, Edinburgh, UK'''

[http://linuxconcloudopeneu2013.sched.org/event/e0b06ed074144b5bcdb9a0b2791ff2cb?iframe=no&w=900&sidebar=yes&bg=no#.UhTeVGJFynw CRIU: Time and Space Travel Service for Linux Applications -- Pavel Emelyanov ]

Slides [https://events.linuxfoundation.org/sites/events/files/slides/criu-3.11.pdf "CRIU:Time and Space Travel Service for Linux Applications"]

--[[User:Xemul|Xemul]] 19:30, 21 Aug 2013 (MSK)
<br clear="both">

== LinuxCon North America ==
[[Image:LinuxCon-logo.jpg|left|100px|link=]]

'''September 16-18, 2013, New Orleans, LA, USA'''

[http://linuxconcloudopenna2013.sched.org/event/91c1b43ac4c93aeafc27c91ccaed7bc5#.Ue0JsmJFwrQ CRIU: Time and Space Travel Service for Linux Applications -- Pavel Emelyanov ]

Slides [https://events.linuxfoundation.org/sites/events/files/slides/criu-3.11.pdf "CRIU:Time and Space Travel Service for Linux Applications"]

--[[User:Xemul|Xemul]] 14:30, 22 July 2013 (MSK)
<br clear="both">

== CRIU talk at LVEE ==
[[Image:LVEE 2013.png‎|left|100px|link=http://lvee.org]]
'''27-30 June, 2013. Grodno, Belarus'''

Linux Userspace Checkpoint/Restore: From Dreams to Reality - Andrey Vagin

--[[User:Avagin|Avagin]] ([[User talk:Avagin|talk]]) 06:05, 6 June 2013 (EDT)
<br clear="both">

== Fedora Virtualization Day Moscow 2013==
[[Image:russian_fedora.png|left|100px|link=http://russianfedora.ru/]]
'''1 June, 2013. Moscow, Russia'''

[http://russianfedora.ru/content/%D0%98%D1%82%D0%BE%D0%B3%D0%B8-fedora-virtualization-day CRIU: Checkpoint and Restore (mostly) In Userspace - Andrey Vagin] [http://mirror.yandex.ru/fedora/russianfedora/video/FedoraVirtualizationDay/04-Wagin-Part2.webm video]

--[[User:Avagin|Avagin]] ([[User talk:Avagin|talk]]) 14:03, 5 June 2013 (EDT)
<br clear="both">

== CRIU talk at SCALE11x ==
[[Image:Scale-11x.png|100px|left|link=http://www.socallinuxexpo.org/scale11x]]
'''22-24 February, 2013. Los Angeles, CA, USA'''

[http://www.socallinuxexpo.org/scale11x/presentations/checkpoint-restore-live-migration-and-beyond Checkpoint, Restore, Live Migration and Beyond - Kir Kolyshkin]

--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 12:10, 23 January 2013 (EST)
<br clear="both">

== CRIU talk at linux.conf.au ==
[[Image:Linux-conf-au-2013.jpg|left|link=https://lca2013.linux.org.au/]]
'''28 January to 2 February, 2013. Canberra, Australia'''

[http://conf.linux.org.au/schedule/30116/view_talk?day=thursday Checkpoint and Restore: Are We There Yet? - Pavel Emelyanov]

--[[User:Kir|Kir]] 12:51, 8 October 2012 (EDT)
<br clear="both">

== FOSDEM 2013 ==
[[Image:Fosdem-2013.png|left|100px|link=https://fosdem.org/2013/]]
'''2 and 3 February, 2013. Brussels, Belgium'''

[https://fosdem.org/2013/schedule/event/criu_ckeckpoint_restore/ CRIU: Checkpoint and Restore (mostly) In Userspace - Andrey Vagin]

--[[User:Kir|Kir]] ([[User talk:Kir|talk]]) 21:00, 22 January 2013 (EST)
<br clear="both">

== LinuxCon Europe 2012 ==
[[Image:LinuxCon-logo.jpg|left|100px|link=]]

'''November 5-9, 2012, Barcelona, Spain'''

[http://linuxconeurope2012.sched.org/event/bd32207c146c75dd5cbf165006d47e7b Checkpoint and Restore: Are We There Yet? - Pavel Emelyanov]

--[[User:Kir|Kir]] 12:51, 8 October 2012 (EDT)
<br clear="both">

== YAC 2012 ==
[[Image:yac_logo.jpg|left|100px|link=]]

'''1 Oct 2012, Moscow, Russia'''

[https://events.yandex.ru/events/yac/2012?openTalkDescription=35-3 CRIU: more than a live migration (incl. slides and video)]

--[[User:Kir|Kir]] 12:25, 8 October 2012 (EDT)

Google Summer of Code Ideas

2024-03-08T01:15:12Z

Avagin:

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.

== Contacts ==

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@openvz.org mailing list] or write in [https://gitter.im/save-restore/criu gitter].

== Project ideas ==

=== 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>

=== 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).

'''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>, Andrei Vagin <avagin@gmail.com>

=== Add support for pidfd file descriptors ===

'''Summary:''' Support C/R of pidfd descriptors

There is pidfd_open syscall which allows opening
a special PID file descriptor. A user can send a signal to
the process (pidfd_send_signal syscall), wait for the process
(poll() on pidfd).

At the moment CRIU can't dump processes that have pidfd's opened.

'''Links:'''
* https://lwn.net/Articles/801319/
* https://lwn.net/Articles/794707/
* https://github.com/torvalds/linux/blob/v5.16/kernel/fork.c#L1877

'''Details:'''
* Skill level: intermediate
* Language: C
* Expected size: 350 hours
* Mentors: Alexander Mikhalitsyn <alexander@mihalicyn.com>, Christian Brauner <christian@brauner.io>
* Suggested by: Alexander Mikhalitsyn <alexander@mihalicyn.com>

=== Add support for memfd_secret file descriptors ===

'''Summary:''' Support C/R of memfd_secret descriptors

There is memfd_secret syscall which allows user to open
special memfd which is backed by special memory range which
is inaccessible by another processes (and the kernel too!).

At the moment CRIU can't dump processes that have memfd_secret's opened.

'''Links:'''
* https://lwn.net/Articles/865256/

'''Details:'''
* Skill level: intermediate
* Language: C
* Expected size: 350 hours
* Mentors: Alexander Mikhalitsyn <alexander@mihalicyn.com>, Mike Rapoport <mike.rapoport@gmail.com>
* Suggested by: Alexander Mikhalitsyn <alexander@mihalicyn.com>

=== Use eBPF to lock and unlock the network ===

'''Summary:''' Use eBPF instead of external iptables-restore tool for network lock and unlock.

During checkpointing and restoring CRIU locks the network to make sure no network packets are accepted by the network stack during the time the process is checkpointed. Currently CRIU calls out to iptables-restore to create and delete the corresponding iptables rules. Another approach which avoids calling out to the external binary iptables-restore would be to directly inject eBPF rules. There have been reports from users that iptables-restore fails in some way and eBPF could avoid this external dependency.

'''Links:'''
* https://www.criu.org/TCP_connection#Checkpoint_and_restore_TCP_connection
* https://github.com/systemd/systemd/blob/master/src/core/bpf-firewall.c
* https://blog.zeyady.com/2021-08-16/gsoc-criu

'''Details:'''
* Skill level: intermediate
* Language: C
* Expected size: 350 hours
* Mentors: Radostin Stoyanov <rstoyanov@fedoraproject.org>, Prajwal S N <prajwalnadig21@gmail.com>
* Suggested by: Adrian Reber <areber@redhat.com>

=== Files on detached mounts ===

'''Summary:''' Initial support of open files on "detached" mounts

When criu dumps a process with an open fd on a file, it gets the mount identifier (mnt_id) via /proc/<pid>/fdinfo/<fd>, so that criu knows from which exact mount the file was initially opened. This way criu can restore this fd by opening the same exact file from topologically the same mount in restored mount tree.

Restoring fd from the right mount can be important in different cases, for instance if the process would later want to resolve paths relative to the fd, and obviously resolving from the same file on different mount can lead to different resolved paths, or if the process wants to check path to the file via /proc/<pid>/fd/<fd>.

But we have a problem finding on which mount we need to reopen the file at restore if we only know mnt_id but can't find this mnt_id in /proc/<pid>/mountinfo.

Mountinfo file shows the mount tree topology of current mntns: parent - child relations, sharing group information, mountpoint and fs root information. And if we don't see mnt_id in it we don't know anything about this mount.

This can happen in two cases

* 1) external mount or file - if file was opened from e.g. host it's mount would not be visible in container mountinfo
* 2) mount was lazily unmounted

In case of 1) we have criu options to help criu handle external dependencies.

In case of 2) or no options provided criu can't resolve mnt_id in mountinfo and criu fails.

'''Solution:'''
We can handle 2) with: resolving major/minor via fstat, using name_to_handle_at and open_by_handle_at to open same file on any other available mount from same superblock (same major/minor) in container. Now we have fd2 of the same file as fd, but on existing mount we can dump it as usual instead, and mark it as "detached" in image, now criu on restore knows where to find this file, but instead of just opening fd2 from actually restored mount, we create a temporary bindmount which is lazy unmounted just after open making the file appear as a file on detached mount.

Known problems with this approach:

* Stat on btrfs gives wrong major/minor
* file handles does not work everywhere
* file handles can return fd2 on deleted file or on other hardlink, this needs special handling.

Additionally (optional part):
We can export real major/minor in fdinfo (kernel).
We can think of new kernel interface to get mount's major/minor and root (shift from fsroot) for detached mounts, if we have it we don't need file handle hack to find file on other mount (see fsinfo or getvalues kernel patches in LKML, can we add this info there?).

'''Details:'''
* Skill level: intermediate
* Language: C
* Expected size: 350 hours
* Mentor: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
* Suggested by: Pavel Tikhomirov <ptikhomirov@virtuozzo.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>, Prajwal S N <prajwalnadig21@gmail.com>
* Suggested by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>

=== Kubernetes operator for managing container checkpoints ===

'''Summary:''' Develop a Kubernetes operator that automates the management of container checkpoints

Container checkpointing has recently been introduced as an alpha feature in Kubernetes.
To enable this feature, the kubelet API was extended with an endpoint that enables the
creation of checkpoints for individual containers. By default, all container checkpoints
are stored as tar archives in <code>/var/lib/kubelet/checkpoints</code> using the following
file name format: <code>checkpoint-<pod-name>_<namespace-name>-<container-name>-<timestamp>.tar</code>.
However, the current implementation does not provide a mechanism for limiting the number
of checkpoints, which may lead to filling up all existing disk space. This project aims to
develop a Kubernetes operator that automates the management of checkpoints and provides
a garbage collection mechanism to discard obsolete checkpoints.

'''Links:'''
* https://github.com/checkpoint-restore/checkpoint-restore-operator
* https://kubernetes.io/docs/reference/node/kubelet-checkpoint-api/
* https://kubernetes.io/blog/2022/12/05/forensic-container-checkpointing-alpha/
* https://kubernetes.io/blog/2023/03/10/forensic-container-analysis/
* https://github.com/kubernetes/kubernetes/pull/115888
* https://github.com/kubernetes/enhancements/issues/2008

'''Details:'''
* Skill level: intermediate
* Language: Go
* Expected size: 350 hours
* Mentors: Adrian Reber <areber@redhat.com>, Radostin Stoyanov <rstoyanov@fedoraproject.org>, Prajwal S N <prajwalnadig21@gmail.com>
* Suggested by: Adrian Reber

== Suspended project ideas ==

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

=== 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

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

Main Page

2023-11-28T02:14:46Z

Avagin:

<div style="float: {{{1|right}}}">
{{Download box|left}}
[[Image:3.19.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.

;[[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>

File:3.19.jpg

2023-11-28T02:13:40Z

Avagin: v3.19

== Summary ==
v3.19

Template:Release date

2023-11-28T02:10:29Z

Avagin:

<includeonly>{{#switch: v{{{1}}}
| 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:Last version

2023-11-28T02:09:55Z

Avagin:

3.19

Release schedule

2023-11-28T02:09:41Z

Avagin: /* 2023 */

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 ==

=== 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/3.19

2023-11-16T21:00:55Z

Avagin: /* New features */

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

=== New features ===
* LoongArch64 support
* C/R membarrier() registrations
* Restore THP_DISABLE prctl.
* prctl: Migrate prctl(NO_NEW_PRIVS) setting.

=== Bugfixes ===
* Many fixes and improvements from the Google team.
* Fix dumping hugetlb-based memfd on kernels < 4.16.
* Fixes here and there.

=== Improvements ===
* drop python 2 support
* support XSAVE on newer Intel CPUs

Template:Codename

2023-11-16T20:44:02Z

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
| 
}}</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>