CRIU - User contributions [en]

User:Sergey Bronnikov

2022-02-14T14:29:48Z

Sergey Bronnikov:

* Homepage: [https://bronevichok.ru/ bronevichok.ru]

Contacts

2019-11-03T10:11:16Z

Sergey Bronnikov: Fix markup

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

* [https://twitter.com/__criu__ CRIU twitter]
* [https://www.youtube.com/channel/UCeXb0oWYd7ZE-44TrTSWxmg Youtube channel]
* [https://lists.openvz.org/mailman/listinfo/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]]

Contacts

2019-11-03T10:10:28Z

Sergey Bronnikov: G+ has been shutdown some time ago

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

* [https://twitter.com/__criu__ CRIU twitter]
* [https://www.youtube.com/channel/UCeXb0oWYd7ZE-44TrTSWxmg Youtube channel]
* [https://lists.openvz.org/mailman/listinfo/criu Mailing list]
* IRC channels on Freenode:
** [https://webchat.freenode.net/?channels=#criu #criu] - developers talks. Logs are [available https://botbot.me/freenode/criu/].
** [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]]

Community

2017-01-15T21:43:12Z

Sergey Bronnikov: Fix CodeAurora site address

[[File:Community.jpg|right]]
CRIU is a community-driven project. It started by Virtuozzo kernel engineers in 2011, but the project potential was soon recognized by other companies and individuals and so they became actively involved. This article summarizes the current state of project community.

== Companies ==

This list includes companies and projects whose employees contributed at least 10 patches,
and is loosely ordered by the company's contribution amount.

* [https://virtuozzo.com/ Virtuozzo] employs a number of key developers and provides most of the project infrastructure
* [https://canonical.com/ Canonical] employs {{Commits by|Tycho Andersen|tych0}}
* [https://cloudlinux.com/ CloudLinux] employs {{Commits by|Ruslan Kuprieiev|efiop}}
* [https://ibm.com/linux IBM] employs {{Commits by|Laurent Dufour|ldu4}} and {{Commits by|Mike Rapoport|rppt}}
* [https://google.com/ Google] employs {{Commits by|Filipe Brandenburger|filbranden}} and {{Commits by|Saied Kazemi|SaiedKazemi}}
* [https://www.codeaurora.org/ CodeAurora] employs Christopher Covington
* [https://redhat.com/ Red Hat] employs {{Commits by|Oleg Nesterov|utrace}} and {{Commits by|Adrian Reber|adrianreber}}
* [https://samsung.com/ Samsung], [https://huawei.com/ Huawei] and others employs minor contributors
* [https://acronis.com/ Acronis] sponsors a few students working on the project

== Get involved ==

Start with subscribing to the [https://lists.openvz.org/mailman/listinfo/criu mailing list],
where most of the fun is taking place (yes we're old school).

If you are ready to send some actual patches, please don't do so via github, see [[how to submit patches]].

For other ways to be involved, see [[contacts]].

== See also ==

* [[History]]
* [[How to submit patches]]
* [[Contacts]]

== External links ==

* https://github.com/xemul/criu/graphs/contributors

[[Category: Development]]

News/events/past

2016-08-02T09:10:58Z

Sergey Bronnikov: meetup in Tel-Aviv

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

=== 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]]
'''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)

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

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

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)

== Black belt tech @ DockerCon 2016 ==
[[Image:Dockercon16.png|left|100px]]

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

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)

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

== Systor 2016 ==

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

'''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)

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

'''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)

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

'''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)

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

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

'''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)

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

'''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)

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

'''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)

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

'''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)

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

'''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)

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

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

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

'''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]]

'''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]]

'''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]]
'''Boston, MA, USA, June 5-6 2015'''

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

'''June 2015, On Air'''

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

Andrew Vagin will talk 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|128px]]

'''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]]

'''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]]
'''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]]

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

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

'''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]]

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

'''12:45 MSK, 15 Feb, 2014 '''

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

'''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]]

'''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]]

'''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]]

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

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

== CRIU talk at Fedora Virtualization Day ==
[[Image:russian_fedora.png|left|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|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">

== CRIU talk at FOSDEM ==
[[Image:Fosdem-2013.png|left|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 ==
[[Image:LinuxCon-logo.jpg|left|100px]]

'''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]]

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

