[CRIU] crtools error checkpoint/restore error ("Unable to open pstree.img")

[Kevin Wilson]

Hi,
I have 2 short questions if I may:
1) I get some "type unsupported source cgroup" messages in the dump.
log which was attached previously in this thread (see below)
What is the meaning of these messages? Is it normal for them to appear
(my image is with cgroups support)

2) Does checkpoint works with cgroups (like the freezer cgroup)?

regards,
Kevin


(00.028211) type unsupported source cgroup 14 / @
/sys/fs/cgroup/systemd flags 30000e options
release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd,
(00.028233) type unsupported source cgroup 15 / @
/sys/fs/cgroup/cpuset flags 30000e options cpuset,
(00.028352) type unsupported source cgroup 16 / @
/sys/fs/cgroup/cpu,cpuacct flags 30000e options cpuacct,cpu,
(00.028377) type unsupported source cgroup 17 / @
/sys/fs/cgroup/memory flags 30000e options memory,
(00.028399) type unsupported source cgroup 18 / @
/sys/fs/cgroup/devices flags 30000e options devices,
(00.028422) type unsupported source cgroup 19 / @
/sys/fs/cgroup/freezer flags 30000e options freezer,
(00.028444) type unsupported source cgroup 1a / @ /sys/fs/cgroup/blkio
flags 30000e options blkio,
(00.028475) type unsupported source cgroup 1b / @
/sys/fs/cgroup/perf_event flags 30000e options perf_event,

On Tue, Mar 26, 2013 at 8:26 PM, Pavel Emelyanov <xemul at parallels.com> wrote:
> On 03/26/2013 10:21 PM, Kevin Wilson wrote:
>> Hello,
>> First of all, FYI, my tests up till now were performed with crtools
>> 0.4; but from now on I will try with the latest git tree.
>
> Good! You will most likely need the crtools kernel tree. It's the same
> v3.9, but with several patches applied on top, that will appear upstream
> in v3.10 merge window.
>
>> 1)
>>> Am I right, you tried to checkpoint an sshd, which served your connection?
>> Yes. This indeed gave error in **checkpoint**. Then after reboot, I
>> tried directly on the machine itself, and this time
>> it worked. It could be that checpointing over sshd connection should
>> work and this is considered a BUG. I will try to understand it more
>> deeply.
>
> OK.
>
>> 2) adding -x for restore did not help. I have the same problem still
>> and the same error as restore gave before (the error I posted)
>
> This may indicate, that the peer of the socket you're trying to restore
> doesn't exist. That's is why we put external unix sockets under option --
> when using one, you must make sure, that the peer socket exists yourself,
> crtools can't do it.
>
>> 3)
>>> BTW, have you applied two patches I've recently sent? If no, please do.
>> I cloned the git tree about an  hour ago, and "git log" showed
>> dump: Missing \n in pr_err message, from two hours ago, which means
>> that the two last patches were not in the tree yet. I see now that
>> they are in the tree.
>
> Yes, I've applied them 20 minutes ago.
>
>> Should I try  restore with -x with the new patches ?
>
> Yes, they will provide more descriptive logging.
>
>> Best,
>> Kevin
>
> Thanks,
> Pavel