[CRIU] [PATCH] inet: tcp -- Find size of max memory allowed to restore TCP data, v2

[Frederico Araujo]

Sorry, I meant tcp_rmem and tcp_wmem in my previous email.

Thank you!


On Thu, Oct 10, 2013 at 6:31 PM, Frederico Araujo <araujof at gmail.com> wrote:

> Hi there,
>
> After updating CRIU to the current development version (which contains
> this patch), checkpoint started crashing when dumping established
> connections. The problem is that CRIU can't find tcp_rmem and tcp_rmem on
> the container, although these files exist on the host machine. My host
> machine and lxc container are running both Ubuntu Saucy (latest update).
> Also, my lxc container is running unconfined and the network type is veth,
> linking to a bridge I created.
>
> I understood the reason for this patch. However, should checkpoint fail in
> case these two files are not present? Do you guys know a way to make these
> files available to the guest lxc container? I tried playing with the
> container's fstab, without success.
>
> Any help or comments will be much appreciated!
>
> Best,
> Fred
>
>
>
> On Mon, Oct 7, 2013 at 10:18 AM, Cyrill Gorcunov <gorcunov at gmail.com>wrote:
>
>> On Mon, Oct 07, 2013 at 05:22:09PM +0400, Cyrill Gorcunov wrote:
>> >
>> > Yeah, I'll check the sysctl engine code, thanks! As to read queue -- I
>> think yes,
>> > you're right, I'll update, thanks!
>>
>> Update attached.
>>
>> _______________________________________________
>> CRIU mailing list
>> CRIU at openvz.org
>> https://lists.openvz.org/mailman/listinfo/criu
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20131010/29345a78/attachment-0001.html>