CRIU

The 1.0 is out!About two months ago the last required kernel patch has found itsway upstream. Since then we have concentrated on the tool itselfmaking it work reliably and with as little ugly hacks as possible :)Right now we have quite a lot of ... [More] things to sort out, e.g. what plan for the 2.0 should be, what API modifications we need to make smooth integration with other projects, how to automate the live-migration use-case, how the release cycle should look like, do we need -stable branches, etc.But the first big goal is achieved -- the project is not just the "proof of concept" thing any more :)Have fun and stay tuned! [Less]

Here's +LWN.net recap of CRIU session at the recent Linux Kernel Summit event in Edinburgh, led by +Pavel Emelyanov (Please note that this a free link to lwn.net content which is currently subscribers-only. If you like lwn.net, please consider subscribing.)

We're looking forward towards v1.0!Some time ago CRIU has come to a state of all the kernel support it needed hit the upstream kernel (3.11). So we released v0.7 and concentrated on the tool itself.Then there was v0.8 with RPC service, a couple of ... [More] other new features and a lot of bugfixes. Now we have mostly developed the next chunk of changes we planned and are ready to tag the next version.We think it's time for 1.0.Although there is still a lot of stuff to do (and to fix), the major goal is achieved -- the functionality is really "in userspace", and we've had enough time to fix and polish stuff that was left for later. [Less]

Fun technical detail of CRIU internals.Right now the restoring code uses 4 different memory allocation techniques. We need two types of objects -- those used by CRIU process only and those, that are created in CRIU process but then are re-mapped into ... [More] the address space of a task being restored with proper pointers fixups. Both types have "sub-types" that reside either in CRIU private memory or in a memory shared between all CRIU processes.I wonder, will we ever need the 5th allocation type :) [Less]

In this hangout our project leader +Pavel Emelyanov will describe the current status of the project, highlighting the recent v1.1 release, and share the project plans for the foreseeable future. He will also answer all those burning questions you were so afraid to ask.

I was told, that CRIU is successfully used to live-migrate (i.e. with severl pre-dump iterations) a 48Gb application.Cool!

Hello, everyone!I'm glad to announce the 8th release of the checkpoint-restore tool. Though it was mostly bugfix release, we have added a couple of new features.You can find the changelog at http://criu.org/Download/criu/0.8and get the sourced from ... [More] http://download.openvz.org/criu/criu-0.8.tar.bz2It doesn't require any new kernel stuff, so you can run it on v3.11.This version of CRIU should be the last -RC for the v1.0. I really hope that we'll be able to resolve all the stuff we need within a month.See you in Edinburgh on LinuxCon :) [Less]

A video record of +Pavel Emelyanov 's talk about +CRIU on LinuxPlumbers conference in New Orleans.

So, Fedora-19's latest kernel is Linux-3.11, the newest CRIU package (v0.7) is in the process of getting there. This means, that very soon Fedora-19 will be the most feature-complete CRIU system!Oh, and Fedora-20 will be the same too :)

+Pavel Emelyanov was presenting +CRIU at the recent Linux Con in New Orleans. Here are the slides from the talk, mostly describing project history and current state, and possible CRIU applications.