[CRIU] [Announce] Stable 1.3.1 release
Zmudzinski, Krystof C
krystof.c.zmudzinski at intel.com
Mon Sep 15 10:31:12 PDT 2014
Sorry. I meant, should I use ubuntu-lxc/daily?
Krystof
On Sep 15, 2014 10:26 AM, "Zmudzinski, Krystof C" <krystof.c.zmudzinski at intel.com> wrote:
This doesn't work for me:
git clone https://github.com/tych0/lxc
Should I just use the 1.3.1?
Krystof
-----Original Message-----
From: criu-bounces at openvz.org [mailto:criu-bounces at openvz.org] On Behalf Of Zmudzinski, Krystof C
Sent: Friday, September 12, 2014 3:56 PM
To: Tycho Andersen
Cc: CRIU; Pavel Emelyanov
Subject: Re: [CRIU] [Announce] Stable 1.3.1 release
Yes, that was it. I was told to use a different update process.
I'm testing checkpointing right now but may not be done until Monday.
Thanks for all the help.
Krystof
-----Original Message-----
From: Tycho Andersen [mailto:tycho.andersen at canonical.com]
Sent: Friday, September 12, 2014 1:14 PM
To: Zmudzinski, Krystof C
Cc: Pavel Emelyanov; CRIU
Subject: Re: [CRIU] [Announce] Stable 1.3.1 release
On Fri, Sep 12, 2014 at 03:51:55PM +0000, Zmudzinski, Krystof C wrote:
> I installed the dev version of lxc and now all commands except for lxc-start give me this error:
> Insufficent privileges to control test-lxc
Do you by chance still have the old lxc from the packages installed?
The new commands may be loading the old liblxc.so, which can cause problems like this. You can verify with:
criu:~ ldd `which lxc-checkpoint`
linux-vdso.so.1 => (0x00007fff1e7ee000)
liblxc.so.1 => /usr/local/lib/liblxc.so.1 (0x00007fb62a22c000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fb62a00e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fb629c47000)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x00007fb629a42000)
libapparmor.so.1 => /usr/lib/x86_64-linux-gnu/libapparmor.so.1 (0x00007fb629836000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fb629612000)
libseccomp.so.2 => /usr/lib/x86_64-linux-gnu/libseccomp.so.2 (0x00007fb6293fb000)
libcgmanager.so.0 => /lib/x86_64-linux-gnu/libcgmanager.so.0 (0x00007fb6291e0000)
libnih.so.1 => /lib/x86_64-linux-gnu/libnih.so.1 (0x00007fb628fc7000)
libnih-dbus.so.1 => /lib/x86_64-linux-gnu/libnih-dbus.so.1 (0x00007fb628dbd000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007fb628b78000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fb628974000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb62a4ad000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fb628736000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fb628531000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fb628329000)
Note that I'm loading liblxc.so from /usr/local/lib instead of /usr/lib. I have a few instructions on correcting this here:
http://bazaar.launchpad.net/~tycho-s/+junk/snapshot-instructions/view/head:/README
Tycho
> Krystof
>
> -----Original Message-----
> From: Tycho Andersen [mailto:tycho.andersen at canonical.com]
> Sent: Friday, September 12, 2014 8:25 AM
> To: Zmudzinski, Krystof C
> Cc: Pavel Emelyanov; CRIU
> Subject: Re: [CRIU] [Announce] Stable 1.3.1 release
>
> On Fri, Sep 12, 2014 at 03:11:20PM +0000, Zmudzinski, Krystof C wrote:
> > criu restore without -d, run.sh never returns:
> >
> > 28368 pts/18 S+ 0:00 | \_ /bin/bash ./run.sh test-lxc
> > 28442 pts/18 S+ 0:00 | \_ /root/criu-1.3.1/criu restore --evasive-devices --tcp-established --man
> > 28443 ? Ss 0:00 | \_ /sbin/init
> > 28467 ? Ss 0:00 | \_ crond
> > 28468 ? Ss 0:00 | \_ /usr/sbin/httpd
> > 28475 ? S 0:00 | | \_ /usr/sbin/httpd
> > 28469 ? Ss 0:00 | \_ sendmail: Queue runner at 01:00:00 for /var/spool/clientmqueue
> > 28470 ? Ss 0:00 | \_ sendmail: accepting connections
> > 28471 ? Ss 0:00 | \_ /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2
> > 28477 ? S 0:00 | | \_ /usr/sbin/saslauthd -m /var/run/saslauthd -a pam -n 2
> > 28472 ? Ss 0:00 | \_ xinetd -stayalive -pidfile /var/run/xinetd.pid
> > 28473 ? Ss 0:00 | \_ /usr/sbin/sshd
> > 28474 ? Sl 0:00 | \_ /sbin/rsyslogd -i /var/run/syslogd.pid -c 5
> >
> > With -d, the container is gone after restore.
>
> This is presumably related to pdeath_sig? I guess your images have it set.
>
> > Without -d, lxc-info says that the container is not running so I can't lxc-attach.
>
> To make lxc-info work, there is some other lxc infrastructure that needs to be set up. lxc-checkpoint will do this for you.
>
> Tycho
>
> > Krystof
> >
> > -----Original Message-----
> > From: criu-bounces at openvz.org [mailto:criu-bounces at openvz.org] On
> > Behalf Of Pavel Emelyanov
> > Sent: Friday, September 12, 2014 1:26 AM
> > To: CRIU
> > Subject: [CRIU] [Announce] Stable 1.3.1 release
> >
> > Hi all!
> >
> > The spotted nasty problem with root task restore (kudos Tycho) is
> > fixed with explicit option. It's better to have this early than to
> > wait for 1.4 :)
> >
> > Plus, other fixes we've had (with mount points) are also fixed.
> >
> > http://criu.org/Download/criu/1.3.1
> >
> > Thanks,
> > Pavel
> > _______________________________________________
> > CRIU mailing list
> > CRIU at openvz.org
> > https://lists.openvz.org/mailman/listinfo/criu
> >
> > _______________________________________________
> > CRIU mailing list
> > CRIU at openvz.org
> > https://lists.openvz.org/mailman/listinfo/criu
_______________________________________________
CRIU mailing list
CRIU at openvz.org
https://lists.openvz.org/mailman/listinfo/criu
More information about the CRIU
mailing list