[CRIU] How to pre-dump lxc or docker?
陈晓
chenxiao_study at 126.com
Thu Sep 25 02:46:20 PDT 2014
ok, thank you for your reply, I will try it!<br/> carl
At 2014-09-25 17:40:17, "Pavel Emelyanov" <xemul at parallels.com> wrote:
>On 09/24/2014 08:20 PM, Tycho Andersen wrote:
>> On Wed, Sep 24, 2014 at 08:06:24PM +0800, 陈晓 wrote:
>>> Becasue I want to dump lxc by copy on write and less the freeze time. The command lxc-checkpoint does not support --pre-images-dir,so I can not dump lxc by pre-dump.So I do not know how to pre-dump lxc.
>>
>> You might be able to just take the command line that LXC uses and
>> s/dump/pre-dump, I've not tried it but it might work :).
>
>It's not that easy :) If you want to decrease the freeze time with that
>then you should start the memory tracker (--track-mem) and on the next
>dump say where previous images are (--prev-img-dir).
>
>Not that I'm trying to enforce this feature in lxc. Just to let you know.
>
>> I think this is something we would like to add (patches welcome :),
>> but for now the main focus is on making the current implementation of
>> lxc-checkpoint solid.
>>
>> Tycho
>>
>>> thanks,
>>> carl
>>> 在 2014-09-24 19:43:27,"Pavel Emelyanov" <xemul at parallels.com> 写道:
>>> On 09/24/2014 03:29 PM, 陈晓 wrote:
>>>> I hava dumped the lxc successfully with lxc tools, but how can I pre-dump lxc,
>>>> the command lxc-checkpoint do not support pre-dump.
>>>
>>> Presumably you can pre-dump one manually, then dump and restore using
>>> LXC tools.
>>>
>>> Why do you need pre-dump?
>>>
>>> Thanks,
>>> Pavel
>>>
>>
>
More information about the CRIU
mailing list