CRIU

Here is a funny story for ya. Hackers and banks, all that stuff.My colleague +Andrey Wagin went into a bank. While waiting in a queue he was working on his laptop. A security guard in a uniform approached him and asked to turn the laptop off and put ... [More] it away. To a question why he answered that those small characters are scrolling down way too fast! [Less]

There are two APIs for CRIU functionality -- command line and RPC. The latter is provided by the CRIU service launched in the background and listening on a unix socket.Starting from the next release, we'll have an integration of this service into +systemd startup engine. Many thanks to +Shawn Landden for this!

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.

In the next release CRIU will provide one more API for ... programmers!Currently CRIU can only be run as a command-line tool. This is very handy to be used in scripts, but when it comes to C, Python, Java or any other programs, spawning a process and ... [More] exec()-uting the tools is possible, but not extremely elegant.So to make life easier we introduce a simple RPC API in CRIU. The RPC  is protocol-buffer-based, so it should be relatively easy to use one with any modern language. Two examples -- for C and Python -- of how to use the RPC are in $sources/test/rpc/ directory.Have fun! [Less]

Another thing that will be in 0.7 (quite soon, btw) is the support for "not too tricky" knots of shared mount-points.In Linux, mount-points can propagate changes to each other, based on "shared", "slave" and "master" relations between them. Before ... [More] 0.7 release, CRIU could not dump (and restore) such things, but this time we have investigated the issue and made preliminary support for such cases. What CRIU currently supports should be enough for dumping and restoring mount "knots" created by systemd! :)More work to be done here though, the ultimate goal is to make the "random mount tree" test (implemented, sits in the zdtm/ test suite) always pass. [Less]

Version 0.7 is out now!It includes some new features, like TUN devices, shared mounts and sigaltstack support, as well as quite a lot of bugfixes.But the main news item is, as of kernel 3.11, we have finally merged upstream all the critical ... [More] CRIU-related features! So from now on we will concentrate on the tool stability and performance, and we are no longer needed to sync our  releases with the kernel releases, as we did before.Therefore, the next release will come out earlier than in 2 months and will (should) contain a big bugfix set. New features will also be added, of course, we'll share our plans next time.Have fun! [Less]

We've promised lots of news, so here's one more.The amount of lines of CRIU code (without tests) is now above the 40K value! A historical note -- the v0.1 released about a year ago was two times smaller -- slightly bigger than 20K.

The closer to the 0.7 release we get, the more news we have :)Let's start with something that is already done -- now we have support for TUN devices, used by e.g. openVPN! We have checked a trivial configuration and the openvpn client running in a ... [More] container with active connection and configured tun device seems to survive the checkpoint/restore cycle.Unfortunately, one would need patched kernel for that to work, but the required patches are already in David Miller's net-next tree and will most likely get merged into 3.12 kernel.Say tuned, more news are coming soon! [Less]

One more talk about +CRIU is accepted :) This time it's LinuxCon Europe in Edinburgh.

And one more talk about +CRIU  in Europe.