From: Pavel Emelyanov <xemul@parallels.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lwn@lwn.net, "criu@openvz.org" <criu@openvz.org>
Cc: users@openvz.org,
Containers <containers@lists.linux-foundation.org>,
cgroups mailinglist <cgroups@vger.kernel.org>
Subject: Re: [Announce] Checkpoint-restore tool v0.1
Date: Mon, 23 Jul 2012 12:53:42 +0400 [thread overview]
Message-ID: <500D1116.7070301@parallels.com> (raw)
In-Reply-To: <500D09C9.7060903@parallels.com>
Fixing the bogus containers@ ml and adding cgroups@ one. Sorry :(
== Original message ==
Hi!
I'm glad to announce the first release of the checkpoint-restore tool.
This project is an attempt to implement the checkpoint-restore functionality
for processes and containers without driving too much code into the kernel tree,
but putting there "various oddball helper code" instead.
The tool can already be used for checkpointing and restoring various individual
applications. And the greatest thing about this so far is that most of the below
functionality has the required kernel support in the recently released v3.5!
So, we support now
* x86_64 architecture
* process' linkage
* process groups and sessions (without ttys though :\ )
* memory mappings of any kind (shared, file, etc.)
* threads
* open files (shared between tasks and partially opened-and-unlinked)
* pipes and fifos with data
* unix sockets with packet queues contents
* TCP and UDP sockets (TCP connections support exists, but needs polishing)
* inotifies, eventpoll and eventfd
* tasks' sigactions setup, credentials and itimers
* IPC, mount and PID namespaces
Though namespaces support is in there, we do not yet support an LXC container c/r,
but we're close to it :)
I'd like to thank everyone who took part in new kernel APIs discussions, the
feedback was great! Special thanks goes to Linus for letting the kernel parts
in early, instead of making them sit out of tree till becoming stable enough.
Tarball with the tool sources is at
http://download.openvz.org/criu/crtools-0.1.tar.bz2
The git repo is at
http://git.criu.org/
And some sort of docs growing at
http://criu.org/
There are still things for which we don't have the kernel support merged (SysVIPC
and various anon file descriptors, i.e. inotify, eventpoll, eventfd) yet. We have
the kernel branch with the stuff applied available at
https://github.com/cyrillos/linux-2.6.git
Thanks,
Pavel
next prev parent reply other threads:[~2012-07-23 8:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 8:22 [Announce] Checkpoint-restore tool v0.1 Pavel Emelyanov
2012-07-23 8:53 ` Pavel Emelyanov [this message]
2012-07-23 13:14 ` Serge Hallyn
2012-07-30 10:42 ` richard -rw- weinberger
2012-07-31 8:53 ` Pavel Emelyanov
2012-07-31 8:57 ` richard -rw- weinberger
2012-07-31 9:00 ` Cyrill Gorcunov
2012-07-31 9:07 ` Pavel Emelyanov
2012-07-31 9:29 ` richard -rw- weinberger
2012-07-31 9:54 ` Pavel Emelyanov
2012-07-31 10:08 ` richard -rw- weinberger
2012-07-31 10:16 ` Cyrill Gorcunov
2012-07-31 10:21 ` richard -rw- weinberger
2012-07-31 10:30 ` Cyrill Gorcunov
2012-09-20 10:16 ` [Announce] Checkpoint-restore tool v0.2 Pavel Emelyanov
2012-09-20 13:05 ` Serge Hallyn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=500D1116.7070301@parallels.com \
--to=xemul@parallels.com \
--cc=cgroups@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=criu@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=users@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox