<div dir="ltr"><br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Urgen Sherpa</b> <span dir="ltr"><<a href="mailto:urgen.sherpa@nepallink.net">urgen.sherpa@nepallink.net</a>></span><br>
Date: Mon, Feb 10, 2014 at 12:49 PM<br>Subject: Re: [CRIU] CRIU LXC error<br>To: David Shwatrz <<a href="mailto:dshwatrz@gmail.com">dshwatrz@gmail.com</a>><br><br><br><div dir="ltr"><div>Thank you all for the reply,i added lxc.tty=0 as well as lxc.console=none in "/var/lib/lxc/test-container/config" and also in Host Ubuntu files.<br>
The output later was::<br>root@ktmnp:/var/lib/lxc/test-container# lxc-info -n test-container<br>
state: RUNNING<br>pid: 1634<br>root@ktmnp:/home/nplink/criu-1.1# ./criu dump -t 1634 -D /dumps --ext-unix-sk --tcp-established --file-locks -o dump.log<br>root@ktmnp:/home/nplink/criu-1.1# cat /dumps/dump.log <br>
Error (parasite-syscall.c:387): si_code=4 si_pid=1920 si_status=5<br>
Error (parasite-syscall.c:387): si_code=4 si_pid=1921 si_status=5<br>Error (parasite-syscall.c:387): si_code=4 si_pid=1922 si_status=5<br>Error (tty.c:203): tty: Can't obtain ptmx index: Inappropriate ioctl for device<br>
Error (cr-dump.c:1493): Dump files (pid: 2073) failed with -1<div class=""><br>Error (cr-dump.c:1828): Dumping FAILED.<br></div>root@ktmnp:/home/nplink/criu-1.1# <br><br></div><div>here is what the config file of container looks like<br>
root@ktmnp:/var/lib/lxc/test-container# ls<br>
config fstab lxc_snapshots rootfs rootfs.hold<br>root@ktmnp:/var/lib/lxc/test-container# cat config <br>lxc.console = none<br>lxc.network.type = veth<br>lxc.network.hwaddr = 00:16:3e:b3:f5:95<br>lxc.network.flags = up<br>
lxc.network.link = lxcbr0<br>lxc.rootfs = /var/lib/lxc/test-container/rootfs<br>lxc.mount = /var/lib/lxc/test-container/fstab<br>lxc.pivotdir = lxc_putold<br>lxc.devttydir = lxc<br>lxc.tty = 0<br>lxc.pts = 1024<br>lxc.utsname = test-container<br>
lxc.arch = amd64<br>lxc.cap.drop = sys_module mac_admin mac_override sys_time<br>lxc.cgroup.memory.limit_in_bytes = 1994M<br><br>lxc.cgroup.devices.deny = a<br>lxc.cgroup.devices.allow = c *:* m<br>lxc.cgroup.devices.allow = b *:* m<br>
lxc.cgroup.devices.allow = c 1:3 rwm<br>lxc.cgroup.devices.allow = c 1:5 rwm<br>lxc.cgroup.devices.allow = c 5:1 rwm<br>lxc.cgroup.devices.allow = c 5:0 rwm<br>lxc.cgroup.devices.allow = c 1:9 rwm<br>lxc.cgroup.devices.allow = c 1:8 rwm<br>
lxc.cgroup.devices.allow = c 136:* rwm<br>lxc.cgroup.devices.allow = c 5:2 rwm<br>lxc.cgroup.devices.allow = c 254:0 rm<br>lxc.cgroup.devices.allow = c 10:229 rwm<br>lxc.cgroup.devices.allow = c 10:200 rwm<br>lxc.cgroup.devices.allow = c 1:7 rwm<br>
lxc.cgroup.devices.allow = c 10:228 rwm<br>lxc.cgroup.devices.allow = c 10:232 rwm<br></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Sun, Feb 9, 2014 at 9:34 PM, David Shwatrz <span dir="ltr"><<a href="mailto:dshwatrz@gmail.com" target="_blank">dshwatrz@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
Isn't the "External unix sockets" CRIU plugin supposed to solve this<br>
and to support external terminals?<br>
<br>
see: <a href="http://criu.org/Plugins" target="_blank">http://criu.org/Plugins</a><br>
<br>
DavidS<br>
<div><div><br>
On Sun, Feb 9, 2014 at 2:31 PM, Andrew Vagin <<a href="mailto:avagin@parallels.com" target="_blank">avagin@parallels.com</a>> wrote:<br>
> On Sun, Feb 09, 2014 at 11:31:23AM +0545, Urgen Sherpa wrote:<br>
>> Hello,<br>
>> system used: ubuntu 13.1 X64bit RAM: 2G (in VMware workstation 10.0.0)<br>
>> i was trying to check point lxc container[container=ubuntu 12.04] (using CRIU<br>
>> which i compiled from source using make).<br>
>> steps followed to check point were:-<br>
>> ////below commands are executed outside the container///////<br>
>> //also the console is none(by adding lxc.console=none in file /var/lib/lxc/<br>
>> test-container ) and udev disabled with command<br>
>> ( mv /sbin/udevd{,.bcp} )<br>
>> #lxc-create -n test-container -t ubuntu<br>
>><br>
>> #lxc-start -n test-container -d<br>
>><br>
>> # lxc-info --name test-container<br>
>> state: RUNNING<br>
>> pid: 1647<br>
>> root@ktmnp:/home/criu-1.1# ./criu dump -t 1647 -D /dumps/ --tcp-established<br>
>> --file-locks<br>
>> Error (parasite-syscall.c:387): si_code=4 si_pid=1936 si_status=5<br>
>> Error (parasite-syscall.c:387): si_code=4 si_pid=1939 si_status=5<br>
>> Error (parasite-syscall.c:387): si_code=4 si_pid=1940 si_status=5<br>
>> Error (tty.c:222): tty: Unexpected format on path /dev/lxc/tty4<br>
>> Error (cr-dump.c:1493): Dump files (pid: 2037) failed with -1<br>
>> Error (cr-dump.c:1828): Dumping FAILED.<br>
>><br>
>> any help/ suggestions please!<br>
><br>
> CRIU doesn't support external terminals. You can add two lines in CT's<br>
> config file<br>
><br>
> lxc.console = none<br>
> lxc.tty = 0<br>
><br>
> <a href="http://criu.org/LXC" target="_blank">http://criu.org/LXC</a><br>
><br>
>> _______________________________________________<br>
>> CRIU mailing list<br>
>> <a href="mailto:CRIU@openvz.org" target="_blank">CRIU@openvz.org</a><br>
>> <a href="https://lists.openvz.org/mailman/listinfo/criu" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
><br>
> _______________________________________________<br>
> CRIU mailing list<br>
> <a href="mailto:CRIU@openvz.org" target="_blank">CRIU@openvz.org</a><br>
> <a href="https://lists.openvz.org/mailman/listinfo/criu" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><div dir="ltr"><br>Warm Regards<br>Urgen sherpa<br>Technical support<br>NepalLink Networks (<a href="http://www.nepallink.net" target="_blank">www.nepallink.net</a>)
<div><br></div>The information contained in this e-mail and any
accompanying documents may contain information that is confidential or
otherwise protected from disclosure. If you are not the intended
recipient of this message, please immediately alert the sender by reply
e-mail and then delete this message. Any dissemination, distribution or
other use of the contents of this message by anyone other than the
intended recipient is strictly prohibited. Nepallink Network has taken
every reasonable precaution to minimize the risk, but is not liable for
any damage you may sustain as a result of any virus in this e-mail. You
should carry out your own virus checks before opening the e-mail or
attachment</div>
</font></span></div></div>
</div><br><br clear="all"><br>-- <br><div dir="ltr"><br>Warm Regards<br>Urgen sherpa<br>Technical support<br>NepalLink Networks (<a href="http://www.nepallink.net" target="_blank">www.nepallink.net</a>)
<div><br></div>The information contained in this e-mail and any
accompanying documents may contain information that is confidential or
otherwise protected from disclosure. If you are not the intended
recipient of this message, please immediately alert the sender by reply
e-mail and then delete this message. Any dissemination, distribution or
other use of the contents of this message by anyone other than the
intended recipient is strictly prohibited. Nepallink Network has taken
every reasonable precaution to minimize the risk, but is not liable for
any damage you may sustain as a result of any virus in this e-mail. You
should carry out your own virus checks before opening the e-mail or
attachment</div>
</div>