RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 463367 - [LTC 6.0 FEAT] 201036:Application checkpoint/restart
Summary: [LTC 6.0 FEAT] 201036:Application checkpoint/restart
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: All
OS: All
high
high
Target Milestone: alpha
: 6.0
Assignee: Jesse Larrew
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 356741 465490 554559
TreeView+ depends on / blocked
 
Reported: 2008-09-23 03:10 UTC by IBM Bug Proxy
Modified: 2013-01-10 07:57 UTC (History)
6 users (show)

Fixed In Version: kernel-2.6.32-1
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-02 20:51:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description IBM Bug Proxy 2008-09-23 03:10:29 UTC 
=Comment: #0=================================================
Emily J. Ratliff <emilyr.com> - 2008-09-16 18:30 EDT
1. Feature Overview:
Feature Id:	[201036]
a. Name of Feature:	Application checkpoint/restart
b. Feature Description
IBM has a non-upstream checkpoint/restart application set (MetaCluster), but seeks to offer this
functionality in a community and distribution acceptable form.  Building on the community
containerization effort (virtualizing resources through namespaces) we will develop basic
checkpoint/restart functionality.  This work is incremental with a goal to have the major API's
defined and upstream in mid-2008, but the overall development continuing into 2009.

2. Feature Details:
Sponsor:	LTC
Architectures:
x86
x86_64
ppc64

Arch Specificity: Both
Affects Core Kernel: Yes
Delivery Mechanism: Direct from community
Category:	Kernel
Request Type:	Kernel - Enhancement from IBM
d. Upstream Acceptance:	In Progress
Sponsor Priority	1
f. Severity: High
IBM Confidential:	no
Code Contribution:	IBM code
g. Component Version Target:	2.6.28

3. Business Case
This advanced feature and the higher availability it brings enhance the value proposition of linux
for high end users.

4. Primary contact at Red Hat: 
John Jarvis
jjarvis

5. Primary contacts at Partner:
Project Management Contact:
Michael Hohnbaum, hbaum.com, 503-578-5486

Technical contact(s):
Badari Pulavarty, badari.com
Serge Hallyn, sergeh.com

IBM Manager:
Pat Gaughen, gaughen.com
Comment 1 Bill Nottingham 2008-10-02 16:24:06 UTC 
Do you have a link to the first sets of patches?
Comment 2 IBM Bug Proxy 2008-10-13 22:41:50 UTC 
The latest version of the first set of actual checkpoint/restart patches can be found at:

http://lkml.org/lkml/2008/10/8/94

The freezer control group, which is also needed for checkpoint/restart, is in Andrew Morton's -mm tree, and (according to Andrew) likely to be pushed into 2.6.28.  The full patchset is 11 patches posted as two patchsets, the first 5 patches (see https://lists.linux-foundation.org/pipermail/containers/2008-August/012376.html ) and the second 6 patches (see https://lists.linux-foundation.org/pipermail/containers/2008-August/012481.html).

Please let me know if I should post tarballs of the patchsets.
Comment 3 Bill Nottingham 2008-10-14 01:03:43 UTC 
Shouldn't be needed as of right now; thanks for the pointer.
Comment 4 IBM Bug Proxy 2008-10-22 17:40:43 UTC 
This is just an update to point out that the freezer patchset is in Linus' tree.
Comment 5 IBM Bug Proxy 2009-02-06 15:42:08 UTC 
The following kernel config variable will need to be set to
enable the freezer, which we need for checkpoint/restart:

CONFIG_CGROUP_FREEZER=y
Comment 7 IBM Bug Proxy 2009-03-02 22:31:19 UTC 
Freezer is available since before 2.6.29.

To enable it, the kernel must be compiled with CONFIG_CGROUP_FREEZER=y
Comment 8 Bill Nottingham 2009-03-03 22:23:26 UTC 
The feature requested has already been accepted into the upstream code base
planned for the next major release of Red Hat Enterprise Linux.

When the next milestone release of Red Hat Enterprise Linux 6 is available,
please verify that the feature requested is present and functioning as
desired.
Comment 10 Mike Gahagan 2010-02-08 20:22:18 UTC 
I can confirm the freezer cgroup has been added to the 2.6.32 RHEL 6 kernels, is this the only functionality needed to satisfy this feature request?
Comment 11 IBM Bug Proxy 2010-05-04 19:50:50 UTC 
------- Comment From sergeh.com 2010-05-04 15:47 EDT-------
Freezer functionality verified.
Comment 12 releng-rhel@redhat.com 2010-07-02 20:51:53 UTC 
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.