[http://events.yandex.ru/talks/334/ CRIU: more than a live migration (incl. slides and video)]

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

News/events

2016-08-02T09:10:23Z

Sergey Bronnikov: meetup in Tel-Aviv is over

Articles

2016-07-24T20:40:44Z

Sergey Bronnikov: added links to the articles on RedHat site and LWN

<noinclude>Articles about the CRIU project:

</noinclude>
* 2016-07-20, Red Hat KnowledgeBase: [https://access.redhat.com/articles/2455211 CRIU - Checkpoint/Restore in user space]
* 2016-07-20, LWN.net: [https://lwn.net/SubscriberLink/694593/4d6291b3f727791a/ Quality in open source: testing CRIU]
* 2016-06-22, Usenix: [https://www.usenix.org/conference/atc16/technical-sessions/presentation/kashyap Instant OS Updates via Userspace Checkpoint-and-Restart]
* 2016-05-04: [http://lisas.de/~adrian/?p=1183 Lazy Process Migration]
* 2015-12-31, [http://kimh.github.io/blog/jp/criu/experiment-to-suspend-and-resume-docker-container-with-criu-jp/ Use the CRIU Docker container of stop / resume to the challenge]
* 2015-12-31, [http://blog.codeship.com/how-containers-will-change-the-game-server-hosting-industry/ How Containers Will Change the Game Server Hosting Industry]
* 2015-09-21, [http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/ Checkpoint and restore Docker container with CRIU]
* 2015-09-21, [https://blog.docker.com/2015/09/dolly-demo-linuxcon-runc/ Dolly Demo at LinuxCon: Rapid cloning of existing services with runC]
* 2015-09-10, [http://blog.tonicdev.com/2015/09/10/time-traveling-in-node.js-notebooks.html Time Traveling in Node.js Notebooks]
* 2015-01-01, [http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/openstack-at-cisco/linux-containers-white-paper-cisco-red-hat.pdfLinux Containers: Why They’re in Your Future and What Has to Happen First]
* 2015-07-01, [http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html How did the Quake demo from DockerCon Work?]
* 2015-05-06, [https://insights.ubuntu.com/2015/05/06/live-migration-in-lxd/ Live Migration in LXD] Ubuntu Insignts
* 2015-04-22, TuxDiary [http://tuxdiary.com/2015/04/22/dump-debug-resume-process-criu/ Dump, debug, resume process with criu]
* 2014-12-12, Symposium on Information and Communication Systems (SInCom 2014) [https://lisas.de/~adrian/proceedingsSInCom2014.pdf Checkpoint/Restore in User-Space with Open MPI]
* 2014-09-31, [http://www.reuters.com/article/wa-parallels-idUSnBw035202a+100+BSW20141103 Parallels Surpasses One Million Deployed Virtual Containers]
* 2014-08-01, ADMIN magazine: [http://www.admin-magazine.com/Archive/2014/22/Save-and-Restore-Linux-Processes-with-CRIU Save and Restore Linux Processes with CRIU]
* 2014-02-15, OCCAM Reproduce: [http://www.occamportal.org/papers/reproduce/reproduce14_paper_05.pdf Efficient, Accurate and Reproducible Simulation of Multi-Threaded Workloads] ([http://www.occamportal.org/slides/reproduce/reproduce14_slides_05.pdf slides])
* 2013-11-25, Phoronix: [http://www.phoronix.com/scan.php?page=news_item&px=MTUyNjE Checkpoint-Restore Hits v1.0: Freeze Your Linux Apps]
* 2013-11-25, LWN: [http://lwn.net/Articles/574918/ A note about 1.0]
* 2013-10-29, LWN: [http://lwn.net/Articles/572125/ Kernel summit report]
* 2013-02-01, A blog [http://www.anchor.com.au/blog/2013/02/overview-of-checkpoint-and-restore-live-migrating-processes-on-a-linux-system/ post] upon LCA-2013 talk.
* 2013-01-09, LWN: [http://lwn.net/Articles/531939/ Checkpoint/restore and signals]
* 2012-11-20, LWN: [http://lwn.net/Articles/525675/ LCE: Checkpoint/restore in user space: are we there yet?]
* 2012-05-01, LWN: [http://lwn.net/Articles/495304/ TCP connection repair]
* 2012-01-31, LWN: [http://lwn.net/Articles/478111/ Preparing for user-space checkpoint/restore]
* 2011-07-19, LWN: [http://lwn.net/Articles/452184/ Checkpoint/restart (mostly) in user space]
* 2012-07-24, OpenVZ blog: [http://openvz.livejournal.com/42414.html CRtools 0.1 released!]
* 2012-02-26, The International Symposium on Grids and Clouds (ISGC) [https://lisas.de/~adrian/ISGC-2012_031.pdf Pos (isgc 2012) 031 live process migration for load balancing and/or fault tolerance]

{| class="mw-collapsible <includeonly>mw-collapsed</includeonly>" border="0"
|-
! style="text-align: left; font-weight: normal" | in Russian:
|-
|
* 13.05.2016, Habrahabr: [https://habrahabr.ru/post/283504/ Особенности тестирования технологии C/R в Linux]
* 09.03.2016, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=44015 Выпуск CRIU 2.0, системы для сохранения и восстановления состояния процессов в Linux]
* 18.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43539 CRIU, путь от вызывающей непонимание разработки до интеграции в Red Hat Enterprise Linux]
* 09.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43489 Выпуск CRIU 1.8, системы для сохранения и восстановления состояния процессов в Linux]
* 09.09.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42939 Выпуск CRIU 1.7, системы для сохранения и восстановления состояния процессов в Linux]
* 25.08.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42850 Проект OpenVZ анонсировал новый компонент для миграции Linux контейнеров - P.Haul]
* 27.05.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42315 Статус интеграции проектов CRIU и Docker]
* 25.11.2013, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=38519 Анонс выхода 1.0]
* 28.04.2015, Типичный программист: [http://tproger.ru/interview/pavel-emelyanov/ Разработка ядра Linux — это общение в клубе по интересам]
* 22.04.2013, Habrahabr: [http://habrahabr.ru/post/177499/ В преддверии очередного релиза CRIU]
* 04.03.2013, IT-computer: [http://www.it-computer.com/osvaivaem-sistemu-zamorozki-processov-criu Осваиваем систему заморозки процессов CRIU]
* 28.09.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34958 CRIU 0.2 release]
* 05.11.2013, Xakep: [https://xakep.ru/2013/11/05/criu-manual/ Осваиваем систему заморозки процессов CRIU]
* 15.08.2013, Habrahabr: [http://habrahabr.ru/company/parallels/blog/190066/ «Разработка ядра Linux — это общение в клубе по интересам»]
* 01.10.2012, YaC 2012: [http://events.yandex.ru/events/yac/2012/talks/352/ больше, чем живая миграция для Linux контейнеров]
* 24.07.2012, Habrahabr: [http://habrahabr.ru/post/148413/ CRIU — новый амбициозный проект для сохранения и восстановления состояния процессов]
* 24.07.2012, Ru-OpenVZ blog: [http://ru-openvz.livejournal.com/5753.html Вышел первый релиз CRtools, версия 0.1]
* 24.07.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34408 Первый релиз CRtools, утилиты для заморозки и восстановления состояния процессов в Linux]
* 24.07.2012, LOR: [http://www.linux.org.ru/news/kernel/8021514 Вышел первый релиз CRtools, версия 0.1]
* Копипаста о v0.1 "CRIU / CRtools 0.1 — создание контрольных точек Linux-приложений и восстановление с них": [http://rosinvest.com/novosti/949423 Rosinvest], [http://www.nixp.ru/news/11854.html NIXP] [http://pcnews.ru/top/news/day/criu-crtools-linux-openvz-checkpoint-restore-in-userspace-cpt-system-90-10-lxc-org-398305.html PCNews]
|}

Articles

2016-07-11T13:27:52Z

Sergey Bronnikov: papers by Adrian Rebel

<noinclude>Articles about the CRIU project:

</noinclude>
* 2016-06-22, Usenix: [https://www.usenix.org/conference/atc16/technical-sessions/presentation/kashyap Instant OS Updates via Userspace Checkpoint-and-Restart]
* 2016-05-04: [http://lisas.de/~adrian/?p=1183 Lazy Process Migration]
* 2015-12-31, [http://kimh.github.io/blog/jp/criu/experiment-to-suspend-and-resume-docker-container-with-criu-jp/ Use the CRIU Docker container of stop / resume to the challenge]
* 2015-12-31, [http://blog.codeship.com/how-containers-will-change-the-game-server-hosting-industry/ How Containers Will Change the Game Server Hosting Industry]
* 2015-09-21, [http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/ Checkpoint and restore Docker container with CRIU]
* 2015-09-21, [https://blog.docker.com/2015/09/dolly-demo-linuxcon-runc/ Dolly Demo at LinuxCon: Rapid cloning of existing services with runC]
* 2015-09-10, [http://blog.tonicdev.com/2015/09/10/time-traveling-in-node.js-notebooks.html Time Traveling in Node.js Notebooks]
* 2015-01-01, [http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/openstack-at-cisco/linux-containers-white-paper-cisco-red-hat.pdfLinux Containers: Why They’re in Your Future and What Has to Happen First]
* 2015-07-01, [http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html How did the Quake demo from DockerCon Work?]
* 2015-05-06, [https://insights.ubuntu.com/2015/05/06/live-migration-in-lxd/ Live Migration in LXD] Ubuntu Insignts
* 2015-04-22, TuxDiary [http://tuxdiary.com/2015/04/22/dump-debug-resume-process-criu/ Dump, debug, resume process with criu]
* 2014-12-12, Symposium on Information and Communication Systems (SInCom 2014) [https://lisas.de/~adrian/proceedingsSInCom2014.pdf Checkpoint/Restore in User-Space with Open MPI]
* 2014-09-31, [http://www.reuters.com/article/wa-parallels-idUSnBw035202a+100+BSW20141103 Parallels Surpasses One Million Deployed Virtual Containers]
* 2014-08-01, ADMIN magazine: [http://www.admin-magazine.com/Archive/2014/22/Save-and-Restore-Linux-Processes-with-CRIU Save and Restore Linux Processes with CRIU]
* 2014-02-15, OCCAM Reproduce: [http://www.occamportal.org/papers/reproduce/reproduce14_paper_05.pdf Efficient, Accurate and Reproducible Simulation of Multi-Threaded Workloads] ([http://www.occamportal.org/slides/reproduce/reproduce14_slides_05.pdf slides])
* 2013-11-25, Phoronix: [http://www.phoronix.com/scan.php?page=news_item&px=MTUyNjE Checkpoint-Restore Hits v1.0: Freeze Your Linux Apps]
* 2013-11-25, LWN: [http://lwn.net/Articles/574918/ A note about 1.0]
* 2013-10-29, LWN: [http://lwn.net/Articles/572125/ Kernel summit report]
* 2013-02-01, A blog [http://www.anchor.com.au/blog/2013/02/overview-of-checkpoint-and-restore-live-migrating-processes-on-a-linux-system/ post] upon LCA-2013 talk.
* 2013-01-09, LWN: [http://lwn.net/Articles/531939/ Checkpoint/restore and signals]
* 2012-11-20, LWN: [http://lwn.net/Articles/525675/ LCE: Checkpoint/restore in user space: are we there yet?]
* 2012-05-01, LWN: [http://lwn.net/Articles/495304/ TCP connection repair]
* 2012-01-31, LWN: [http://lwn.net/Articles/478111/ Preparing for user-space checkpoint/restore]
* 2011-07-19, LWN: [http://lwn.net/Articles/452184/ Checkpoint/restart (mostly) in user space]
* 2012-07-24, OpenVZ blog: [http://openvz.livejournal.com/42414.html CRtools 0.1 released!]
* 2012-02-26, The International Symposium on Grids and Clouds (ISGC) [https://lisas.de/~adrian/ISGC-2012_031.pdf Pos (isgc 2012) 031 live process migration for load balancing and/or fault tolerance]

{| class="mw-collapsible <includeonly>mw-collapsed</includeonly>" border="0"
|-
! style="text-align: left; font-weight: normal" | in Russian:
|-
|
* 13.05.2016, Habrahabr: [https://habrahabr.ru/post/283504/ Особенности тестирования технологии C/R в Linux]
* 09.03.2016, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=44015 Выпуск CRIU 2.0, системы для сохранения и восстановления состояния процессов в Linux]
* 18.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43539 CRIU, путь от вызывающей непонимание разработки до интеграции в Red Hat Enterprise Linux]
* 09.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43489 Выпуск CRIU 1.8, системы для сохранения и восстановления состояния процессов в Linux]
* 09.09.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42939 Выпуск CRIU 1.7, системы для сохранения и восстановления состояния процессов в Linux]
* 25.08.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42850 Проект OpenVZ анонсировал новый компонент для миграции Linux контейнеров - P.Haul]
* 27.05.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42315 Статус интеграции проектов CRIU и Docker]
* 25.11.2013, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=38519 Анонс выхода 1.0]
* 28.04.2015, Типичный программист: [http://tproger.ru/interview/pavel-emelyanov/ Разработка ядра Linux — это общение в клубе по интересам]
* 22.04.2013, Habrahabr: [http://habrahabr.ru/post/177499/ В преддверии очередного релиза CRIU]
* 04.03.2013, IT-computer: [http://www.it-computer.com/osvaivaem-sistemu-zamorozki-processov-criu Осваиваем систему заморозки процессов CRIU]
* 28.09.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34958 CRIU 0.2 release]
* 05.11.2013, Xakep: [https://xakep.ru/2013/11/05/criu-manual/ Осваиваем систему заморозки процессов CRIU]
* 15.08.2013, Habrahabr: [http://habrahabr.ru/company/parallels/blog/190066/ «Разработка ядра Linux — это общение в клубе по интересам»]
* 01.10.2012, YaC 2012: [http://events.yandex.ru/events/yac/2012/talks/352/ больше, чем живая миграция для Linux контейнеров]
* 24.07.2012, Habrahabr: [http://habrahabr.ru/post/148413/ CRIU — новый амбициозный проект для сохранения и восстановления состояния процессов]
* 24.07.2012, Ru-OpenVZ blog: [http://ru-openvz.livejournal.com/5753.html Вышел первый релиз CRtools, версия 0.1]
* 24.07.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34408 Первый релиз CRtools, утилиты для заморозки и восстановления состояния процессов в Linux]
* 24.07.2012, LOR: [http://www.linux.org.ru/news/kernel/8021514 Вышел первый релиз CRtools, версия 0.1]
* Копипаста о v0.1 "CRIU / CRtools 0.1 — создание контрольных точек Linux-приложений и восстановление с них": [http://rosinvest.com/novosti/949423 Rosinvest], [http://www.nixp.ru/news/11854.html NIXP] [http://pcnews.ru/top/news/day/criu-crtools-linux-openvz-checkpoint-restore-in-userspace-cpt-system-90-10-lxc-org-398305.html PCNews]
|}

Articles

2016-06-24T12:44:32Z

Sergey Bronnikov: added article written by Kashayp

<noinclude>Articles about the CRIU project:

</noinclude>
* 2016-06-22, Usenix: [https://www.usenix.org/conference/atc16/technical-sessions/presentation/kashyap Instant OS Updates via Userspace Checkpoint-and-Restart]
* 2015-12-31, [http://kimh.github.io/blog/jp/criu/experiment-to-suspend-and-resume-docker-container-with-criu-jp/ Use the CRIU Docker container of stop / resume to the challenge]
* 2015-12-31, [http://blog.codeship.com/how-containers-will-change-the-game-server-hosting-industry/ How Containers Will Change the Game Server Hosting Industry]
* 2015-09-21, [http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/ Checkpoint and restore Docker container with CRIU]
* 2015-09-21, [https://blog.docker.com/2015/09/dolly-demo-linuxcon-runc/ Dolly Demo at LinuxCon: Rapid cloning of existing services with runC]
* 2015-09-10, [http://blog.tonicdev.com/2015/09/10/time-traveling-in-node.js-notebooks.html Time Traveling in Node.js Notebooks]
* 2015-01-01, [http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/openstack-at-cisco/linux-containers-white-paper-cisco-red-hat.pdfLinux Containers: Why They’re in Your Future and What Has to Happen First]
* 2015-07-01, [http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html How did the Quake demo from DockerCon Work?]
* 2015-05-06, [https://insights.ubuntu.com/2015/05/06/live-migration-in-lxd/ Live Migration in LXD] Ubuntu Insignts
* 2015-04-22, [http://tuxdiary.com/2015/04/22/dump-debug-resume-process-criu/ Dump, debug, resume process with criu] TuxDiary
* 2014-09-31, [http://www.reuters.com/article/wa-parallels-idUSnBw035202a+100+BSW20141103 Parallels Surpasses One Million Deployed Virtual Containers]
* 2014-08-01, ADMIN magazine: [http://www.admin-magazine.com/Archive/2014/22/Save-and-Restore-Linux-Processes-with-CRIU Save and Restore Linux Processes with CRIU]
* 2014-02-15, OCCAM Reproduce: [http://www.occamportal.org/papers/reproduce/reproduce14_paper_05.pdf Efficient, Accurate and Reproducible Simulation of Multi-Threaded Workloads] ([http://www.occamportal.org/slides/reproduce/reproduce14_slides_05.pdf slides])
* 2013-11-25, Phoronix: [http://www.phoronix.com/scan.php?page=news_item&px=MTUyNjE Checkpoint-Restore Hits v1.0: Freeze Your Linux Apps]
* 2013-11-25, LWN: [http://lwn.net/Articles/574918/ A note about 1.0]
* 2013-10-29, LWN: [http://lwn.net/Articles/572125/ Kernel summit report]
* 2013-02-01, A blog [http://www.anchor.com.au/blog/2013/02/overview-of-checkpoint-and-restore-live-migrating-processes-on-a-linux-system/ post] upon LCA-2013 talk.
* 2013-01-09, LWN: [http://lwn.net/Articles/531939/ Checkpoint/restore and signals]
* 2012-11-20, LWN: [http://lwn.net/Articles/525675/ LCE: Checkpoint/restore in user space: are we there yet?]
* 2012-05-01, LWN: [http://lwn.net/Articles/495304/ TCP connection repair]
* 2012-01-31, LWN: [http://lwn.net/Articles/478111/ Preparing for user-space checkpoint/restore]
* 2011-07-19, LWN: [http://lwn.net/Articles/452184/ Checkpoint/restart (mostly) in user space]
* 2012-07-24, OpenVZ blog: [http://openvz.livejournal.com/42414.html CRtools 0.1 released!]

{| class="mw-collapsible <includeonly>mw-collapsed</includeonly>" border="0"
|-
! style="text-align: left; font-weight: normal" | in Russian:
|-
|
* 13.05.2016, Habrahabr: [https://habrahabr.ru/post/283504/ Особенности тестирования технологии C/R в Linux]
* 09.03.2016, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=44015 Выпуск CRIU 2.0, системы для сохранения и восстановления состояния процессов в Linux]
* 18.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43539 CRIU, путь от вызывающей непонимание разработки до интеграции в Red Hat Enterprise Linux]
* 09.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43489 Выпуск CRIU 1.8, системы для сохранения и восстановления состояния процессов в Linux]
* 09.09.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42939 Выпуск CRIU 1.7, системы для сохранения и восстановления состояния процессов в Linux]
* 25.08.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42850 Проект OpenVZ анонсировал новый компонент для миграции Linux контейнеров - P.Haul]
* 27.05.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42315 Статус интеграции проектов CRIU и Docker]
* 25.11.2013, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=38519 Анонс выхода 1.0]
* 28.04.2015, Типичный программист: [http://tproger.ru/interview/pavel-emelyanov/ Разработка ядра Linux — это общение в клубе по интересам]
* 22.04.2013, Habrahabr: [http://habrahabr.ru/post/177499/ В преддверии очередного релиза CRIU]
* 04.03.2013, IT-computer: [http://www.it-computer.com/osvaivaem-sistemu-zamorozki-processov-criu Осваиваем систему заморозки процессов CRIU]
* 28.09.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34958 CRIU 0.2 release]
* 05.11.2013, Xakep: [https://xakep.ru/2013/11/05/criu-manual/ Осваиваем систему заморозки процессов CRIU]
* 15.08.2013, Habrahabr: [http://habrahabr.ru/company/parallels/blog/190066/ «Разработка ядра Linux — это общение в клубе по интересам»]
* 01.10.2012, YaC 2012: [http://events.yandex.ru/events/yac/2012/talks/352/ больше, чем живая миграция для Linux контейнеров]
* 24.07.2012, Habrahabr: [http://habrahabr.ru/post/148413/ CRIU — новый амбициозный проект для сохранения и восстановления состояния процессов]
* 24.07.2012, Ru-OpenVZ blog: [http://ru-openvz.livejournal.com/5753.html Вышел первый релиз CRtools, версия 0.1]
* 24.07.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34408 Первый релиз CRtools, утилиты для заморозки и восстановления состояния процессов в Linux]
* 24.07.2012, LOR: [http://www.linux.org.ru/news/kernel/8021514 Вышел первый релиз CRtools, версия 0.1]
* Копипаста о v0.1 "CRIU / CRtools 0.1 — создание контрольных точек Linux-приложений и восстановление с них": [http://rosinvest.com/novosti/949423 Rosinvest], [http://www.nixp.ru/news/11854.html NIXP] [http://pcnews.ru/top/news/day/criu-crtools-linux-openvz-checkpoint-restore-in-userspace-cpt-system-90-10-lxc-org-398305.html PCNews]
|}

Incremental dumps

2016-06-24T12:30:43Z

Sergey Bronnikov: typo fixed

If you're doing several dumps in a row, the 2nd and subsequent dumps can be speed up. Here's how:

== Create the first dump ==

# mkdir -p <path-to-images>/1/
# criu dump --tree <pid> --images-dir <path-to-images>/1/ --leave-running --track-mem

* Images are put into the <code>1/</code> sub-directory, since we're about to create the 2nd (and more) incremental dumps and it's handy to store them in this way;
* The <code>--leave-running</code> option is used to make criu not kill the tasks after dump, but let them run further;
* The <code>--track-mem</code> option makes criu ask kernel to monitor memory changes to optimize the subsequent dump.

== Create the second dump ==

# mkdir <path-to-images>/2/
# criu dump --tree <pid> --images-dir <path-to-images>/2/ --leave-running --track-mem --prev-images-dir ../1/

* Note, that the <code>--prev-images-dir</code> path is relative to the <code>--images-dir</code> one;
* Similarly the 3rd and all the other dumps can be created.

== Create the last dump ==

# mkdir <path-to-images>/N/
# criu dump --tree <pid> --images-dir <path-to-images>/N/ --track-mem --prev-images-dir ../N-1/

* No <code>--leave-running</code> option will make tasks be killed after dump;
* No need in memory tracking option.

== Restore ==

Now you can restore the processes from whatever images you want

# criu restore --images-dir <path-to-images>/ANY/

{{Note|After each (but the last) dump tasks continue running and thus can modify filesystem. CRIU doesn't snapshot filesystem and assumes, that proper filesystem state for restore is provided by user}}

== Data deduplication ==

After creation of such stack of images some data would get duplication in dumps. If you don't want to keep duplicates there's an ability to punch duplicate data from non-top images. There are two options for this.

; Deduplication action
: The <code>criu dedup</code> command would open the image directory and punch holes in the ''parent'' images in needed places

; Automatic deduplication while dumping
: The <code>--auto-dedup</code> option would cause every write to images with process' pages to go an punch holes in respective parent images.

The latter option appies to both <code>dump</code> and <code>page-server</code> actions and thus is extremely useful in [[disk-less migration]] scenario.

[[Category:HOWTO]]
[[Category:Memory]]

Incremental dumps

2016-06-24T12:30:17Z

Sergey Bronnikov: typo fixed

If you're doing several dumps in a row, the 2nd and subsequent dumps can be speed up. Here's how:

== Create the first dump ==

# mkdir -p <path-to-images>/1/
# criu dump --tree <pid> --images-dir <path-to-images>/1/ --leave-running --track-mem

* Images are put into the <code>1/</code> sub-directory, since we're about to create the 2nd (and more) incremental dumps and it's handy to store them in this way;
* The <code>--leave-running</code> option is used to make criu not kill the tasks after dump, but let them run further;
* The <code>--track-mem</code> option makes criu ask kernel to monitor memory changes to optimize the subsequent dump.

== Create the second dump ==

# mkdir <path-to-images>/2/
# criu dump --tree <pid> --images-dir <path-to-images>/2/ --leave-running --track-mem --prev-images-dir ../1/

* Note, that the <code>--prev-images-dir</code> path is relative to the <code>--images-dir</code> one;
* Similarly the 3rd and all the other dumps can be created.

== Create the last dump ==

# mkdir <path-to-images>/N/
# criu dump --tree <pid> --images-dir <path-to-images>/N/ --track-mem --prev-images-dir ../N-1/

* No <code>--leave-running</code> option will make tasks be killed after dump;
* No need in memory tracking option.

== Restore ==

Now you can restore the processes from whatever images you want

# criu restore --images-dir <path-to-images>/ANY/

{{Note|After each (but the last) dump tasks continue running and thus can modify filesystem. CRIU doesn't snapshot filesystem and assumes, that proper filesystem state for restore is provided by user}}

== Data deduplication ==

After creation of such stack of images some data would get duplication in dumps. If you don't want to keep duplicates there's an ability to punch duplicate data from non-top images. There are two options for this.

; Deduplication action
: The <code>crui dedup</code> command would open the image directory and punch holes in the ''parent'' images in needed places

; Automatic deduplication while dumping
: The <code>--auto-dedup</code> option would cause every write to images with process' pages to go an punch holes in respective parent images.

The latter option appies to both <code>dump</code> and <code>page-server</code> actions and thus is extremely useful in [[disk-less migration]] scenario.

[[Category:HOWTO]]
[[Category:Memory]]

Articles

2016-06-01T15:05:15Z

Sergey Bronnikov: add new articles about criu

<noinclude>Articles about the CRIU project:

</noinclude>
* 2015-12-31, [http://kimh.github.io/blog/jp/criu/experiment-to-suspend-and-resume-docker-container-with-criu-jp/ Use the CRIU Docker container of stop / resume to the challenge]
* 2015-12-31, [http://blog.codeship.com/how-containers-will-change-the-game-server-hosting-industry/ How Containers Will Change the Game Server Hosting Industry]
* 2015-09-21, [http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/ Checkpoint and restore Docker container with CRIU]
* 2015-09-21, [https://blog.docker.com/2015/09/dolly-demo-linuxcon-runc/ Dolly Demo at LinuxCon: Rapid cloning of existing services with runC]
* 2015-09-10, [http://blog.tonicdev.com/2015/09/10/time-traveling-in-node.js-notebooks.html Time Traveling in Node.js Notebooks]
* 2015-01-01, [http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/openstack-at-cisco/linux-containers-white-paper-cisco-red-hat.pdfLinux Containers: Why They’re in Your Future and What Has to Happen First]
* 2015-07-01, [http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html How did the Quake demo from DockerCon Work?]
* 2015-05-06, [https://insights.ubuntu.com/2015/05/06/live-migration-in-lxd/ Live Migration in LXD] Ubuntu Insignts
* 2015-04-22, [http://tuxdiary.com/2015/04/22/dump-debug-resume-process-criu/ Dump, debug, resume process with criu] TuxDiary
* 2014-09-31, [http://www.reuters.com/article/wa-parallels-idUSnBw035202a+100+BSW20141103 Parallels Surpasses One Million Deployed Virtual Containers]
* 2014-08-01, ADMIN magazine: [http://www.admin-magazine.com/Archive/2014/22/Save-and-Restore-Linux-Processes-with-CRIU Save and Restore Linux Processes with CRIU]
* 2014-02-15, OCCAM Reproduce: [http://www.occamportal.org/papers/reproduce/reproduce14_paper_05.pdf Efficient, Accurate and Reproducible Simulation of Multi-Threaded Workloads] ([http://www.occamportal.org/slides/reproduce/reproduce14_slides_05.pdf slides])
* 2013-11-25, Phoronix: [http://www.phoronix.com/scan.php?page=news_item&px=MTUyNjE Checkpoint-Restore Hits v1.0: Freeze Your Linux Apps]
* 2013-11-25, LWN: [http://lwn.net/Articles/574918/ A note about 1.0]
* 2013-10-29, LWN: [http://lwn.net/Articles/572125/ Kernel summit report]
* 2013-02-01, A blog [http://www.anchor.com.au/blog/2013/02/overview-of-checkpoint-and-restore-live-migrating-processes-on-a-linux-system/ post] upon LCA-2013 talk.
* 2013-01-09, LWN: [http://lwn.net/Articles/531939/ Checkpoint/restore and signals]
* 2012-11-20, LWN: [http://lwn.net/Articles/525675/ LCE: Checkpoint/restore in user space: are we there yet?]
* 2012-05-01, LWN: [http://lwn.net/Articles/495304/ TCP connection repair]
* 2012-01-31, LWN: [http://lwn.net/Articles/478111/ Preparing for user-space checkpoint/restore]
* 2011-07-19, LWN: [http://lwn.net/Articles/452184/ Checkpoint/restart (mostly) in user space]
* 2012-07-24, OpenVZ blog: [http://openvz.livejournal.com/42414.html CRtools 0.1 released!]

{| class="mw-collapsible <includeonly>mw-collapsed</includeonly>" border="0"
|-
! style="text-align: left; font-weight: normal" | in Russian:
|-
|
* 13.05.2016, Habrahabr: [https://habrahabr.ru/post/283504/ Особенности тестирования технологии C/R в Linux]
* 09.03.2016, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=44015 Выпуск CRIU 2.0, системы для сохранения и восстановления состояния процессов в Linux]
* 18.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43539 CRIU, путь от вызывающей непонимание разработки до интеграции в Red Hat Enterprise Linux]
* 09.12.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=43489 Выпуск CRIU 1.8, системы для сохранения и восстановления состояния процессов в Linux]
* 09.09.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42939 Выпуск CRIU 1.7, системы для сохранения и восстановления состояния процессов в Linux]
* 25.08.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42850 Проект OpenVZ анонсировал новый компонент для миграции Linux контейнеров - P.Haul]
* 27.05.2015, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=42315 Статус интеграции проектов CRIU и Docker]
* 25.11.2013, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=38519 Анонс выхода 1.0]
* 28.04.2015, Типичный программист: [http://tproger.ru/interview/pavel-emelyanov/ Разработка ядра Linux — это общение в клубе по интересам]
* 22.04.2013, Habrahabr: [http://habrahabr.ru/post/177499/ В преддверии очередного релиза CRIU]
* 04.03.2013, IT-computer: [http://www.it-computer.com/osvaivaem-sistemu-zamorozki-processov-criu Осваиваем систему заморозки процессов CRIU]
* 28.09.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34958 CRIU 0.2 release]
* 05.11.2013, Xakep: [https://xakep.ru/2013/11/05/criu-manual/ Осваиваем систему заморозки процессов CRIU]
* 15.08.2013, Habrahabr: [http://habrahabr.ru/company/parallels/blog/190066/ «Разработка ядра Linux — это общение в клубе по интересам»]
* 01.10.2012, YaC 2012: [http://events.yandex.ru/events/yac/2012/talks/352/ больше, чем живая миграция для Linux контейнеров]
* 24.07.2012, Habrahabr: [http://habrahabr.ru/post/148413/ CRIU — новый амбициозный проект для сохранения и восстановления состояния процессов]
* 24.07.2012, Ru-OpenVZ blog: [http://ru-openvz.livejournal.com/5753.html Вышел первый релиз CRtools, версия 0.1]
* 24.07.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34408 Первый релиз CRtools, утилиты для заморозки и восстановления состояния процессов в Linux]
* 24.07.2012, LOR: [http://www.linux.org.ru/news/kernel/8021514 Вышел первый релиз CRtools, версия 0.1]
* Копипаста о v0.1 "CRIU / CRtools 0.1 — создание контрольных точек Linux-приложений и восстановление с них": [http://rosinvest.com/novosti/949423 Rosinvest], [http://www.nixp.ru/news/11854.html NIXP] [http://pcnews.ru/top/news/day/criu-crtools-linux-openvz-checkpoint-restore-in-userspace-cpt-system-90-10-lxc-org-398305.html PCNews]
|}

Contacts

2016-03-29T13:06:07Z

Sergey Bronnikov: more criu channels

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

* [https://twitter.com/__criu__ CRIU twitter]
* [https://plus.google.com/+CriuOrg Google Plus page]
* [https://plus.google.com/communities/110000765381213982617 CRIU Community on Google Plus]
* [https://www.youtube.com/channel/UCeXb0oWYd7ZE-44TrTSWxmg Youtube channel]
* [https://lists.openvz.org/mailman/listinfo/criu Mailing list]
* IRC channels on Freenode:
** [https://webchat.freenode.net/?channels=#criu #criu] - developers talks. Logs are [available https://botbot.me/freenode/criu/].
** [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]]

Podcasts

2016-03-29T12:42:45Z

Sergey Bronnikov: Fizteh.Radio

<noinclude>Podcasts with the CRIU project:

</noinclude>
* 2016-03-24, Физтех.Радио: [https://vk.com/wall-24086381_35574 https://vk.com/wall-24086381_35574]
* 2015-07-17, DevZen podcast: [http://devzen.ru/episode-0050/ Episode 50]
* 2015-06-17, DevOps Дефлопе: [http://devopsdeflope.ru/posts/2015/021.html #021 - нет больше CP и AP]
* 2015-04-29, FLOSS Weekly: [http://twit.tv/show/floss-weekly/334 #334 CRIU]
* 2014-08-02, Radio-T: [http://www.radio-t.com/p/2014/08/02/podcast-403/ #433]
* 2014-12-22, Software Development podcast: [http://sdcast.ksdaemon.ru/2014/12/sdcast-15/ SDcast #15]
* 2014-12-04, DevOps Дефлопе: [http://devopsdeflope.ru/posts/2014/015.html 015 - Из самого сердца Докера]

Continuous integration

2016-03-25T11:34:37Z

Sergey Bronnikov: full RPi model name

== Travis CI ==
It's a public service, which is integrated with github and it's available for everyone.

We use "The Trusty beta Build Environment", where we have a full root access and an ability to execute docker containers. We use Travis to check compilation on x86_64, arm and aarch64. In addition, we execute all tests which have to work on the Trusty kernel.

The most interesting part of this work is how to build CRIU for other platforms on x86_64. We use [[Docker build|Docker]] to get a container for a target platform and qemu-static to run this container. qemu-static doesn't exist in all distributions, so we download it from Debian and extract binaries from it [https://github.com/xemul/criu/blob/master/scripts/build/extract-deb-pkg].

It's highly recommended to enable Travis for your criu repo on github and check changes before sending them to the mail list.

[https://travis-ci.org/xemul/criu.svg?branch=criu-dev]

== Mr Jenkins ==
We use Jenkins to execute tests. It works only for the criu upstream repo and isn't available to users yet. If you visit [https://ci.openvz.org/view/CRIU/], you will find more than dozen jobs for different configurations. We try to test all criu features.

Most part of jobs uses [ZDTM Test Suite]. There each test is a small program. Each job plays different scenarios with these tests:
* dump/restore
* dump/restore a few times
* dump/restore with a freezer cgroup
* dump only
* pre-dump, dump/restore with or without page-server
* pre-dump with duplication
* fault-injection
* collect code coverage

In addition, we execute our tests on linux-next to be sure that nobody breaks us in a kernel space.

[https://ci.openvz.org/job/CRIU/ https://ci.openvz.org/job/CRIU/job/CRIU-x86_64/branch/criu-dev/badge/icon?believeme=.png]
[https://ci.openvz.org/computer/CRIU-linux-next https://ci.openvz.org/job/CRIU-linux-next/badge/icon?believeme=.png]

== Targets ==

CRIU project supports different hardware architectures and we test all of supported archs. This chapter describes targets used for CRIU testing.

* Virtuozzo virtual machine (x86_64, Fedora?)

* [http://www.fit-pc.com/web/products/fitlet/ Fitlet] (x86_64, Fedora 23)

* Raspberry Pi Model B Rev 2 (ARM, Raspbian)

* Virtual machine (PPC64el)

== Links ==
* [https://travis-ci.org/xemul/criu Travis]
* [https://ci.openvz.org/view/CRIU/ Mr Jenkins]

[[Category: Development]]

Continuous integration

2016-03-23T12:59:42Z

Sergey Bronnikov: add targets

== Travis CI ==
It's a public service, which is integrated with github and it's available for everyone.

We use "The Trusty beta Build Environment", where we have a full root access and an ability to execute docker containers. We use Travis to check compilation on x86_64, arm and aarch64. In addition, we execute all tests which have to work on the Trusty kernel.

The most interesting part of this work is how to build CRIU for other platforms on x86_64. We use [[Docker build|Docker]] to get a container for a target platform and qemu-static to run this container. qemu-static doesn't exist in all distributions, so we download it from Debian and extract binaries from it [https://github.com/xemul/criu/blob/master/scripts/build/extract-deb-pkg].

It's highly recommended to enable Travis for your criu repo on github and check changes before sending them to the mail list.

== Mr Jenkins ==
We use Jenkins to execute tests. It works only for the criu upstream repo and isn't available to users yet. If you visit [https://ci.openvz.org/view/CRIU/], you will find more than dozen jobs for different configurations. We try to test all criu features.

Most part of jobs uses [ZDTM Test Suite]. There each test is a small program. Each job plays different scenarios with these tests:
* dump/restore
* dump/restore a few times
* dump/restore with a freezer cgroup
* dump only
* pre-dump, dump/restore with or without page-server
* pre-dump with duplication
* fault-injection
* collect code coverage

In addition, we execute our tests on linux-next to be sure that nobody breaks us in a kernel space.

[https://ci.openvz.org/computer/CRIU-x86_64/ https://ci.openvz.org/job/CRIU-x86_64/badge/icon?believeme=.png]
[https://ci.openvz.org/computer/CRIU-linux-next https://ci.openvz.org/job/CRIU-linux-next/badge/icon?believeme=.png]

== Targets ==

CRIU project supports different hardware architectures and we test all of supported archs. This chapter describes targets used for CRIU testing.

* Virtuozzo virtual machine (x86_64, Fedora?)

* [http://www.fit-pc.com/web/products/fitlet/ Fitlet] (x86_64, Fedora 23)

* Raspberry Pi (ARM, Raspbian)

* Virtual machine (PPC64el)

== Links ==
* [https://travis-ci.org/xemul/criu Travis]
* [https://ci.openvz.org/view/CRIU/ Mr Jenkins]

[[Category: Development]]

Integration

2016-03-23T12:22:42Z

Sergey Bronnikov: added Virtuozzo (as it is successor of OpenVZ0

CRIU is not so easy to be used as a standalone tool -- it works best integrated into other software. This page lists such software and provides details about the current status.

== OpenVZ ==
{{Status|in progress}}

Currently, vzctl supports CRIU for checkpoint/restore of upstream containers (i.e. when non-OpenVZ kernel is used). Commands <code>vzctl suspend</code> and <code>vzctl restore</code> fully work. Live migration doesn't work yet as it requires support for <code>vzctl suspend {--suspend, --dump, --kill, --restore}</code> which is not yet implemented as it requires a separate daemon to hold the state of a partially checkpointed container (or an ability from criu tool to do that).
* [https://openvz.org Project homepage]
* [http://git.openvz.org/?p=vzctl&a=search&h=HEAD&st=commit&s=CRIU%7Ccriu%7Ccrtools&sr=1 Relevant vzctl git commits]

== [[LXC]]/LXD ==
{{Status|ready}}
* [http://linuxcontainers.org Project homepage]
* The tools version 1.1.0 fully supports CRIU to C/R LXC containers
* [https://linuxcontainers.org/lxc/manpages/man1/lxc-checkpoint.1.html lxc-checkpoint man page]

== [[Docker]] ==
{{Status|in progress}}
* [https://docker.io Project homepage]
* Integration [https://github.com/docker/libcontainer/pull/204 efforts] done by Saied Kazemi from Google
* [https://github.com/docker/libcontainer/pull/479 Merged] into libcontainers

== CoreOS Rocket ==
{{Status|not started}}

== OpenMPI ==
{{Status|stalled}}
* Adrian Reber [https://lisas.de/~adrian/open-mpi.git/ did] first version of patches

== [[X applications|Wayland/Weston]] ==
{{Status|stalled}}
* Ruslan Kuprieiev plans to [http://lists.openvz.org/pipermail/criu/2015-January/018875.html patch] Weston to let CRIU C/R graphical apps

== The <code>file</code> utility ==
{{Status|ready}}
* Starting from v1.6 new images (v1.1) will be generated
* File utility starting from 5.23 [https://github.com/file/file/commit/0d76d756c5d7d5bbd4df6390b21b080f32665fd6 will support these]

== Systemd ==
{{Status|not started}}
Adrian suggested that

Migrating
processes from one system to another works, depending on the process,
pretty good. Migrating a process under systemd's control might be
possible by just killing the process on the source side but it cannot
become a child process of systemd on the destination of the migration
without systemd knowing how to restore a process and thus making it a
child process of systemd (--restore-sibling).

[[Category:Plans]]

== Screen/TMUX ==
{{Status|stalled}}

* Jerome [https://github.com/jpetazzo/critmux did] this some time ago

== Shell ==
{{Status|not started}}

It would be nice to have bash (or other shell) to launch criu with <code>--restore-sibling</code> option and get new kid processes from it.

== Subgraph OS ==
{{Status|not started}}

* [https://subgraph.com/sgos/index.en.html Subgraph OS] is a desktop operation system uses containers for users applications.

== Virtuozzo ==
{{Status|ready}}

* [https://openvz.org/Virtuozzo Virtuozzo] is a virtualization and automation solution built on top of OpenVZ.

Integration

2016-03-17T14:45:10Z

Sergey Bronnikov: added Subgraph OS

Main Page

2016-02-26T09:23:53Z

Sergey Bronnikov: more badges!

{{Download box|right}}
__NOTOC__
<big>Welcome to CRIU, a project to implement checkpoint/restore functionality for Linux in userspace.

Checkpoint/Restore In Userspace, or CRIU (pronounced kree-oo, IPA: /krɪʊ/, Russian: криу), is a software tool for Linux operating system. Using this tool, you can freeze a running application (or part of it) and checkpoint it to a hard drive as a collection of files. You can then use the files to restore and run the application from the point it was frozen at. The distinctive feature of the CRIU project is that it is mainly implemented in user space.

<div style="background-color: #f6f6f6; padding: 1em; text-align: left;" class="plainlinks">
[https://criu.org https://static.openvz.org/criu_88x31.gif] is a project of [https://openvz.org https://static.openvz.org/openvz_88x31.gif] and is supported by [https://www.odin.com https://static.openvz.org/odin_88x31.png], [https://www.acronis.com https://static.openvz.org/acronis_88x31.png], [https://mos.ru https://static.openvz.org/moscowgov_small.png] and [https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FZ8W4VU9AS2XL your donations].</div></big>
{{Like}}
<br clear="both">

<div style="float:left; width: 33%">

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

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

;[[:Category:API]]
: Collection of pages about CRIU's API.

;[[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 style="float:left; width: 33%; margin-left: 0.5%;">
== 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://criu.org/cov/ Code coverage results]
: Shows how zdtm run covers the criu code paths

;[[How to submit patches]]
:

</div>

<div style="float:right; width: 33%">
{{News block 2}}
</div>

<br clear="both">
<div style="float:left; width: 33%">
== [[:Category:Under the hood|Under the hood]] ==
* [[Checkpoint/Restore]]
* [[:Category:Network]]
* [[:Category:Files]]
* [[:Category:Memory]]
* [[Pending signals]]
* [[Stages of restoring]]
* [[Code blobs]]
* [[Comparison to other CR projects]]
</div>

<div style="float:left; width: 33%; margin-left: 0.5%;">
== External links ==
{{:Articles}}
</div>

<div style="float:left; width: 33%; margin-left: 0.5%;">
== Audio ==
{{:Podcasts}}
</div>

<div style="float:right; width: 33%;">
== Other ==
* Project [[history]]
* [[Logo]] description
* [[Events]]
* Join the [[CRIU acronym fun]]
</div>

Todo

2016-02-20T09:01:19Z

Sergey Bronnikov: make note more visible

{{note|This list is being transformed into the [https://github.com/xemul/criu/issues github issues]}}

{| class="wikitable sortable"
|-
! component
! task
! complexity
! potential/willing assignee
! comments
|-
| tests || automate process of measurement code coverage || easy || - || It is required to automate process of getting code coverage. We have code coverage results [http://criu.org/cov/ measured in 2012]. Would be nice to get up to date results on periodic basis and without manual actions.
|-
| crtools || Inherit resources, not restore || medium || - || Sigactions are restored for every task before it fork()-s. Then children check for the sa_action from their image matches to one it got from parent. Need to do the same for rlimits, maybe other resources too.
|-
| crtools || Implement [[restorer v2]] || hard (v2) || - ||
|-
| crtools || New images format || medium (v2) || - || See [[what's bad with V1 images]]
|-
| kernel/crtools || Tune the start-time of tasks || medium || - || When we restore tasks their start-time goes forward (since we create the new task effectively). Need to address this somehow, most likely with the [[time namespace]].
|-
| crtools || Support chroot-ed mount namespace || medium || - || If the root task lives in another mount namespace ''and'' has its root moved (with chroot()) CRIU dump fails with errors about inability to resolve files' paths. This is because CRIU treats the mount namespace's root as the init task's root which should be "/".
|-
| crtools || Non-stop memory (first?) pre-dump || medium || - || When reading only the memory we can avoid freezing tasks and draining memory with parasite. There's a system call named "read_process_vm" which can help us accessing the other task's memory. The disadvantage of this approach is the need for additional memory. We may control this behaviour by reading memory in chunks and not allocating to much of additional buffers.
|-
| kernel/crtools || Speed up fetching info about tasks || medium || Andrey Vagin || Using proc to get info about tasks is nice but too slow. We have measured that having socket-based engine that would fetch info about tasks from the kernel speeds things up significantly. So Andrey is working on the [[Task-diag]] patchset that would implement that.
|-
| kernel || Make pipes swappable || hard || - || When [[Memory dumping and restoring|pre-dumping]] memory we pull all the task's memory into pipe with vmsplice and then send it via network splicing the pages into socket. During this period all the memory is effectively pinned as pages in pipe are not swappable.
|-
| kernel/crtools || Adjust per-task/-container timers offsets || medium || - || Absolute timers differ on different nodes. When live migrating a task/container this difference may (and will) screw the timers up.
|-
| crtools || [[time namespace|Shift timers' timeouts]] according to the actual C-to-R delay || medium || - || If we pause tasks between C and R we, probably, need to adjust timers respectively. "Medium" complexity is because it's unclear ''what'' to do, not ''how''.
|-
| kernel/crtools || Put call to mmap into VDSO || easy || Cyrill || To put the [[parasite code]] into target process we modify its code to call the <code>mmap()</code> system call (and the unmodify it back) and put the parasite into new area. Oleg Nesterov suggests not to patch victim, but to always have one on VDSO.
|-
| crtools || [[Integration]] with other projects || hard || - || CRIU is not working great by itself. There's alway some specific about what user wants to dump. Integrating CRIU with other projects will make CRIU work at its best.
|-
| crtools || Restore tasks into fresh new pid namespace || easy || Kuprieiev Ruslan || When we dumped processes, it can be hard to restore it back, if they didn't live in a pid namespace, due to PIDs conflict. It would be nice to have the ability to ask CRIU to create the pid namespace for those guys and restore them there. A thing to worry about is this new namespace's init task.
|-
| crtools || Rollback tree state || medium || - || When we checkpointed process tree with -R option (let them run after checkpoint) we might want to return the tasks into checkpointed state on the same machine. Currently this can only be done by killing the processes and restoring them from scratch. If we could ask CRIU to restore the images ''into'' the ready processes that could speed things up, especially if carefully caring about [[memory changes tracking]].
|-
| crtools || Restore arbitrary mountpoints tree || hard || - || Linux kernel can construct tricky knows with [[mount points]]. We don't support arbitrary configuration of such things, only those that are in active use by software. Need to fix them up.
|-
| crtools || Lazy restore using [[userfaultfd]] || medium || xemul || It might make sense to restore tasks w/o putting all the memory into respective places. Instead, the VMAs in question can be marked as "lazy" and pages will get filled into them in the background and, upon demand, in the out-of-order manner. The functionality is related to lazy migration and seamless kernel update tasks.
|-
| crtools || [[Lazy migration]] using [[userfaultfd]] || medium || xemul || Lazy migration is when we move all the tasks on another node, but leave theirs memory on the source one. Not to allow tasks read garbage from empty address space we protect all of it as inaccessible. When tasks start reading/writing the mem they got page-fault-ed. With the userfaultfd technology it can be possible to intercept the #PF, pull the page from source node and map it into expected address.
|-
| crtools || Speed up [[logging]] || medium || Cyrill || Synchronous formatting and writes into log files slow things down. On the other hand turning logs off make it impossible to troubleshoot.
|-
| crtools || Sanitize [[logging]] messages || hard || - || Currently log messages are printed w/o any logic, it's hard to analize what has happened when CRIU fails. Need to improve that by, e.g. categorizing images and [[When C/R fails|explaining them]] in more details.
|-
| crtools || Page transfer filters || medium || - || The page-xfer engine just splices the pages from stealing pipes into socket. Packing or encrypting the data would be nice. Maybe it's purely for [[P.Haul]]?
|-
| crtools || TCP socket migration with changed IP || medium || - || It might make sense to migrate a tcp connection on a box with changed IP address _if_ both boxes are NAT-ed to the destination. We will then have to go to NAT box and fix the conntracks in that case and use CRIT images modifucation facilities.
|-
| crtools || [[Applying images]] || hard (v2) || xemul@ w/ students || Think about ability to take images and apply them to a living task(s). Like it was described in the "rollback" feature above. Another exampl -- repopulate fdtable according to data from image. Yet another use-case -- when doing partial migration (see below) we'll need to modify one part to switch from pipes to sockets. What else? With constant replication of tree state we can do incremental dumps on source node and apply those increments on pre-created replicas on the destination node.
|-
| crtools || Partial migration || hard || - || If tasks subtree has connections to the rest of the tree (e.g. with pipes of unix sockets) we try to detect this and refuse the dump. It should be possible to take part of the tree, migrating it somewhere and recreating the mentioned links with some other appropriate IPC channel. E.g. pipes with sockets, shared memory with distributed shared memory and so on.
|-
| crtools || Shared objects (mm/fs) support || medium || - || Things created with CLONE_FOO flags are not supported now (exception -- full threads). Now we have the kcmp syscall and can do it. The shared fdtable (CLONE_FILES) is supported, the next candidate is mm sharing, as we do know, that MySQL does so sometimes.
|-
| crtools || Smart paths resolution || hard || - || Files can be overmounted. In this case CRIU will refuse the dump saying that file is [[invisible files|not alive]] but inaccessible by its name. Need a way to resolve paths to such. There are two ways: 1. Move mounts, that overlap the desired path temporarily, then open the file, then move the mountpoint back. 2. When creating a new mount pre-open an fd keeping the mountpoint. Later, do accurate path resolve and call openat() on proper mountpoint fd.
|-
| kernel/crtools || [[TCP repair TODO|TCP repair fixes]] || hard || - || We can dump and restore live [[TCP connection]]. There are some issues with it, that should be fixed.
|-
| kernel || [[Seamless kernel upgrade]] || hard || xemul || Briefly — dump tasks (into memory), change the kernel w/ kexec, then restore tasks back. From the tasks and remote client perspective tasks has just stopped and then resumed on the newer kernel. Can be a good complement to the classic live-patching technology.
|-
| crtools || Restore arbitrary process tree || hard || - || Need to restore any process tree, which could be created with help PR_SET_CHILD_SUBREAPER and CLONE_PARENT. Processes can share other resources [http://man7.org/linux/man-pages/man2/clone2.2.html clone(2)]. Look at [https://github.com/xemul/criu/blob/master/test/zdtm/live/static/session02.c session02]. The task of resolving the given images into operations we might need to perform seem to be NP (not proven though).
|-
| crtools || C/R [[X applications]] || hard || Ruslan Kuprieiev || Dump/restore of graphical applications (see about [[integration]]). In case of X app part of its state is stored into the X-server. Need the way to fetch this state during dump and put this state back into the server on restore. Requires fixing the X-server software too.
|-
| crtools || More detailed RPC fail codes || easy || - || Currently only 3 typical errors are reported(see [https://github.com/xemul/criu/blob/master/include/cr-errno.h#L8 include/cr-errno.h]). Need to extend this set as currently it's hard to understand what has happened w/o analysing CRIU log files.
|-
| crtools || Make CRIU work on AArch32 with CONFIG_KUSER_HELPERS=n || medium || cov || CRIU currently fails on AArch32 kernels built with CONFIG_KUSER_HELPERS=n.
|-
| kernel || Fix VDSO remapping on non-x86 architectures || medium || Laurent Dufour, cov || However some architectures like PowerPC and ARM are keeping a reference to the VDSO base address to build the signal return stack frame by calling the VDSO sigreturn service. So once the VDSO has been moved, this reference is no more valid and the signal frame built later are not usable.
|-
| tests || Run many/all tests in "container" || medium || - || Currently we run zdtm tests one-by-one. It would be nice to run the all in one pseudo-container and C/R them as one big subtree.
|-
| tests || [[Fuzz testing|Trinity-like (fuzz) testing]] || hard || - || The existing suite is 99% functionality testing. Need more sophisticated testing -- take a process that has done a random set of actions, C/R one, check that all is OK. The latter is the most complicated thing.
|-
| tests/infrastructure || Run tests on patches sent to the mailing lists || medium || Ruslan Kuprieiev || It's quite typical that a set sent to the mailing list fails some tests. Need a robot that would monitor the list, check the patches and send the result back.
|-
| crtools || Set checkpoint tokens without recompiling || medium || - || Sometimes you need to call checkpoint in some particular point of the code. The way to do it now is to recompile app with criu_dump() call where needed. But it is quite a bummer to recompile, repackage and redistribute an app you want to c/r. It would be great if one could set a token in app source and then let criu find that point in running task and take a snapshot. The best way to do it might be in libcriu.
|-
| crtools || Large ghost files support || medium || - || If we have a large ghost (opened unlinked) file, it's inefficient to copy it to another node via CRIU dump. Need to migrate them independently, iteratively, using memory tracking.
|}

[[Category:Development]]
[[Category:Plans]]

Todo

2016-02-20T08:57:17Z

Sergey Bronnikov: Update link to GIT repo

This list is being transformed into the github issues @ https://github.com/xemul/criu/issues

{| class="wikitable sortable"
|-
! component
! task
! complexity
! potential/willing assignee
! comments
|-
| tests || automate process of measurement code coverage || easy || - || It is required to automate process of getting code coverage. We have code coverage results [http://criu.org/cov/ measured in 2012]. Would be nice to get up to date results on periodic basis and without manual actions.
|-
| crtools || Inherit resources, not restore || medium || - || Sigactions are restored for every task before it fork()-s. Then children check for the sa_action from their image matches to one it got from parent. Need to do the same for rlimits, maybe other resources too.
|-
| crtools || Implement [[restorer v2]] || hard (v2) || - ||
|-
| crtools || New images format || medium (v2) || - || See [[what's bad with V1 images]]
|-
| kernel/crtools || Tune the start-time of tasks || medium || - || When we restore tasks their start-time goes forward (since we create the new task effectively). Need to address this somehow, most likely with the [[time namespace]].
|-
| crtools || Support chroot-ed mount namespace || medium || - || If the root task lives in another mount namespace ''and'' has its root moved (with chroot()) CRIU dump fails with errors about inability to resolve files' paths. This is because CRIU treats the mount namespace's root as the init task's root which should be "/".
|-
| crtools || Non-stop memory (first?) pre-dump || medium || - || When reading only the memory we can avoid freezing tasks and draining memory with parasite. There's a system call named "read_process_vm" which can help us accessing the other task's memory. The disadvantage of this approach is the need for additional memory. We may control this behaviour by reading memory in chunks and not allocating to much of additional buffers.
|-
| kernel/crtools || Speed up fetching info about tasks || medium || Andrey Vagin || Using proc to get info about tasks is nice but too slow. We have measured that having socket-based engine that would fetch info about tasks from the kernel speeds things up significantly. So Andrey is working on the [[Task-diag]] patchset that would implement that.
|-
| kernel || Make pipes swappable || hard || - || When [[Memory dumping and restoring|pre-dumping]] memory we pull all the task's memory into pipe with vmsplice and then send it via network splicing the pages into socket. During this period all the memory is effectively pinned as pages in pipe are not swappable.
|-
| kernel/crtools || Adjust per-task/-container timers offsets || medium || - || Absolute timers differ on different nodes. When live migrating a task/container this difference may (and will) screw the timers up.
|-
| crtools || [[time namespace|Shift timers' timeouts]] according to the actual C-to-R delay || medium || - || If we pause tasks between C and R we, probably, need to adjust timers respectively. "Medium" complexity is because it's unclear ''what'' to do, not ''how''.
|-
| kernel/crtools || Put call to mmap into VDSO || easy || Cyrill || To put the [[parasite code]] into target process we modify its code to call the <code>mmap()</code> system call (and the unmodify it back) and put the parasite into new area. Oleg Nesterov suggests not to patch victim, but to always have one on VDSO.
|-
| crtools || [[Integration]] with other projects || hard || - || CRIU is not working great by itself. There's alway some specific about what user wants to dump. Integrating CRIU with other projects will make CRIU work at its best.
|-
| crtools || Restore tasks into fresh new pid namespace || easy || Kuprieiev Ruslan || When we dumped processes, it can be hard to restore it back, if they didn't live in a pid namespace, due to PIDs conflict. It would be nice to have the ability to ask CRIU to create the pid namespace for those guys and restore them there. A thing to worry about is this new namespace's init task.
|-
| crtools || Rollback tree state || medium || - || When we checkpointed process tree with -R option (let them run after checkpoint) we might want to return the tasks into checkpointed state on the same machine. Currently this can only be done by killing the processes and restoring them from scratch. If we could ask CRIU to restore the images ''into'' the ready processes that could speed things up, especially if carefully caring about [[memory changes tracking]].
|-
| crtools || Restore arbitrary mountpoints tree || hard || - || Linux kernel can construct tricky knows with [[mount points]]. We don't support arbitrary configuration of such things, only those that are in active use by software. Need to fix them up.
|-
| crtools || Lazy restore using [[userfaultfd]] || medium || xemul || It might make sense to restore tasks w/o putting all the memory into respective places. Instead, the VMAs in question can be marked as "lazy" and pages will get filled into them in the background and, upon demand, in the out-of-order manner. The functionality is related to lazy migration and seamless kernel update tasks.
|-
| crtools || [[Lazy migration]] using [[userfaultfd]] || medium || xemul || Lazy migration is when we move all the tasks on another node, but leave theirs memory on the source one. Not to allow tasks read garbage from empty address space we protect all of it as inaccessible. When tasks start reading/writing the mem they got page-fault-ed. With the userfaultfd technology it can be possible to intercept the #PF, pull the page from source node and map it into expected address.
|-
| crtools || Speed up [[logging]] || medium || Cyrill || Synchronous formatting and writes into log files slow things down. On the other hand turning logs off make it impossible to troubleshoot.
|-
| crtools || Sanitize [[logging]] messages || hard || - || Currently log messages are printed w/o any logic, it's hard to analize what has happened when CRIU fails. Need to improve that by, e.g. categorizing images and [[When C/R fails|explaining them]] in more details.
|-
| crtools || Page transfer filters || medium || - || The page-xfer engine just splices the pages from stealing pipes into socket. Packing or encrypting the data would be nice. Maybe it's purely for [[P.Haul]]?
|-
| crtools || TCP socket migration with changed IP || medium || - || It might make sense to migrate a tcp connection on a box with changed IP address _if_ both boxes are NAT-ed to the destination. We will then have to go to NAT box and fix the conntracks in that case and use CRIT images modifucation facilities.
|-
| crtools || [[Applying images]] || hard (v2) || xemul@ w/ students || Think about ability to take images and apply them to a living task(s). Like it was described in the "rollback" feature above. Another exampl -- repopulate fdtable according to data from image. Yet another use-case -- when doing partial migration (see below) we'll need to modify one part to switch from pipes to sockets. What else? With constant replication of tree state we can do incremental dumps on source node and apply those increments on pre-created replicas on the destination node.
|-
| crtools || Partial migration || hard || - || If tasks subtree has connections to the rest of the tree (e.g. with pipes of unix sockets) we try to detect this and refuse the dump. It should be possible to take part of the tree, migrating it somewhere and recreating the mentioned links with some other appropriate IPC channel. E.g. pipes with sockets, shared memory with distributed shared memory and so on.
|-
| crtools || Shared objects (mm/fs) support || medium || - || Things created with CLONE_FOO flags are not supported now (exception -- full threads). Now we have the kcmp syscall and can do it. The shared fdtable (CLONE_FILES) is supported, the next candidate is mm sharing, as we do know, that MySQL does so sometimes.
|-
| crtools || Smart paths resolution || hard || - || Files can be overmounted. In this case CRIU will refuse the dump saying that file is [[invisible files|not alive]] but inaccessible by its name. Need a way to resolve paths to such. There are two ways: 1. Move mounts, that overlap the desired path temporarily, then open the file, then move the mountpoint back. 2. When creating a new mount pre-open an fd keeping the mountpoint. Later, do accurate path resolve and call openat() on proper mountpoint fd.
|-
| kernel/crtools || [[TCP repair TODO|TCP repair fixes]] || hard || - || We can dump and restore live [[TCP connection]]. There are some issues with it, that should be fixed.
|-
| kernel || [[Seamless kernel upgrade]] || hard || xemul || Briefly — dump tasks (into memory), change the kernel w/ kexec, then restore tasks back. From the tasks and remote client perspective tasks has just stopped and then resumed on the newer kernel. Can be a good complement to the classic live-patching technology.
|-
| crtools || Restore arbitrary process tree || hard || - || Need to restore any process tree, which could be created with help PR_SET_CHILD_SUBREAPER and CLONE_PARENT. Processes can share other resources [http://man7.org/linux/man-pages/man2/clone2.2.html clone(2)]. Look at [https://github.com/xemul/criu/blob/master/test/zdtm/live/static/session02.c session02]. The task of resolving the given images into operations we might need to perform seem to be NP (not proven though).
|-
| crtools || C/R [[X applications]] || hard || Ruslan Kuprieiev || Dump/restore of graphical applications (see about [[integration]]). In case of X app part of its state is stored into the X-server. Need the way to fetch this state during dump and put this state back into the server on restore. Requires fixing the X-server software too.
|-
| crtools || More detailed RPC fail codes || easy || - || Currently only 3 typical errors are reported(see [https://github.com/xemul/criu/blob/master/include/cr-errno.h#L8 include/cr-errno.h]). Need to extend this set as currently it's hard to understand what has happened w/o analysing CRIU log files.
|-
| crtools || Make CRIU work on AArch32 with CONFIG_KUSER_HELPERS=n || medium || cov || CRIU currently fails on AArch32 kernels built with CONFIG_KUSER_HELPERS=n.
|-
| kernel || Fix VDSO remapping on non-x86 architectures || medium || Laurent Dufour, cov || However some architectures like PowerPC and ARM are keeping a reference to the VDSO base address to build the signal return stack frame by calling the VDSO sigreturn service. So once the VDSO has been moved, this reference is no more valid and the signal frame built later are not usable.
|-
| tests || Run many/all tests in "container" || medium || - || Currently we run zdtm tests one-by-one. It would be nice to run the all in one pseudo-container and C/R them as one big subtree.
|-
| tests || [[Fuzz testing|Trinity-like (fuzz) testing]] || hard || - || The existing suite is 99% functionality testing. Need more sophisticated testing -- take a process that has done a random set of actions, C/R one, check that all is OK. The latter is the most complicated thing.
|-
| tests/infrastructure || Run tests on patches sent to the mailing lists || medium || Ruslan Kuprieiev || It's quite typical that a set sent to the mailing list fails some tests. Need a robot that would monitor the list, check the patches and send the result back.
|-
| crtools || Set checkpoint tokens without recompiling || medium || - || Sometimes you need to call checkpoint in some particular point of the code. The way to do it now is to recompile app with criu_dump() call where needed. But it is quite a bummer to recompile, repackage and redistribute an app you want to c/r. It would be great if one could set a token in app source and then let criu find that point in running task and take a snapshot. The best way to do it might be in libcriu.
|-
| crtools || Large ghost files support || medium || - || If we have a large ghost (opened unlinked) file, it's inefficient to copy it to another node via CRIU dump. Need to migrate them independently, iteratively, using memory tracking.
|}

[[Category:Development]]
[[Category:Plans]]

C API

2016-02-20T08:56:25Z

Sergey Bronnikov: Update link to GIT repo

'''libcriu''' is a C API for CRIU, which is a simple wrapper around our [[RPC]]. Although you can use [[RPC]] directly, libcriu is a wrapper providing the interface that is much easier to use from C code. Note that [[RPC]] is supported in the first place, and if you want the most recent set of features you should probably use [[RPC]] directly.

== Introduction ==

libcriu functions are defined in <code>lib/criu.h</code>.

To create a library <code>lib/libcriu.so</code>, run <code>make</code> in the main directory.

{{Warning|The library is not thread- and fork- safe}}

== Preparation ==

=== init options ===

Call <code>int criu_init_opts(void)</code> to initialize request options.

Note: it should be called before using any other functions from libcriu, except <code>criu_check()</code>. Also you should use it to reinitialize options. It returns 0 on success and -1 on fail.

=== set service address ===

Use <code>void criu_set_service_address(char *address)</code> to specify path to a CRIU service socket. Call it with NULL to make libcriu use the default address (currently <code>/var/run/criu_service.socket</code>).

=== set dump/restore options ===
Use <code>criu_set_*</code> functions to setup dump/restore options.

<source lang="c">
void criu_set_pid(int pid);
void criu_set_images_dir_fd(int fd); /* must be set for dump/restore */
void criu_set_leave_running(bool leave_running);
void criu_set_ext_unix_sk(bool ext_unix_sk);
void criu_set_tcp_established(bool tcp_established);
void criu_set_evasive_devices(bool evasive_devices);
void criu_set_shell_job(bool shell_job);
void criu_set_file_locks(bool file_locks);
void criu_set_log_level(int log_level);
void criu_set_log_file(char *log_file);
</source>

If no pid is set on dump, CRIU will dump the calling process itself.
{{Note|If a calling process is not run as root, the whole process tree to be dumped must have the same uid, otherwise CRIU refuses to dump. See [[Usage#Security]].}}

{{Note|<code>images_dir_fd</code> is '''required''' at dump/restore, all other options might be left unset.
The client must open directory for/with images by itself and set <code>images_dir_fd</code> to the opened directory fd.
CRIU will open <code>/proc/''client_pid''/fd/''images_dir_fd''</code>, so it will work even if the client is in another namespace.}}

The logic of setting request is the same as when setting options in console. Here is an example:

# criu restore -D /path/to/imgs_dir -v4 -o restore.log

is equal to:
<source lang="c">
criu_init_opts();
criu_set_service_address("/path/to/criu/service/socket");

int fd = open("/path/to/imgs_dir", O_DIRECTORY);
criu_set_images_dir_fd(fd);

criu_set_log_file("restore.log");
criu_set_log_level(4);

criu_restore();
</source>

== Operations ==

Use the following functions to perform CRIU actions.

=== check ===

int criu_check(void);

=== dump ===

int criu_dump(void);

=== restore ===

int criu_restore(void);

=== restore as a child ===

This one is special. It will fork and exec criu swrk (Service WoRKer) to allow restoring process as a caller child. Calling "exec" implies some restrictions, as, for example, one should make sure, that criu binary is present in PATH and has suid bit set (see [[Usage#Security]]).

int criu_restore_child(void);

=== Return values ===

Here is a table of return and errno values of the above functions:
{| class="wikitable"
|-
! Return value
! errno
! Description

|-
| 0
| undefined
| Success

|-
| >0
| undefined
| Success (<code>criu_restore()</code> only)

|-
| -EBADE
| RPC error (if provided(see [https://github.com/xemul/criu/blob/master/include/cr-errno.h#L8 include/cr-errno.h]), 0 otherwise)
| RPC has returned fail.

|-
| -ECONNREFUSED
| errno
| Unable to connect to CRIU.

|-
| -ECOMM
| errno
| Unable to send/recv msg to/from CRIU.

|-
| -EINVAL
| undefined
| CRIU doesn't support this type of request. You should probably update CRIU.

|-
| -EBADMSG
| undefined
| Unexpected response from CRIU. You should probably update CRIU.
|}

== Examples ==

You could find example of using libcriu at [https://github.com/xemul/criu/tree/master/test/libcriu test/libcriu].

[[Category: API]]

Installation

2016-02-20T08:55:25Z

Sergey Bronnikov: Update link to GIT repo

<code>criu</code> is an utility to checkpoint/restore a process tree. This page describes how to manually build and install prerequisites and the tool itself.

== Installing from packages ==

Some distributions provide ready-to-use [[packages]]. If no, or the CRIU version you want is not yet there, you will need to get CRIU sources and compile it.

== Obtaining CRIU Source ==

You can download the source code as a release tarball or sync the [https://github.com/xemul/criu git repository]. If you plan to modify CRIU sources the latter way is highly recommended.

=== Getting source tarball ===
: {{Latest release}}

=== Cloning git repository ===
git clone https://github.com/xemul/criu

== Dependencies ==

=== Compiler and C Library ===

CRIU is mostly written in C and the build system is based on Makefiles. Thus just install standard <code>gcc</code> and <code>make</code> packages (on Debian, <code>[https://packages.debian.org/build-essential build-essential]</code> will pull in both at once).

If you are cross compiling for ARM, use distribution packages or download prebuilt toolchains from Linaro.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Downloading Linaro toolchains
<div class="mw-collapsible-content">
sudo apt-get install lib32stdc++6 lib32z1 # These are ia32 binaries
mkdir -p deps/`uname -m`-linux-gnu
cd deps
wget http://releases.linaro.org/14.09/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz
tar --strip=1 -C `uname -m`-linux-gnu -xf gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz
wget http://releases.linaro.org/14.09/components/toolchain/binaries/gcc-linaro-aarch64-linux-gnu-4.9-2014.09_linux.tar.xz
tar --strip=1 -C `uname -m`-linux-gnu -xf gcc-linaro-aarch64-linux-gnu-4.9-2014.09_linux.tar.xz
cd ..
</div>
</div>

=== Protocol Buffers ===

CRIU uses the [https://developers.google.com/protocol-buffers/ Google Protocol Buffers] to read and write [[images]] and thus requires [https://github.com/protobuf-c/protobuf-c C language bindings]. The <code>protoc</code> tool is required at build time and the <code>libprotobuf-c.so</code> shared object is required at build and run time. [[CRIT]] also uses python language bindings for protocol buffers and requires the <code>descriptor.proto</code> file typically provided by a distribution's protobuf development package.

==== Distribution Packages ====
The easiest way is to install distribution packages.

* RPM package names
** <code>protobuf</code>
** <code>protobuf-c</code>
** <code>protobuf-c-devel</code>
** <code>protobuf-compiler</code>
** <code>protobuf-devel</code>
** <code>protobuf-python</code>
* Debian package names
** <code>libprotobuf-dev</code>
** <code>libprotobuf-c0-dev</code>
** <code>protobuf-c-compiler</code>
** <code>protobuf-compiler</code>
** <code>python-protobuf</code>

==== Building Protocol Buffers From Source ====
If you would like to build from source, you can use the following commands to obtain the source code repositories, configure, and build the code. On a Debian based system, you may have to install <code>autoconf curl g++ libtool</code> packages first.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
To build protobuf
<div class="mw-collapsible-content">
cd deps
git clone https://github.com/google/protobuf.git protobuf
cd protobuf
./autogen.sh
./configure --prefix=`pwd`/../`uname -m`-linux-gnu
make
make install
cd ../..
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
To build protobuf-c
<div class="mw-collapsible-content">
cd deps
git clone https://github.com/protobuf-c/protobuf-c.git protobuf-c
cd protobuf-c
./autogen.sh
mkdir ../pbc-`uname -m`
cd ../pbc-`uname -m`
../protobuf-c/configure --prefix=`pwd`/../`uname -m`-linux-gnu \
PKG_CONFIG_PATH=`pwd`/../`uname -m`-linux-gnu/lib/pkgconfig
make
make install
cd ../..
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
To cross-compile for ARM some more tricks will be required.
<div class="mw-collapsible-content">
For ARMv7

cd deps
mkdir -p pbc-arm
cd pbc-arm
../protobuf-c/configure --host=arm-linux-gnueabihf --prefix=`pwd`/../arm-linux-gnueabihf \
--disable-protoc PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
make PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
make install PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
cd ../..

For ARM8

cd deps
mkdir -p pbc-aarch64
cd pbc-aarch64
../protobuf-c/configure --host=aarch64-linux-gnu --prefix=`pwd`/../aarch64-linux-gnu \
--disable-protoc PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
make PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
make install PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
cd ../..
</div>
</div>

=== Other deps ===

* <code>python-ipaddr</code> is used by CRIT to pretty-print ip.
* If <code>libbsd</code> available, CRIU will be compiled with setproctitle() support. It will allow to make process titles of service workers to be more verbose.
* The iproute2 tool version 3.5.0 or higher is needed for dumping network namespaces. The latest one can be cloned from [http://git.kernel.org/?p=linux/kernel/git/shemminger/iproute2.git;a=summary iproute2]. It should be compiled and a path to ip written in the environment variable <code>CR_IP_TOOL</code>.
* If you would like to use <code>make test</code> you should install <code>libaio-devel</code> and <code>libcap-devel</code>.

== Linux Kernel ==

Linux kernel v3.11 or newer is required, with some specific options set. If your distribution does not provide needed kernel, you might want to compile one yourself.

=== Configuring the kernel ===

Most likely the first thing to enable is the <code>CONFIG_EXPERT=y</code> (General setup -> Configure standard kernel features (expert users)) option, which on x86_64 depends on the <code>CONFIG_EMBEDDED=y</code> (General setup -> Embedded system) one (welcome to Kconfig reverse chains hell).

The following options must be enabled for CRIU to work:

* ''General setup'' options
** <code>CONFIG_CHECKPOINT_RESTORE=y</code> (Checkpoint/restore support)
** <code>CONFIG_NAMESPACES=y</code> (Namespaces support)
** <code>CONFIG_UTS_NS=y</code> (Namespaces support -> UTS namespace)
** <code>CONFIG_IPC_NS=y</code> (Namespaces support -> IPC namespace)
** <code>CONFIG_PID_NS=y</code> (Namespaces support -> PID namespaces)
** <code>CONFIG_NET_NS=y</code> (Namespaces support -> Network namespace)
** <code>CONFIG_FHANDLE=y</code> (Open by fhandle syscalls)
** <code>CONFIG_EVENTFD=y</code> (Enable eventfd() system call)
** <code>CONFIG_EPOLL=y</code> (Enable eventpoll support)
* ''Networking support -> Networking options'' options for sock-diag subsystem
** <code>CONFIG_UNIX_DIAG=y</code> (Unix domain sockets -> UNIX: socket monitoring interface)
** <code>CONFIG_INET_DIAG=y</code> (TCP/IP networking -> INET: socket monitoring interface)
** <code>CONFIG_INET_UDP_DIAG=y</code> (TCP/IP networking -> INET: socket monitoring interface -> UDP: socket monitoring interface)
** <code>CONFIG_PACKET_DIAG=y</code> (Packet socket -> Packet: sockets monitoring interface)
** <code>CONFIG_NETLINK_DIAG=y</code> (Netlink socket -> Netlink: sockets monitoring interface)
* Other options
** <code>CONFIG_INOTIFY_USER=y</code> (File systems -> Inotify support for userspace)
** <code>CONFIG_IA32_EMULATION=y</code> (x86 only) (Executable file formats -> Emulations -> IA32 Emulation)

For some [[usage scenarios]] there is an ability to track memory changes and produce [[incremental dumps]]. Need to enable the <code>CONFIG_MEM_SOFT_DIRTY=y</code> (optional) (Processor type and features -> Track memory changes).

Note we also have our [[custom kernel]], which might contain some experimental CRIU related patches.

== Building CRIU From Source ==

=== Native Compilation ===
Simply run <code>make</code> in the CRIU source directory.

=== Compilation in Docker container ===

There's a ''docker-build'' target in Makefile which builds CRIU in Ubuntu Docker container. Just run <code>make docker-build</code> and that's it.

=== Non-standard compilation ===

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Building natively, but specifying built dependencies manually
<div class="mw-collapsible-content">
cd deps
rsync -a --exclude=.git --exclude=deps .. criu-`uname -m`
cd criu-`uname -m`
make \
USERCFLAGS="-I`pwd`/../`uname -m`-linux-gnu/include -L`pwd`/../`uname -m`-linux-gnu/lib" \
PATH="`pwd`/../`uname -m`-linux-gnu/bin:$PATH"
sudo LD_LIBRARY_PATH=`pwd`/../`uname -m`-linux-gnu/lib ./criu check
cd ../..
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Cross Compilation for ARM
<div class="mw-collapsible-content">
ARMv7
cd deps
rsync -a --exclude=.git --exclude=deps .. criu-arm
cd criu-arm
make \
ARCH=arm \
CROSS_COMPILE=`pwd`/../`uname -m`-linux-gnu/bin/arm-linux-gnueabihf- \
USERCFLAGS="-I`pwd`/../arm-linux-gnueabihf/include -L`pwd`/../arm-linux-gnueabihf/lib" \
PATH="`pwd`/../`uname -m`-linux-gnu/bin:$PATH"
cd ../..

ARMv8
cd deps
rsync -a --exclude=.git --exclude=deps .. criu-aarch64
cd criu-aarch64
make \
ARCH=aarch64 \
CROSS_COMPILE=`pwd`/../`uname -m`-linux-gnu/bin/aarch64-linux-gnu- \
USERCFLAGS="-I`pwd`/../aarch64-linux-gnu/include -L`pwd`/../aarch64-linux-gnu/lib" \
PATH="`pwd`/../`uname -m`-linux-gnu/bin:$PATH"
cd ../..
</div>
</div>

== Installation ==
CRIU works perfectly even when run from the sources directory (with the "./criu" command), but if you want to have in standard paths run <code>make install</code>.

You may need to install the following packages to generate docs in Debian-based OS's to avoid errors from install-man:
* <code>asciidoc</code>
* <code>xmlto</code>

== Checking That It Works ==

First thing to do is to run <code>criu check --ms</code>.

At the end it should say "Looks OK", if it doesn't the messages on the screen explain what functionality is missing. If you're using our custom kernel, then the <code>--ms</code> option should not be used, in this case CRIU would check for ''all'' the kernel features to work.

You can then try running the [[ZDTM Test Suite]] which sits in the <code>tests/zdtm/</code> directory.

== Further reading ==

Please see [[Usage]] and [[Advanced usage]], as well as [[:Category:HOWTO]].

[[Category:HOWTO]]

News/events

2016-02-01T15:06:11Z

Sergey Bronnikov: Removed FOSDEM

News/events/past

2016-02-01T15:06:01Z

Sergey Bronnikov: FOSDEM passed

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

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

'''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)

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

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

'''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)

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

'''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)

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

'''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)

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

'''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)

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

'''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)

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

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

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

'''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]]

'''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]]

'''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]]
'''Boston, MA, USA, June 5-6 2015'''

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

'''June 2015, On Air'''

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

Andrew Vagin will talk 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|128px]]

'''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]]

'''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]]
'''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]]

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

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

'''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]]

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

'''12:45 MSK, 15 Feb, 2014 '''

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

'''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]]

'''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]]

'''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]]

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

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

== CRIU talk at Fedora Virtualization Day ==
[[Image:russian_fedora.png|left|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|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">

== CRIU talk at FOSDEM ==
[[Image:Fosdem-2013.png|left|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 ==
[[Image:LinuxCon-logo.jpg|left|100px]]

'''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]]

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

[http://events.yandex.ru/talks/334/ CRIU: more than a live migration (incl. slides and video)]

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

Articles

2015-12-31T15:29:07Z

Sergey Bronnikov: more articles

<noinclude>Articles about the CRIU project:

</noinclude>
* 2015-12-31, [http://kimh.github.io/blog/jp/criu/experiment-to-suspend-and-resume-docker-container-with-criu-jp/ Use the CRIU Docker container of stop / resume to the challenge]
* 2015-12-31, [http://blog.codeship.com/how-containers-will-change-the-game-server-hosting-industry/ How Containers Will Change the Game Server Hosting Industry]
* 2015-09-21, [http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/ Checkpoint and restore Docker container with CRIU]
* 2015-09-21, [https://blog.docker.com/2015/09/dolly-demo-linuxcon-runc/ Dolly Demo at LinuxCon: Rapid cloning of existing services with runC]
* 2015-09-10, [http://blog.tonicdev.com/2015/09/10/time-traveling-in-node.js-notebooks.html Time Traveling in Node.js Notebooks]
* 2015-01-01, [http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/openstack-at-cisco/linux-containers-white-paper-cisco-red-hat.pdfLinux Containers: Why They’re in Your Future and What Has to Happen First]
* 2015-07-01, [http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html How did the Quake demo from DockerCon Work?]
* 2015-05-06, [https://insights.ubuntu.com/2015/05/06/live-migration-in-lxd/ Live Migration in LXD] Ubuntu Insignts
* 2015-04-22, [http://tuxdiary.com/2015/04/22/dump-debug-resume-process-criu/ Dump, debug, resume process with criu] TuxDiary
* 2014-09-31, [http://www.reuters.com/article/wa-parallels-idUSnBw035202a+100+BSW20141103 Parallels Surpasses One Million Deployed Virtual Containers]
* 2014-08-01, ADMIN magazine: [http://www.admin-magazine.com/Archive/2014/22/Save-and-Restore-Linux-Processes-with-CRIU Save and Restore Linux Processes with CRIU]
* 2014-02-15, OCCAM Reproduce: [http://www.occamportal.org/papers/reproduce/reproduce14_paper_05.pdf Efficient, Accurate and Reproducible Simulation of Multi-Threaded Workloads] ([http://www.occamportal.org/slides/reproduce/reproduce14_slides_05.pdf slides])
* 2013-11-25, Phoronix: [http://www.phoronix.com/scan.php?page=news_item&px=MTUyNjE Checkpoint-Restore Hits v1.0: Freeze Your Linux Apps]
* 2013-11-25, LWN: [http://lwn.net/Articles/574918/ A note about 1.0]
* 2013-10-29, LWN: [http://lwn.net/Articles/572125/ Kernel summit report]
* 2013-02-01, A blog [http://www.anchor.com.au/blog/2013/02/overview-of-checkpoint-and-restore-live-migrating-processes-on-a-linux-system/ post] upon LCA-2013 talk.
* 2013-01-09, LWN: [http://lwn.net/Articles/531939/ Checkpoint/restore and signals]
* 2012-11-20, LWN: [http://lwn.net/Articles/525675/ LCE: Checkpoint/restore in user space: are we there yet?]
* 2012-05-01, LWN: [http://lwn.net/Articles/495304/ TCP connection repair]
* 2012-01-31, LWN: [http://lwn.net/Articles/478111/ Preparing for user-space checkpoint/restore]
* 2011-07-19, LWN: [http://lwn.net/Articles/452184/ Checkpoint/restart (mostly) in user space]
* 2012-07-24, OpenVZ blog: [http://openvz.livejournal.com/42414.html CRtools 0.1 released!]

{| class="mw-collapsible <includeonly>mw-collapsed</includeonly>" border="0"
|-
! style="text-align: left; font-weight: normal" | in Russian:
|-
|
* 18.12.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=43539 CRIU, путь от вызывающей непонимание разработки до интеграции в Red Hat Enterprise Linux]
* 09.12.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=43489 Выпуск CRIU 1.8, системы для сохранения и восстановления состояния процессов в Linux]
* 09.09.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42939 Выпуск CRIU 1.7, системы для сохранения и восстановления состояния процессов в Linux]
* 25.08.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42850 Проект OpenVZ анонсировал новый компонент для миграции Linux контейнеров - P.Haul]
* 27.05.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42315 Статус интеграции проектов CRIU и Docker]
* 25.11.2013, Opennet [http://www.opennet.ru/opennews/art.shtml?num=38519 Анонс выхода 1.0]
* 28.04.2015, Типичный программист [http://tproger.ru/interview/pavel-emelyanov/ Разработка ядра Linux — это общение в клубе по интересам]
* 22.04.2013, Habrahabr: [http://habrahabr.ru/post/177499/ В преддверии очередного релиза CRIU]
* 04.03.2013, IT-computer: [http://www.it-computer.com/osvaivaem-sistemu-zamorozki-processov-criu Осваиваем систему заморозки процессов CRIU]
* 28.09.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34958 CRIU 0.2 release]
* 05.11.2013, Xakep: [https://xakep.ru/2013/11/05/criu-manual/ Осваиваем систему заморозки процессов CRIU]
* 15.08.2013, Habrahabr: [http://habrahabr.ru/company/parallels/blog/190066/ «Разработка ядра Linux — это общение в клубе по интересам»]
* 01.10.2012, YaC 2012: [http://events.yandex.ru/events/yac/2012/talks/352/ больше, чем живая миграция для Linux контейнеров]
* 24.07.2012, Habrahabr: [http://habrahabr.ru/post/148413/ CRIU — новый амбициозный проект для сохранения и восстановления состояния процессов]
* 24.07.2012, Ru-OpenVZ blog: [http://ru-openvz.livejournal.com/5753.html Вышел первый релиз CRtools, версия 0.1]
* 24.07.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34408 Первый релиз CRtools, утилиты для заморозки и восстановления состояния процессов в Linux]
* 24.07.2012, LOR: [http://www.linux.org.ru/news/kernel/8021514 Вышел первый релиз CRtools, версия 0.1]
* Копипаста о v0.1 "CRIU / CRtools 0.1 — создание контрольных точек Linux-приложений и восстановление с них": [http://rosinvest.com/novosti/949423 Rosinvest], [http://www.nixp.ru/news/11854.html NIXP] [http://pcnews.ru/top/news/day/criu-crtools-linux-openvz-checkpoint-restore-in-userspace-cpt-system-90-10-lxc-org-398305.html PCNews]
|}

Articles

2015-12-31T15:12:34Z

Sergey Bronnikov: “The most dramatic addition to @Docker from a gaming perspective was support for @__criu__”

<noinclude>Articles about the CRIU project:

</noinclude>
* 2015-12-31, [http://blog.codeship.com/how-containers-will-change-the-game-server-hosting-industry/ How Containers Will Change the Game Server Hosting Industry]
* 2015-09-21, [http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/ Checkpoint and restore Docker container with CRIU]
* 2015-09-21, [https://blog.docker.com/2015/09/dolly-demo-linuxcon-runc/ Dolly Demo at LinuxCon: Rapid cloning of existing services with runC]
* 2015-09-10, [http://blog.tonicdev.com/2015/09/10/time-traveling-in-node.js-notebooks.html Time Traveling in Node.js Notebooks]
* 2015-01-01, [http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/openstack-at-cisco/linux-containers-white-paper-cisco-red-hat.pdfLinux Containers: Why They’re in Your Future and What Has to Happen First]
* 2015-07-01, [http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html How did the Quake demo from DockerCon Work?]
* 2014-09-31, [http://www.reuters.com/article/wa-parallels-idUSnBw035202a+100+BSW20141103 Parallels Surpasses One Million Deployed Virtual Containers]
* 2014-08-01, ADMIN magazine: [http://www.admin-magazine.com/Archive/2014/22/Save-and-Restore-Linux-Processes-with-CRIU Save and Restore Linux Processes with CRIU]
* 2014-02-15, OCCAM Reproduce: [http://www.occamportal.org/papers/reproduce/reproduce14_paper_05.pdf Efficient, Accurate and Reproducible Simulation of Multi-Threaded Workloads] ([http://www.occamportal.org/slides/reproduce/reproduce14_slides_05.pdf slides])
* 2013-11-25, Phoronix: [http://www.phoronix.com/scan.php?page=news_item&px=MTUyNjE Checkpoint-Restore Hits v1.0: Freeze Your Linux Apps]
* 2013-11-25, LWN: [http://lwn.net/Articles/574918/ A note about 1.0]
* 2013-10-29, LWN: [http://lwn.net/Articles/572125/ Kernel summit report]
* 2013-02-01, A blog [http://www.anchor.com.au/blog/2013/02/overview-of-checkpoint-and-restore-live-migrating-processes-on-a-linux-system/ post] upon LCA-2013 talk.
* 2013-01-09, LWN: [http://lwn.net/Articles/531939/ Checkpoint/restore and signals]
* 2012-11-20, LWN: [http://lwn.net/Articles/525675/ LCE: Checkpoint/restore in user space: are we there yet?]
* 2012-05-01, LWN: [http://lwn.net/Articles/495304/ TCP connection repair]
* 2012-01-31, LWN: [http://lwn.net/Articles/478111/ Preparing for user-space checkpoint/restore]
* 2011-07-19, LWN: [http://lwn.net/Articles/452184/ Checkpoint/restart (mostly) in user space]
* 2012-07-24, OpenVZ blog: [http://openvz.livejournal.com/42414.html CRtools 0.1 released!]

{| class="mw-collapsible <includeonly>mw-collapsed</includeonly>" border="0"
|-
! style="text-align: left; font-weight: normal" | in Russian:
|-
|
* 18.12.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=43539 CRIU, путь от вызывающей непонимание разработки до интеграции в Red Hat Enterprise Linux]
* 09.12.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=43489 Выпуск CRIU 1.8, системы для сохранения и восстановления состояния процессов в Linux]
* 09.09.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42939 Выпуск CRIU 1.7, системы для сохранения и восстановления состояния процессов в Linux]
* 25.08.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42850 Проект OpenVZ анонсировал новый компонент для миграции Linux контейнеров - P.Haul]
* 27.05.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42315 Статус интеграции проектов CRIU и Docker]
* 25.11.2013, Opennet [http://www.opennet.ru/opennews/art.shtml?num=38519 Анонс выхода 1.0]
* 22.04.2013, Habrahabr: [http://habrahabr.ru/post/177499/ В преддверии очередного релиза CRIU]
* 04.03.2013, IT-computer: [http://www.it-computer.com/osvaivaem-sistemu-zamorozki-processov-criu Осваиваем систему заморозки процессов CRIU]
* 28.09.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34958 CRIU 0.2 release]
* 05.11.2013, Xakep: [https://xakep.ru/2013/11/05/criu-manual/ Осваиваем систему заморозки процессов CRIU]
* 15.08.2013, Habrahabr: [http://habrahabr.ru/company/parallels/blog/190066/ «Разработка ядра Linux — это общение в клубе по интересам»]
* 01.10.2012, YaC 2012: [http://events.yandex.ru/events/yac/2012/talks/352/ больше, чем живая миграция для Linux контейнеров]
* 24.07.2012, Habrahabr: [http://habrahabr.ru/post/148413/ CRIU — новый амбициозный проект для сохранения и восстановления состояния процессов]
* 24.07.2012, Ru-OpenVZ blog: [http://ru-openvz.livejournal.com/5753.html Вышел первый релиз CRtools, версия 0.1]
* 24.07.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34408 Первый релиз CRtools, утилиты для заморозки и восстановления состояния процессов в Linux]
* 24.07.2012, LOR: [http://www.linux.org.ru/news/kernel/8021514 Вышел первый релиз CRtools, версия 0.1]
* Копипаста о v0.1 "CRIU / CRtools 0.1 — создание контрольных точек Linux-приложений и восстановление с них": [http://rosinvest.com/novosti/949423 Rosinvest], [http://www.nixp.ru/news/11854.html NIXP] [http://pcnews.ru/top/news/day/criu-crtools-linux-openvz-checkpoint-restore-in-userspace-cpt-system-90-10-lxc-org-398305.html PCNews]
|}

Packages

2015-12-30T12:54:49Z

Sergey Bronnikov: criu package in Mageia

This page summarizes our knowledge about CRIU packages in various Linux distributions.

== AltLinux ==
: http://packages.altlinux.org/crtools

== Arch ==
: https://aur.archlinux.org/packages/crtools-git/
{{Note| CONFIG_CHECKPOINT_RESTORE is [https://lists.archlinux.org/pipermail/arch-dev-public/2014-April/026102.html disabled] since v3.14, so [https://bugs.archlinux.org/task/43088 please vote here] to enable it back}}

== CoreOS ==
: https://github.com/coreos/coreos-overlay/tree/master/sys-process/criu

== Debian ==
: https://tracker.debian.org/pkg/criu

== Fedora ==
: https://apps.fedoraproject.org/packages/criu

== Gentoo ==
: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/criu/

== Kali ==
: http://pkg.kali.org/pkg/criu

== Mageia ==
: http://madb.mageia.org/package/show/application/0/name/criu

== OpenSUSE ==
: https://build.opensuse.org/package/show/openSUSE:Factory/criu#

== Ubuntu ==
: https://launchpad.net/ubuntu/+source/criu

== See also ==

* [http://pkgs.org/search/criu Search CRIU package in various Linux distributions]
* [https://qa.debian.org/popcon.php?package=criu Popularity contest statistics for criu]

Articles

2015-12-30T12:53:18Z

Sergey Bronnikov: added latest articles

<noinclude>Articles about the CRIU project:

</noinclude>
* 2015-09-21, [http://blog.circleci.com/checkpoint-and-restore-docker-container-with-criu/ Checkpoint and restore Docker container with CRIU]
* 2015-09-21, [https://blog.docker.com/2015/09/dolly-demo-linuxcon-runc/ Dolly Demo at LinuxCon: Rapid cloning of existing services with runC]
* 2015-09-10, [http://blog.tonicdev.com/2015/09/10/time-traveling-in-node.js-notebooks.html Time Traveling in Node.js Notebooks]
* 2015-01-01, [http://www.cisco.com/c/dam/en/us/solutions/collateral/data-center-virtualization/openstack-at-cisco/linux-containers-white-paper-cisco-red-hat.pdfLinux Containers: Why They’re in Your Future and What Has to Happen First]
* 2015-07-01, [http://blog.kubernetes.io/2015/07/how-did-quake-demo-from-dockercon-work.html How did the Quake demo from DockerCon Work?]
* 2014-09-31, [http://www.reuters.com/article/wa-parallels-idUSnBw035202a+100+BSW20141103 Parallels Surpasses One Million Deployed Virtual Containers]
* 2014-08-01, ADMIN magazine: [http://www.admin-magazine.com/Archive/2014/22/Save-and-Restore-Linux-Processes-with-CRIU Save and Restore Linux Processes with CRIU]
* 2014-02-15, OCCAM Reproduce: [http://www.occamportal.org/papers/reproduce/reproduce14_paper_05.pdf Efficient, Accurate and Reproducible Simulation of Multi-Threaded Workloads] ([http://www.occamportal.org/slides/reproduce/reproduce14_slides_05.pdf slides])
* 2013-11-25, Phoronix: [http://www.phoronix.com/scan.php?page=news_item&px=MTUyNjE Checkpoint-Restore Hits v1.0: Freeze Your Linux Apps]
* 2013-11-25, LWN: [http://lwn.net/Articles/574918/ A note about 1.0]
* 2013-10-29, LWN: [http://lwn.net/Articles/572125/ Kernel summit report]
* 2013-02-01, A blog [http://www.anchor.com.au/blog/2013/02/overview-of-checkpoint-and-restore-live-migrating-processes-on-a-linux-system/ post] upon LCA-2013 talk.
* 2013-01-09, LWN: [http://lwn.net/Articles/531939/ Checkpoint/restore and signals]
* 2012-11-20, LWN: [http://lwn.net/Articles/525675/ LCE: Checkpoint/restore in user space: are we there yet?]
* 2012-05-01, LWN: [http://lwn.net/Articles/495304/ TCP connection repair]
* 2012-01-31, LWN: [http://lwn.net/Articles/478111/ Preparing for user-space checkpoint/restore]
* 2011-07-19, LWN: [http://lwn.net/Articles/452184/ Checkpoint/restart (mostly) in user space]
* 2012-07-24, OpenVZ blog: [http://openvz.livejournal.com/42414.html CRtools 0.1 released!]

{| class="mw-collapsible <includeonly>mw-collapsed</includeonly>" border="0"
|-
! style="text-align: left; font-weight: normal" | in Russian:
|-
|
* 18.12.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=43539 CRIU, путь от вызывающей непонимание разработки до интеграции в Red Hat Enterprise Linux]
* 09.12.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=43489 Выпуск CRIU 1.8, системы для сохранения и восстановления состояния процессов в Linux]
* 09.09.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42939 Выпуск CRIU 1.7, системы для сохранения и восстановления состояния процессов в Linux]
* 25.08.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42850 Проект OpenVZ анонсировал новый компонент для миграции Linux контейнеров - P.Haul]
* 27.05.2015, Opennet [http://www.opennet.ru/opennews/art.shtml?num=42315 Статус интеграции проектов CRIU и Docker]
* 25.11.2013, Opennet [http://www.opennet.ru/opennews/art.shtml?num=38519 Анонс выхода 1.0]
* 22.04.2013, Habrahabr: [http://habrahabr.ru/post/177499/ В преддверии очередного релиза CRIU]
* 04.03.2013, IT-computer: [http://www.it-computer.com/osvaivaem-sistemu-zamorozki-processov-criu Осваиваем систему заморозки процессов CRIU]
* 28.09.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34958 CRIU 0.2 release]
* 05.11.2013, Xakep: [https://xakep.ru/2013/11/05/criu-manual/ Осваиваем систему заморозки процессов CRIU]
* 15.08.2013, Habrahabr: [http://habrahabr.ru/company/parallels/blog/190066/ «Разработка ядра Linux — это общение в клубе по интересам»]
* 01.10.2012, YaC 2012: [http://events.yandex.ru/events/yac/2012/talks/352/ больше, чем живая миграция для Linux контейнеров]
* 24.07.2012, Habrahabr: [http://habrahabr.ru/post/148413/ CRIU — новый амбициозный проект для сохранения и восстановления состояния процессов]
* 24.07.2012, Ru-OpenVZ blog: [http://ru-openvz.livejournal.com/5753.html Вышел первый релиз CRtools, версия 0.1]
* 24.07.2012, Opennet: [http://www.opennet.ru/opennews/art.shtml?num=34408 Первый релиз CRtools, утилиты для заморозки и восстановления состояния процессов в Linux]
* 24.07.2012, LOR: [http://www.linux.org.ru/news/kernel/8021514 Вышел первый релиз CRtools, версия 0.1]
* Копипаста о v0.1 "CRIU / CRtools 0.1 — создание контрольных точек Linux-приложений и восстановление с них": [http://rosinvest.com/novosti/949423 Rosinvest], [http://www.nixp.ru/news/11854.html NIXP] [http://pcnews.ru/top/news/day/criu-crtools-linux-openvz-checkpoint-restore-in-userspace-cpt-system-90-10-lxc-org-398305.html PCNews]
|}

Packages

2015-12-30T12:45:34Z

Sergey Bronnikov: criu package in Kali Linux

This page summarizes our knowledge about CRIU packages in various Linux distributions.

== AltLinux ==
: http://packages.altlinux.org/crtools

== Arch ==
: https://aur.archlinux.org/packages/crtools-git/
{{Note| CONFIG_CHECKPOINT_RESTORE is [https://lists.archlinux.org/pipermail/arch-dev-public/2014-April/026102.html disabled] since v3.14, so [https://bugs.archlinux.org/task/43088 please vote here] to enable it back}}

== CoreOS ==
: https://github.com/coreos/coreos-overlay/tree/master/sys-process/criu

== Debian ==
: https://tracker.debian.org/pkg/criu

== Fedora ==
: https://apps.fedoraproject.org/packages/criu

== Gentoo ==
: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/criu/

== Kali ==
: http://pkg.kali.org/pkg/criu

== OpenSUSE ==
: https://build.opensuse.org/package/show/openSUSE:Factory/criu#

== Ubuntu ==
: https://launchpad.net/ubuntu/+source/criu

== See also ==

* [http://pkgs.org/search/criu Search CRIU package in various Linux distributions]
* [https://qa.debian.org/popcon.php?package=criu Popularity contest statistics for criu]

Installation

2015-12-26T20:58:52Z

Sergey Bronnikov: libcap-devel package is required for at least 'make test'

<code>criu</code> is an utility to checkpoint/restore a process tree. This page describes how to manually build and install prerequisites and the tool itself.

== Installing from packages ==

Some distributions provide ready-to-use [[packages]]. If no, or the CRIU version you want is not yet there, you will need to get CRIU sources and compile it.

== Obtaining CRIU Source ==

You can download the source code as a release tarball or sync the [http://git.criu.org/?p=criu.git;a=summary git repository]. If you plan to modify CRIU sources the latter way is highly recommended.

=== Getting source tarball ===
: {{Latest release}}

=== Cloning git repository ===
git clone https://github.com/xemul/criu

== Dependencies ==

=== Compiler and C Library ===

CRIU is mostly written in C and the build system is based on Makefiles. Thus just install standard <code>gcc</code> and <code>make</code> packages (on Debian, <code>[https://packages.debian.org/build-essential build-essential]</code> will pull in both at once).

If you are cross compiling for ARM, use distribution packages or download prebuilt toolchains from Linaro.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Downloading Linaro toolchains
<div class="mw-collapsible-content">
sudo apt-get install lib32stdc++6 lib32z1 # These are ia32 binaries
mkdir -p deps/`uname -m`-linux-gnu
cd deps
wget http://releases.linaro.org/14.09/components/toolchain/binaries/gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz
tar --strip=1 -C `uname -m`-linux-gnu -xf gcc-linaro-arm-linux-gnueabihf-4.9-2014.09_linux.tar.xz
wget http://releases.linaro.org/14.09/components/toolchain/binaries/gcc-linaro-aarch64-linux-gnu-4.9-2014.09_linux.tar.xz
tar --strip=1 -C `uname -m`-linux-gnu -xf gcc-linaro-aarch64-linux-gnu-4.9-2014.09_linux.tar.xz
cd ..
</div>
</div>

=== Protocol Buffers ===

CRIU uses the [https://developers.google.com/protocol-buffers/ Google Protocol Buffers] to read and write [[images]] and thus requires [https://github.com/protobuf-c/protobuf-c C language bindings]. The <code>protoc</code> tool is required at build time and the <code>libprotobuf-c.so</code> shared object is required at build and run time. [[CRIT]] also uses python language bindings for protocol buffers and requires the <code>descriptor.proto</code> file typically provided by a distribution's protobuf development package.

==== Distribution Packages ====
The easiest way is to install distribution packages.

* RPM package names
** <code>protobuf</code>
** <code>protobuf-c</code>
** <code>protobuf-c-devel</code>
** <code>protobuf-compiler</code>
** <code>protobuf-devel</code>
** <code>protobuf-python</code>
* Debian package names
** <code>libprotobuf-dev</code>
** <code>libprotobuf-c0-dev</code>
** <code>protobuf-c-compiler</code>
** <code>protobuf-compiler</code>
** <code>python-protobuf</code>

==== Building Protocol Buffers From Source ====
If you would like to build from source, you can use the following commands to obtain the source code repositories, configure, and build the code. On a Debian based system, you may have to install <code>autoconf curl g++ libtool</code> packages first.

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
To build protobuf
<div class="mw-collapsible-content">
cd deps
git clone https://github.com/google/protobuf.git protobuf
cd protobuf
./autogen.sh
./configure --prefix=`pwd`/../`uname -m`-linux-gnu
make
make install
cd ../..
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
To build protobuf-c
<div class="mw-collapsible-content">
cd deps
git clone https://github.com/protobuf-c/protobuf-c.git protobuf-c
cd protobuf-c
./autogen.sh
mkdir ../pbc-`uname -m`
cd ../pbc-`uname -m`
../protobuf-c/configure --prefix=`pwd`/../`uname -m`-linux-gnu \
PKG_CONFIG_PATH=`pwd`/../`uname -m`-linux-gnu/lib/pkgconfig
make
make install
cd ../..
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
To cross-compile for ARM some more tricks will be required.
<div class="mw-collapsible-content">
For ARMv7

cd deps
mkdir -p pbc-arm
cd pbc-arm
../protobuf-c/configure --host=arm-linux-gnueabihf --prefix=`pwd`/../arm-linux-gnueabihf \
--disable-protoc PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
make PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
make install PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
cd ../..

For ARM8

cd deps
mkdir -p pbc-aarch64
cd pbc-aarch64
../protobuf-c/configure --host=aarch64-linux-gnu --prefix=`pwd`/../aarch64-linux-gnu \
--disable-protoc PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
make PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
make install PATH=`pwd`/../`uname -m`-linux-gnu/bin:$PATH
cd ../..
</div>
</div>

=== Other deps ===

* <code>python-ipaddr</code> is used by CRIT to pretty-print ip.
* If <code>libbsd</code> available, CRIU will be compiled with setproctitle() support. It will allow to make process titles of service workers to be more verbose.
* The iproute2 tool version 3.5.0 or higher is needed for dumping network namespaces. The latest one can be cloned from [http://git.kernel.org/?p=linux/kernel/git/shemminger/iproute2.git;a=summary iproute2]. It should be compiled and a path to ip written in the environment variable <code>CR_IP_TOOL</code>.
* If you would like to use <code>make test</code> you should install <code>libaio-devel</code> and <code>libcap-devel</code>.

== Linux Kernel ==

Linux kernel v3.11 or newer is required, with some specific options set. If your distribution does not provide needed kernel, you might want to compile one yourself.

=== Configuring the kernel ===

Most likely the first thing to enable is the <code>CONFIG_EXPERT=y</code> (General setup -> Configure standard kernel features (expert users)) option, which on x86_64 depends on the <code>CONFIG_EMBEDDED=y</code> (General setup -> Embedded system) one (welcome to Kconfig reverse chains hell).

The following options must be enabled for CRIU to work:

* ''General setup'' options
** <code>CONFIG_CHECKPOINT_RESTORE=y</code> (Checkpoint/restore support)
** <code>CONFIG_NAMESPACES=y</code> (Namespaces support)
** <code>CONFIG_UTS_NS=y</code> (Namespaces support -> UTS namespace)
** <code>CONFIG_IPC_NS=y</code> (Namespaces support -> IPC namespace)
** <code>CONFIG_PID_NS=y</code> (Namespaces support -> PID namespaces)
** <code>CONFIG_NET_NS=y</code> (Namespaces support -> Network namespace)
** <code>CONFIG_FHANDLE=y</code> (Open by fhandle syscalls)
** <code>CONFIG_EVENTFD=y</code> (Enable eventfd() system call)
** <code>CONFIG_EPOLL=y</code> (Enable eventpoll support)
* ''Networking support -> Networking options'' options for sock-diag subsystem
** <code>CONFIG_UNIX_DIAG=y</code> (Unix domain sockets -> UNIX: socket monitoring interface)
** <code>CONFIG_INET_DIAG=y</code> (TCP/IP networking -> INET: socket monitoring interface)
** <code>CONFIG_INET_UDP_DIAG=y</code> (TCP/IP networking -> INET: socket monitoring interface -> UDP: socket monitoring interface)
** <code>CONFIG_PACKET_DIAG=y</code> (Packet socket -> Packet: sockets monitoring interface)
** <code>CONFIG_NETLINK_DIAG=y</code> (Netlink socket -> Netlink: sockets monitoring interface)
* Other options
** <code>CONFIG_INOTIFY_USER=y</code> (File systems -> Inotify support for userspace)
** <code>CONFIG_IA32_EMULATION=y</code> (x86 only) (Executable file formats -> Emulations -> IA32 Emulation)

For some [[usage scenarios]] there is an ability to track memory changes and produce [[incremental dumps]]. Need to enable the <code>CONFIG_MEM_SOFT_DIRTY=y</code> (optional) (Processor type and features -> Track memory changes).

Note we also have our [[custom kernel]], which might contain some experimental CRIU related patches.

== Building CRIU From Source ==

=== Native Compilation ===
Simply run <code>make</code> in the CRIU source directory.

=== Compilation in Docker container ===

There's a ''docker-build'' target in Makefile which builds CRIU in Ubuntu Docker container. Just run <code>make docker-build</code> and that's it.

=== Non-standard compilation ===

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Building natively, but specifying built dependencies manually
<div class="mw-collapsible-content">
cd deps
rsync -a --exclude=.git --exclude=deps .. criu-`uname -m`
cd criu-`uname -m`
make \
USERCFLAGS="-I`pwd`/../`uname -m`-linux-gnu/include -L`pwd`/../`uname -m`-linux-gnu/lib" \
PATH="`pwd`/../`uname -m`-linux-gnu/bin:$PATH"
sudo LD_LIBRARY_PATH=`pwd`/../`uname -m`-linux-gnu/lib ./criu check
cd ../..
</div>
</div>

<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
Cross Compilation for ARM
<div class="mw-collapsible-content">
ARMv7
cd deps
rsync -a --exclude=.git --exclude=deps .. criu-arm
cd criu-arm
make \
ARCH=arm \
CROSS_COMPILE=`pwd`/../`uname -m`-linux-gnu/bin/arm-linux-gnueabihf- \
USERCFLAGS="-I`pwd`/../arm-linux-gnueabihf/include -L`pwd`/../arm-linux-gnueabihf/lib" \
PATH="`pwd`/../`uname -m`-linux-gnu/bin:$PATH"
cd ../..

ARMv8
cd deps
rsync -a --exclude=.git --exclude=deps .. criu-aarch64
cd criu-aarch64
make \
ARCH=aarch64 \
CROSS_COMPILE=`pwd`/../`uname -m`-linux-gnu/bin/aarch64-linux-gnu- \
USERCFLAGS="-I`pwd`/../aarch64-linux-gnu/include -L`pwd`/../aarch64-linux-gnu/lib" \
PATH="`pwd`/../`uname -m`-linux-gnu/bin:$PATH"
cd ../..
</div>
</div>

== Installation ==
CRIU works perfectly even when run from the sources directory (with the "./criu" command), but if you want to have in standard paths run <code>make install</code>.

You may need to install the following packages to generate docs in Debian-based OS's to avoid errors from install-man:
* <code>asciidoc</code>
* <code>xmlto</code>

== Checking That It Works ==

First thing to do is to run <code>criu check --ms</code>.

At the end it should say "Looks OK", if it doesn't the messages on the screen explain what functionality is missing. If you're using our custom kernel, then the <code>--ms</code> option should not be used, in this case CRIU would check for ''all'' the kernel features to work.

You can then try running the [[ZDTM Test Suite]] which sits in the <code>tests/zdtm/</code> directory.

== Further reading ==

Please see [[Usage]] and [[Advanced usage]], as well as [[:Category:HOWTO]].

[[Category:HOWTO]]

Comparison to other CR projects

2015-12-09T19:20:56Z

Sergey Bronnikov: added absent architectures for criu

This pages tries to explain differences between CRIU and other C/R solutions.

== DMTCP ==

{{:DMTCP}}

== BLCR ==

Berkeley Lab Checkpoint/Restart (BLCR) is a part of the Scalable Systems Software Suite ,
developed by the Future Technologies Group at Lawrence Berkeley National Lab under SciDAC
funding from the United States Department of Energy. It is an Open Source, system-level
checkpointer designed with High Performance Computing (HPC) applications in mind: in particular
CPU and memory intensive batch-scheduled MPI jobs. BLCR is implemented as a GPL-licensed
loadable kernel module for Linux 2.4.x and 2.6.x kernels on the x86, x86_64, PPC/PPC64, ARM architectures, and a
small LGPL-licensed library.

== PinLIT / PinPlay ==

PinLIT (Pin-Long Instruction Trace) is a checkpointing tool built on top of Intel's proprietary [https://software.intel.com/en-us/articles/pin-a-dynamic-binary-instrumentation-tool PIN binary instrumentation tool] described on page 48 of [https://cseweb.ucsd.edu/~calder/papers/thesis-cristiano.pdf Cristiano Pereira's PhD thesis]. It records the processor's (big) architectural register state and all pages of memory that contain application and shared library code, optimizing size by only storing memory used during a desired interval.

[https://software.intel.com/en-us/articles/program-recordreplay-toolkit PinPlay] or the Program Record/Replay Toolkit appears to be the successor of or new name for PinLIT.

Both tools appear primarily focused on reducing benchmark runtime on slow computer architecture simulators, leveraging sampling algorithms such as SimPoint.

== OpenVZ (in-kernel) ==

Legacy OpenVZ (RHEL4, RHEL5, RHEL6 based kernels) has in-kernel checkpoint/restore, sources can be found in kernel/cpt/.

== CKPT (in-kernel) ==

(In-kernel) [https://ckpt.wiki.kernel.org/index.php/Main_Page Linux Checkpoint/Restart] was a project from around 2008 to around 2010 to implement checkpoint/restart of Linux processes.

== CRIU, DMTCP, BLCR, OpenVZ comparison table ==

“looks\seems like yes/no” - i found only unproved message(s) saying “yes”/“no”

“not yet” - it is officially planned or i found no reasons, why it can’t be done.

{| class="wikitable sortable"
|-
!
! CRIU
! DMTCP
! BLCR
! OpenVZ

|-
| Arch
| x86_64, ARM, AArch64, PPC64le
| x86, x86_64, ARM
| x86, x86_64, PPC/PPC64, ARM
| x86, x86_64

|-
| OS
| Linux
| Linux
| Linux
| Linux

|-
| Uses standard kernel?
| {{Yes}}, provided it's 3.11 or later
| {{Yes}}
| {{Yes}}, just needs to load module
| {{No}}. OpenVZ kernel is required

|-
| Can be used without preloading special libraries before app start?
| {{Yes}}
| {{No}}
| {{No}}
| {{Yes}}

|-
| Can be used as non-root user?
| {{Yes}}, but user can only manipulate tasks belonging to him
| {{Yes}}
| {{Yes}}
| {{No}}

|-
| Can run unmodified programs?
| {{Yes}}
| {{Yes}}
| {{No}}. Statically linked and/or threaded apps are unsupported.
| {{Yes}}

|-
| Can run unprepared tasks?
| {{Yes}}
| {{No}}. It preloads the DMTCP library. That library runs before the routine main(). It creates a second thread. The checkpoint thread then creates a socket to the DMTCP coordinator and registers itself. The checkpoint thread also creates a signal handler.
| {{No}}. CR shall notify processes when a checkpoint is to occur (before the kernel takes a checkpoint) to allow the processes to prepare itself accordingly.
| {{Yes}}

|-
| Retains behavior of the c/r-ed programs?
| {{Yes}} (but see [[What can change after C/R]])
| {{No}}, because of wrappers on system calls
| {{No}}, because of wrappers on system calls
| {{Yes}}

|-
| Live migration
| {{Yes}}, even if kernel, libs, etc are newer. Can use [[memory changes tracking]] to decrease freeze time
| {{Yes}}, if both kernels are recent
| {{Yes}}, but if all components are the same. Even if prelinked addresses are different, it will not restore, but it can save the whole used libs and localization files to restore program on the different machine
| {{Yes}}

|-
| Containers
| {{Yes}}, LXC and OpenVZ containers
| {{No}}. It doesn't support namespaces, so it probably can’t dump containers
| {{No|Looks like no}}
| {{Yes}}

|-
| Parallel/distributed computations libraries
| {{No}} (planned)
| {{Yes}}. OpenMPI, MPICH2, OpenMP, Cilk are alredy supported and Infiniband is in progress
| {{Yes}}. Cray MPI, Intel MPI, LAM/MPI, MPICH-V, MPICH2, MVAPICH, Open MPI, SGI MPT
| {{Yes}}

|-
| Possible to C/R of gdb with debugged app?
| {{No}}, because they are using the same interface
| {{Yes}}
| {{No}}
| {{Yes}}

|-
| X Window apps (KDE, GNOME, etc)
| {{Yes}}, via VNC
| {{Yes}}, via VNC
| {{No|Looks like no}}
| {{Yes}}, via VNC

|-
| Solutions for invocation in the custom software
| {{Yes}}, [[RPC]] and [[C API]]
| {{Yes}}, plugins and API
| {{No|Not yet}}
| {{Yes}}, via ioctl calls

|-
| colspan="4" |

|-
| Unix sockets
| {{Yes}}
| {{Yes}}
| {{No}}
| {{Yes}}

|-
| UDP sockets
| {{Yes}}, both ipv4 and ipv6
| {{No|Not yet}}. Developers of dmtcp had no request for this
| {{No|Not yet}}
| {{Yes}}

|-
| TCP sockets
| {{Yes}}
| {{Yes}}
| {{No|Not yet}}
| {{Yes}}

|-
| Established TCP connection
| {{Yes}}
| {{No}}, but you can write a simple DMTCP plugin that tells DMTCP how you want to reconnect on restart
| {{No}}
| {{Yes}}

|-
| Infiniband
| {{No}}
| {{No|Not yet, developing is on the half-way}}
| {{No}}
| {{No}}

|-
| Multithread support
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}}

|-
| Multiprocess
| {{Yes}}
| {{Yes}}
| {{Yes}}
| {{Yes}}

|-
| Process groups and sessions
| {{Yes}}
| {{Yes}}
| {{No|Not yet}}
| {{Yes}}

|-
| Zombies
| {{Yes}}
| {{No}}
| {{No}}
| {{Yes}}

|-
| Namespaces
| {{Yes}}
| {{No}}
| {{No}}
| {{Yes}}

|-
| Ptraced programs
| {{No}}
| {{Yes}}
| {{No}}
| {{Yes}}

|-
| System V IPC
| {{Yes}}
| {{Yes}}
| {{No}}
| {{Yes}}

|-
| Memory mappings
| {{Yes}}, all kinds
| {{Yes}}
| {{Partial}}
| {{Yes}}

|-
| Pipes
| {{Yes}}
| {{Yes}}
| {{No|Not yet}}
| {{Yes}}

|-
| Terminals
| {{Yes}}, but only Unix98 PTYs
| {{Yes}}
| {{Yes}}
| {{Yes}}

|-
| Non-POSIX files (inotify, signalfd, eventfd, etc)
| {{Yes}}, inotify, fanotify, epoll, signalfd, eventfd
| {{Yes}}, epoll, eventfd, signalfd are already supported and inotify will be supported in future
| {{No|Looks like no}}
| {{Yes}}

|-
| Timers
| {{Yes}}
| {{No}}. Any counter or timer active since the beginning of a process will consider the restarted process to be a new process.
| {{Yes}}
| {{Yes}}

|-
| Shared resources (files, mm, etc.)
| {{Yes}}. SysVIPC, files, fd table and memory
| {{Yes}}. System V shared memory(shmget, etc.), mmap-based shared memory, shared sockets, pipes, file descriptors
| {{No}}, but it is planned to support shared mmap regions
| {{Yes}}

|-
| Block devices
| {{No}}
| {{Yes|Looks like yes}}
| {{No}}
| {{No}}

|-
| Character devices
| {{Yes}}, only /dev/null, /dev/zero, etc. are supported
| {{Yes}}, looks like null and zero are supported
| {{Yes}}, /dev/null and /dev/zero
| {{Yes}}

|-
| Capture the contents of open files
| {{Yes}}, if file is unlinked
| {{No|Looks like no}}
| {{No|Not yet}}
| {{Yes}}

|}

== Sources ==
DMTCP:
*http://dmtcp.sourceforge.net/
*http://dmtcp.sourceforge.net/papers/dmtcp.pdf
*http://www.ccs.neu.edu/home/gene/papers/ccgrid06.pdf
*http://research.cs.wisc.edu/htcondor/CondorWeek2010/condor-presentations/cooperman-dmtcp.pdf
*http://dmtcp.sourceforge.net/papers/mtcp.pdf

BLCR:
*https://upc-bugs.lbl.gov/blcr/doc/html/
*https://ftg.lbl.gov/assets/projects/CheckpointRestart/Pubs/LBNL-49659.pdf
*https://ftg.lbl.gov/assets/projects/CheckpointRestart/Pubs/blcr.pdf
*https://ftg.lbl.gov/assets/projects/CheckpointRestart/Pubs/checkpointSurvey-020724b.pdf
*https://ftg.lbl.gov/assets/projects/CheckpointRestart/Pubs/lacsi-2003.pdf
*https://ftg.lbl.gov/assets/projects/CheckpointRestart/Pubs/LBNL-60520.pdf

== External links ==

* [http://dmtcp.sourceforge.net/FAQ.html#Internals How does DMTCP work?]

[[Category:Under the hood]]

News/events/past

2015-11-20T18:38:06Z

Sergey Bronnikov: added dockercon and containerdays

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

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

'''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)

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

'''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)

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

'''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)

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

'''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)

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

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

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

'''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]]

'''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]]

'''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]]
'''Boston, MA, USA, June 5-6 2015'''

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

'''June 2015, On Air'''

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

Andrew Vagin will talk 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|128px]]

'''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]]

'''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]]
'''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]]

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

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

'''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]]

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

'''12:45 MSK, 15 Feb, 2014 '''

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

'''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]]

'''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]]

'''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]]

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

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

== CRIU talk at Fedora Virtualization Day ==
[[Image:russian_fedora.png|left|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|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">

== CRIU talk at FOSDEM ==
[[Image:Fosdem-2013.png|left|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 ==
[[Image:LinuxCon-logo.jpg|left|100px]]

'''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]]

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

[http://events.yandex.ru/talks/334/ CRIU: more than a live migration (incl. slides and video)]

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

News/events

2015-11-20T18:37:29Z

Sergey Bronnikov: dockercon and containerdays is over

News/events/past

2015-10-17T14:45:56Z

Sergey Bronnikov: osdevconf passed

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

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

'''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)

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

'''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)

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

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

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

'''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]]

'''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]]

'''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]]
'''Boston, MA, USA, June 5-6 2015'''

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

'''June 2015, On Air'''

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

Andrew Vagin will talk 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|128px]]

'''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]]

'''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]]
'''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]]

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

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

'''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]]

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

'''12:45 MSK, 15 Feb, 2014 '''

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

'''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]]

'''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]]

'''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]]

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

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

== CRIU talk at Fedora Virtualization Day ==
[[Image:russian_fedora.png|left|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|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">

== CRIU talk at FOSDEM ==
[[Image:Fosdem-2013.png|left|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 ==
[[Image:LinuxCon-logo.jpg|left|100px]]

'''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]]

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

[http://events.yandex.ru/talks/334/ CRIU: more than a live migration (incl. slides and video)]

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

News/events

2015-10-17T14:45:28Z

Sergey Bronnikov: removed osdevconf2015

<noinclude> __NOTOC__


This page collects into about events criu takes part in.
<startFeed/>
</noinclude>

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

'''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)

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

'''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)

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

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

<endFeed/>
<noinclude>

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

</noinclude>

News/events

2015-10-01T12:18:43Z

Sergey Bronnikov: reorder events

<noinclude> __NOTOC__


This page collects into about events criu takes part in.
<startFeed/>
</noinclude>

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

'''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)

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

'''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)

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

'''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)

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

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

<endFeed/>
<noinclude>

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

</noinclude>

News/events

2015-10-01T12:17:22Z

Sergey Bronnikov: Kaluga is cradle of Russian cosmonautics

<noinclude> __NOTOC__


This page collects into about events criu takes part in.
<startFeed/>
</noinclude>

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

'''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)

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

'''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)

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

'''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)

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

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

<endFeed/>
<noinclude>

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

</noinclude>

File:Altlinux-logo.gif

2015-10-01T12:14:15Z

Sergey Bronnikov:

Py-P.Haul

2015-09-29T12:17:46Z

Sergey Bronnikov: typo

[[Image:P.Haul-logo.png|300px|right]]

P.Haul is the project on top of CRIU implementing [[live migration]] usage scenario.

== What does the name mean ==

P.Haul (pronounced pee-hɔːl, Russian: пихль) stands for Process HAULer.

== Project logo ==

The project logo -- the [https://en.wikipedia.org/wiki/Pyotr_Pavlovich_Yershov#The_Humpbacked_Horse Little Humpbacked Horse] (Russian: [https://ru.wikipedia.org/wiki/%D0%9A%D0%BE%D0%BD%D1%91%D0%BA-%D0%93%D0%BE%D1%80%D0%B1%D1%83%D0%BD%D0%BE%D0%BA конёк-горбунок]) -- reflects the main purpose of P.Haul: container migration. Logo's Slavic origin emphasizes that the project has Russian roots.

{| class="wikitable"
!| Download
!| Description
!| Preview
|-
|| [https://static.openvz.org/artwork/PHaul-logo.svg PHaul.svg] || SVG, 973K || [[Image:PHaul-logo.svg|50px]]
|-
|| [http://static.openvz.org/artwork/PHaul-logo-800px.png PHaul-logo-800px.png] || PNG, 800x472, 24K || [[Image:PHaul-logo.svg|50px]]
|}

== Project resources ==

The source code is [https://github.com/xemul/p.haul on GitHub]

To participate in P.Haul development please subscribe to the mailing list:
[https://lists.openvz.org/mailman/listinfo/criu List info] | [https://lists.openvz.org/pipermail/criu List archives] | [mailto:criu-join@openvz.org Subscribe] | [mailto:criu-leave@openvz.org Unsubscribe]

We have a [https://github.com/xemul/p.haul/blob/master/test/mtouch/HOWTO test] to play with it

There's also a [https://github.com/xemul/p.haul/wiki/Live-migrating-OVZ-mainstream-container HOWTO] describing how to live migrate an [http://openvz.org OpenVZ] container

== See also ==

* P.Haul [https://openvz.org/Packages packages] in Linux distributions
* P.Haul was [http://linuxplumbersconf.org/2015/ocw/proposals/3165 announced] at Checkpoint and Restore MC, Linux Plumbers conference 2015: [https://etherpad.openstack.org/p/LPC2015_Checkpoint_Restore short notes] and [http://www.slideshare.net/openvz/plumbers-phaul150821152856lva1app6891 slides].

[[Category:P.Haul]]
[[Category:Live migration]]
[[Category:Sub-projects]]

Py-P.Haul

2015-09-25T11:38:42Z

Sergey Bronnikov: Add logo in PNG and SVG formats

[[Image:P.Haul-logo.png|300px|right]]

P.Haul is the project on top of CRIU implementing [[live migration]] usage scenario.

== What does the name mean ==

P.Haul (pronounced pee-hɔːl, Russian: пихль) stands for Process HAULer.

== Project logo ==

The project logo -- the [https://en.wikipedia.org/wiki/Pyotr_Pavlovich_Yershov#The_Humpbacked_Horse Little Humpbacked Horse] (Russian: [https://ru.wikipedia.org/wiki/%D0%9A%D0%BE%D0%BD%D1%91%D0%BA-%D0%93%D0%BE%D1%80%D0%B1%D1%83%D0%BD%D0%BE%D0%BA конёк-горбунок]) -- reflects the main purpose of P.Haul: container migration. Logo's Slavic origin emphasizes that the project has Russian roots.

{| class="wikitable"
!| Download
!| Description
!| Preview
|-
|| [https://static.openvz.org/artwork/PHaul-logo.svg PHaul.svg] || SVG, 973K || [[Image:PHaul-logo.svg|50px]]
|-
|| [http://static.openvz.org/artwork/PHaul-logo-800px.png PHaul-logo-800px.png] || PNG, 800x472, 24K || [[Image:PHaul-logo.svg|50px]]
|}

== Project resources ==

The source code is [https://github.com/xemul/p.haul on GitHub]

To participate in P.Haul develoopment please subscribe to the mailing list:
[https://lists.openvz.org/mailman/listinfo/criu List info] | [https://lists.openvz.org/pipermail/criu List archives] | [mailto:criu-join@openvz.org Subscribe] | [mailto:criu-leave@openvz.org Unsubscribe]

We have a [https://github.com/xemul/p.haul/blob/master/test/mtouch/HOWTO test] to play with it

There's also a [https://github.com/xemul/p.haul/wiki/Live-migrating-OVZ-mainstream-container HOWTO] describing how to live migrate an [http://openvz.org OpenVZ] container

== See also ==

* P.Haul [https://openvz.org/Packages packages] in Linux distributions
* P.Haul was [http://linuxplumbersconf.org/2015/ocw/proposals/3165 announced] at Checkpoint and Restore MC, Linux Plumbers conference 2015: [https://etherpad.openstack.org/p/LPC2015_Checkpoint_Restore short notes] and [http://www.slideshare.net/openvz/plumbers-phaul150821152856lva1app6891 slides].

[[Category:P.Haul]]
[[Category:Live migration]]
[[Category:Sub-projects]]

File:PHaul-logo.svg

2015-09-25T11:37:38Z

Sergey Bronnikov:

File:P.Haul-logo.png

2015-09-21T17:31:44Z

Sergey Bronnikov: Sergey Bronnikov uploaded a new version of File:P.Haul-logo.png

News/events/past

2015-09-19T20:48:14Z

Sergey Bronnikov: yandex event

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

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

'''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)

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

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

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

'''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]]

'''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]]

'''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]]
'''Boston, MA, USA, June 5-6 2015'''

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

'''June 2015, On Air'''

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

Andrew Vagin will talk 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|128px]]

'''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]]

'''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]]
'''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]]

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

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

'''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]]

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

'''12:45 MSK, 15 Feb, 2014 '''

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

'''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]]

'''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]]

'''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]]

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

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

== CRIU talk at Fedora Virtualization Day ==
[[Image:russian_fedora.png|left|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|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">

== CRIU talk at FOSDEM ==
[[Image:Fosdem-2013.png|left|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 ==
[[Image:LinuxCon-logo.jpg|left|100px]]

'''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]]

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

[http://events.yandex.ru/talks/334/ CRIU: more than a live migration (incl. slides and video)]

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

News/events

2015-09-19T20:48:02Z

Sergey Bronnikov: yandex event removed

File:P.Haul-logo.png

2015-09-18T15:56:37Z

Sergey Bronnikov: Sergey Bronnikov uploaded a new version of File:P.Haul-logo.png

Py-P.Haul

2015-09-14T16:55:46Z

Sergey Bronnikov: added draft of logo

[[Image:P.Haul-logo.png|300px|right]]

P.Haul is the project on top of CRIU implementing [[live migration]] usage scenario.

== What does the name mean ==

P.Haul (pronounced pee-hɔːl, Russian: пихль) stands for Process HAULer.

== Project logo ==

The project logo -- the [https://en.wikipedia.org/wiki/Pyotr_Pavlovich_Yershov#The_Humpbacked_Horse Little Humpbacked Horse] (Russian: [https://ru.wikipedia.org/wiki/%D0%9A%D0%BE%D0%BD%D1%91%D0%BA-%D0%93%D0%BE%D1%80%D0%B1%D1%83%D0%BD%D0%BE%D0%BA конёк-горбунок]) -- reflects the main purpose of P.Haul: container migration. Logo's Slavic origin emphasizes that the project has Russian roots.



== Project resources ==

The source code is [https://github.com/xemul/p.haul on GitHub]

To participate in P.Haul develoopment please subscribe to the mailing list:
[https://lists.openvz.org/mailman/listinfo/criu List info] | [https://lists.openvz.org/pipermail/criu List archives] | [mailto:criu-join@openvz.org Subscribe] | [mailto:criu-leave@openvz.org Unsubscribe]

We have a [https://github.com/xemul/p.haul/blob/master/test/mtouch/HOWTO test] to play with it

There's also a [https://github.com/xemul/p.haul/wiki/Live-migrating-OVZ-mainstream-container HOWTO] describing how to live migrate an [http://openvz.org OpenVZ] container

== See also ==

* P.Haul [https://openvz.org/Packages packages] in Linux distributions
* P.Haul was [http://linuxplumbersconf.org/2015/ocw/proposals/3165 announced] at Checkpoint and Restore MC, Linux Plumbers conference 2015: [https://etherpad.openstack.org/p/LPC2015_Checkpoint_Restore short notes] and [http://www.slideshare.net/openvz/plumbers-phaul150821152856lva1app6891 slides].

[[Category:P.Haul]]
[[Category:Live migration]]
[[Category:Sub-projects]]

File:P.Haul-logo.png

2015-09-14T16:46:02Z

Sergey Bronnikov:

Packages

2015-09-14T13:39:44Z

Sergey Bronnikov: link to popularity contest statistics for criu

This page summarizes our knowledge about CRIU packages in various Linux distributions.

== AltLinux ==
: http://packages.altlinux.org/crtools

== Arch ==
: https://aur.archlinux.org/packages/crtools-git/
{{Note| CONFIG_CHECKPOINT_RESTORE is [https://lists.archlinux.org/pipermail/arch-dev-public/2014-April/026102.html disabled] since v3.14, so [https://bugs.archlinux.org/task/43088 please vote here] to enable it back}}

== CoreOS ==
: https://github.com/coreos/coreos-overlay/tree/master/sys-process/criu

== Debian ==
: https://tracker.debian.org/pkg/criu

== Fedora ==
: https://apps.fedoraproject.org/packages/criu

== Gentoo ==
: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-process/criu/

== OpenSUSE ==
: https://build.opensuse.org/package/show/openSUSE:Factory/criu#

== Ubuntu ==
: https://launchpad.net/ubuntu/+source/criu

== See also ==

* [http://pkgs.org/search/criu Search CRIU package in various Linux distributions]
* [https://qa.debian.org/popcon.php?package=criu Popularity contest statistics for criu]

Py-P.Haul

2015-09-10T13:16:25Z

Sergey Bronnikov: add mailing list

P.Haul is the project on top of CRIU implementing [[live migration]] usage scenario.

== What does the name mean ==

P.Haul (pronounced pee-hɔːl, Russian: пихль) stands for Process HAULer.

== Project logo ==

The project logo -- the [https://en.wikipedia.org/wiki/Pyotr_Pavlovich_Yershov#The_Humpbacked_Horse Little Humpbacked Horse] (Russian: [https://ru.wikipedia.org/wiki/%D0%9A%D0%BE%D0%BD%D1%91%D0%BA-%D0%93%D0%BE%D1%80%D0%B1%D1%83%D0%BD%D0%BE%D0%BA конёк-горбунок]) -- reflects the main purpose of P.Haul: container migration. Logo's Slavic origin emphasizes that the project has Russian roots.

== Project resources ==

The source code is [https://github.com/xemul/p.haul on GitHub]

To participate in P.Haul develoopment please subscribe to the mailing list:
[https://lists.openvz.org/mailman/listinfo/criu List info] | [https://lists.openvz.org/pipermail/criu List archives] | [mailto:criu-join@openvz.org Subscribe] | [mailto:criu-leave@openvz.org Unsubscribe]

We have a [https://github.com/xemul/p.haul/blob/master/test/mtouch/HOWTO test] to play with it

There's also a [https://github.com/xemul/p.haul/wiki/Live-migrating-OVZ-mainstream-container HOWTO] describing how to live migrate an [http://openvz.org OpenVZ] container

== See also ==

* P.Haul [https://openvz.org/Packages packages] in Linux distributions
* P.Haul was [http://linuxplumbersconf.org/2015/ocw/proposals/3165 announced] at Checkpoint and Restore MC, Linux Plumbers conference 2015: [https://etherpad.openstack.org/p/LPC2015_Checkpoint_Restore short notes] and [http://www.slideshare.net/openvz/plumbers-phaul150821152856lva1app6891 slides].

[[Category:P.Haul]]
[[Category:Live migration]]
[[Category:Sub-projects]]