From: Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Nathan Lynch <ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
Cc: Containers
<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: Wiki for LXC with Checkpoint/Restart
Date: Wed, 14 Apr 2010 13:40:54 -0700 [thread overview]
Message-ID: <20100414204054.GA24411@us.ibm.com> (raw)
In-Reply-To: <1271273662.18251.105.camel@localhost>
Nathan Lynch [ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org] wrote:
| On Mon, 2010-04-12 at 15:27 -0700, Sukadev Bhattiprolu wrote:
| > Hi,
| >
| > We created following wiki to describe the process to build/test LXC
| > with checkpoint/restart.
| >
| > https://ckpt.wiki.kernel.org/index.php/Link-LXC-USERCR
| >
| > The USERCR and LXC patches that are needed are in:
| >
| > http://lxc.sourceforge.net/patches/lxc+usercr/usercr-patches/
| > http://lxc.sourceforge.net/patches/lxc+usercr/lxc-patches/
| >
| > (and also referred to in the above wiki).
| >
| > For now, the wiki identifies specific "commit-id"s to identify the
| > commit with which the instructions in the wiki were tested. We hope
| > to create more meaningful tags to the commits and if so, we will update
| > the wiki with the tags.
|
| Commit IDs are ugly but unambiguous. I didn't have a problem just
| copy/pasting the commands.
|
| > Please let me know if you have any comments on the wiki or run into
| > problems.
|
| I took the liberty of cleaning up a few stray '|' characters in the last
| code snippet and fixed up the deprecated old-style git invocations (e.g.
| "git-clone" becomes "git clone"). Not trying to be picky about the git
| thing, but the hyphenated commands don't work on newer distributions.
|
| I ran into an issue trying to follow the instructions on a SLES11 x86_64
| system. When building lxc I get:
|
| gcc -fPIC -DPIC -I../../src -DLIBCR -I/home/nathanl/user-cr
| -I/home/nathanl/user-cr/include -g -O2 -Wall
| -shared /home/nathanl/user-cr/checkpoint.o /home/nathanl/user-cr/restart.o /home/nathanl/user-cr/libeclone.a -Wl,-soname,liblxc.so.0 -o liblxc.so liblxc_so-arguments.o liblxc_so-commands.o liblxc_so-start.o liblxc_so-stop.o liblxc_so-monitor.o liblxc_so-console.o liblxc_so-freezer.o liblxc_so-checkpoint.o liblxc_so-restart.o liblxc_so-error.o liblxc_so-parse.o liblxc_so-cgroup.o liblxc_so-utils.o liblxc_so-namespace.o liblxc_so-conf.o liblxc_so-confile.o liblxc_so-state.o liblxc_so-log.o liblxc_so-network.o liblxc_so-nl.o liblxc_so-rtnl.o liblxc_so-genl.o liblxc_so-mainloop.o liblxc_so-af_unix.o -lutil
| /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: /home/nathanl/user-cr/checkpoint.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC
|
| Not sure what to do about it immediately; user-cr/checkpoint.o should be
| built with -fPIC I guess?
Yes, I think thats what Michel or Daniel ran into. For some reason, I
did not run into on Fedora11. Can you add -fPIC to the usercr CFLAGS
and try ? If it works for you, I will try on Fedora11 too and we can
add a patch to lxc.sf.net/patches/lxc+usercr/.
We may need to do something similar for any kernel patches that are
needed on top of each "release" of the wiki.
Sukadev
next prev parent reply other threads:[~2010-04-14 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 22:27 Wiki for LXC with Checkpoint/Restart Sukadev Bhattiprolu
[not found] ` <20100412222727.GA5759-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-14 19:34 ` Nathan Lynch
2010-04-14 20:40 ` Sukadev Bhattiprolu [this message]
[not found] ` <20100414204054.GA24411-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-14 20:55 ` Nathan Lynch
2010-04-15 22:00 ` Nathan Lynch
2010-04-14 19:57 ` Nathan Lynch
2010-04-14 20:00 ` Dan Smith
[not found] ` <87ljcpajog.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-04-14 20:16 ` Nathan Lynch
2010-04-14 20:24 ` Dan Smith
[not found] ` <87hbndaik9.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2010-04-14 20:43 ` Sukadev Bhattiprolu
[not found] ` <20100414204350.GB24411-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-04-14 20:40 ` Dan Smith
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=20100414204054.GA24411@us.ibm.com \
--to=sukadev-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=ntl-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.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