Jump to: navigation, search

Here we list major project milestones.

7 Mar 2016: CRIU 2[edit]

With CRIU 2 we

  • Switched to monthly releases
  • Introduced the devel branch
  • Reworked the code structure

7 Sep 2015: 1.7, time-driven releases[edit]

Since 1.7, a new version is released every 3 months, on the first Monday of a season.

31 Dec 2013: 1.1 release candidate 1[edit]

The biggest change of the 1.1 is going to be

In order to let people try the API and be able to change it if needed, we release the -rc1.

25 Nov 2013: Version 1.0 release[edit]

Some time before this CRIU has come to a state of all the kernel support it needed hit the upstream kernel (3.11). Then the v0.7 was released and the team concentrated on the tool itself. Then there was v0.8 with RPC service, a couple of other new features and a lot of bugfixes. At some point the team has mostly developed the next chunk of changes that was planned and were ready to tag the next version.

It was decided to make it be 1.0.

"Proof of concept" stage[edit]

Before 1.0 release CRIU was in the proof-of-concept state. The main goal of the project was defining the kernel API needed to make C/R real.

  • 3 Jul 2013: Linus merges memory tracking patches in v3.11. At that point, CRIU becomes as functional as OpenVZ checkpoint-restore kernel code. And CRIU user-space no longer requires custom kernel to work on.
  • 1 Jul 2013: V0.6
  • 30 Apr 2013: V0.5
  • 12 Apr 2013: Andrew Morton merges "Memory changes tracking" patches. These patches are prerequisite for such things as incremental dumps or iterative migration. We expect this memory tracker to be long-pending task, but things has happened to be simpler and faster than expected.
  • 20 Feb 2013: V0.4
  • 11 Dec 2012: V0.3
  • 20 Sep 2012: Checkpoint-restore tool v0.2
  • 23 Jul 2012: Checkpoint-restore tool v0.1
  • 14 Feb 2012: Andrew Morton starts to doubt in CRIU. From https://lkml.org/lkml/2012/2/14/384:
Thus far our (my) approach has been to trickle the c/r support code
into mainline as it is developed.  Under the assumption that the end
result will be acceptable and useful kernel code.

I'm afraid that I'm losing confidence in that approach.  We have this
patchset, we have Stanislav's "IPC: checkpoint/restore in userspace
enhancements" (which apparently needs to get more complex to support
LSM context c/r).  I simply *don't know* what additional patchsets are
expected.  And from what you told me it sounds like networking support
is at a very early stage and I fear for what the end result of that
will look like.

So I don't feel that I can continue feeding these things into mainline
until someone can convince me that we won't have a nasty mess (and/or
an unsufficiently useful feature) at the end of the project.
  • 12 Jan 2012: Linus merged a first wave of CRIU patches from Andrew Morton. From commit 0994695, the Andrew's quote :
    - checkpoint/restart feature work.                                                                                                    
      A note on this: this is a project by various mad Russians to perform                                                                
      c/r mainly from userspace, with various oddball helper code added                                                                   
      into the kernel where the need is demonstrated.                                                                                     
      So rather than some large central lump of code, what we have is                                                                     
      little bits and pieces popping up in various places which either                                                                    
      expose something new or which permit something which is normally                                                                    
      kernel-private to be modified.                                                                                                      
      The overall project is an ongoing thing.  I've judged that the size                                                                 
      and scope of the thing means that we're more likely to be successful                                                                
      with it if we integrate the support into mainline piecemeal rather                                                                  
      than allowing it all to develop out-of-tree.                                                                                        
      However I'm less confident than the developers that it will all                                                                     
      eventually work! So what I'm asking them to do is to wrap each piece                                                                
      of new code inside CONFIG_CHECKPOINT_RESTORE.  So if it all                                                                         
      eventually comes to tears and the project as a whole fails, it should                                                               
      be a simple matter to go through and delete all trace of it.
  • 30 Nov 2011: CRIU name coined, dot org domain registered.
Domain Name:CRIU.ORG
Created On:30-Nov-2011 12:49:39 UTC

15 Jul 2011: Pavel sent initial RFC and code[edit]

From http://lwn.net/Articles/451916/:

From: Pavel Emelyanov
Subject: [RFC][PATCH 0/7 + tools] Checkpoint/restore mostly in the userspace
Date: Fri, 15 Jul 2011 17:45:10 +0400

Hi guys!

There have already been made many attempts to have the checkpoint/restore functionality
in Linux, but as far as I can see there's still no final solutions that suits most of
the interested people. The main concern about the previous approaches as I see it was
about - all that stuff was supposed to sit in the kernel thus creating various problems.

I'd like to bring this subject back again proposing the way of how to implement c/r
mostly in the userspace with the reasonable help of a kernel.

That said, I propose to start with very basic set of objects to c/r that can work with

* x86_64 tasks (subtree) which includes
   - registers
   - TLS
   - memory of all kinds (file and anon both shared and private)
* open regular files
* pipes (with data in it)

Core idea:

The core idea of the restore process is to implement the binary handler that can execve-ute
image files recreating the register and the memory state of a task. Restoring the process 
tree and opening files is done completely in the user space, i.e. when restoring the subtree
of processes I first fork all the tasks in respective order, then open required files and 
then call execve() to restore registers and memory.

The checkpointing process is quite simple - all we need about processes can be read from /proc
except for several things - registers and private memory. In current implementation to get 
them I introduce the /proc/<pid>/dump file which produces the file that can be executed by the
described above binfmt. Additionally I introduce the /proc/<pid>/mfd/ dir with info about
mappings. It is populated with symbolc links with names equal to vma->vm_start and pointing to
mapped files (including anon shared which are tmpfs ones). Thus we can open some task's
/proc/<pid>/mfd/<address> link and find out the mapped file inode (to check for sharing) and
if required map one and read the contents of anon shared memory.

Other minor stuff is in patches and mostly tools. The set is for linux-2.6.39. The current
implementation is not yet well tested and has many other defects, but demonstrates the idea. 

What do you think? Does the support from kernel of the proposed type suit us?