[prev in list] [next in list] [prev in thread] [next in thread]
List: openvz-criu
Subject: [CRIU] incremental checkpoint
From: Shivam Mehra <mshivam2196 () gmail ! com>
Date: 2020-10-15 12:57:00
Message-ID: CANp2S659sruhZoZcceh8JhFRghwvciODEdR1cpFFbprToZCQ=w () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Is it possible to do incremental checkpointing in runc with full dumps?
In criu, we can do incremental checkpoints by doing
criu dump --tree <pid> --images-dir <path-to-existing-directory-B> \
--prev-images-dir <path-to-directory-A-relative-to-B> --leave-stopped
--track-mem
from the help option of runc, it says we can use
--parent-path value path for previous criu image files in pre-dump option but
in case of pre-dumps only, Is there similar thing in runc which can do
incremental checkpointing with full dumps also?
[Attachment #5 (text/html)]
<div dir="ltr"><p style="box-sizing:border-box;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe \
UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI \
Emoji";font-size:14px;margin-top:0px">Is it possible to do incremental \
checkpointing in <code \
style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation \
Mono",Menlo,monospace;font-size:11.9px;padding:0.2em \
0.4em;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:6px">runc</code> \
with full <code style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation \
Mono",Menlo,monospace;font-size:11.9px;padding:0.2em \
0.4em;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:6px">dumps</code>?<br \
style="box-sizing:border-box">In criu, we can do incremental checkpoints by \
doing</p><pre style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation \
Mono",Menlo,monospace;font-size:11.9px;margin-top:0px;margin-bottom:16px;padding: \
16px;overflow:auto;line-height:1.45;background-color:rgb(246,248,250);border-radius:6px;color:rgb(36,41,46)"><code \
style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation \
Mono",Menlo,monospace;padding:0px;margin:0px;background:initial;border-radius:6px \
;word-break:normal;border:0px;display:inline;overflow:visible;line-height:inherit">criu \
dump --tree <pid> --images-dir \
<path-to-existing-directory-B> \
--prev-images-dir <path-to-directory-A-relative-to-B> --leave-stopped \
--track-mem </code></pre><p \
style="box-sizing:border-box;margin-top:0px;color:rgb(36,41,46);font-family:-apple-system,BlinkMacSystemFont,"Segoe \
UI",Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe UI \
Emoji";font-size:14px;margin-bottom:0px">from the help option of runc, it says \
we can use<br style="box-sizing:border-box"><code \
style="box-sizing:border-box;font-family:SFMono-Regular,Consolas,"Liberation \
Mono",Menlo,monospace;font-size:11.9px;padding:0.2em \
0.4em;margin:0px;background-color:rgba(27,31,35,0.05);border-radius:6px">--parent-path \
value path for previous criu image files in pre-dump option</code> but in case of \
pre-dumps only, Is there similar thing in runc which can do incremental checkpointing \
with full dumps also?</p></div>
_______________________________________________
CRIU mailing list
CRIU@openvz.org
https://lists.openvz.org/mailman/listinfo/criu
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic