-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RunC post-copy checkpoint failed #4451
Comments
@obsidian0215 can you format the stack trace the same way you formatted the code? The |
I generated the cmd as described in https://github.com/opencontainers/runc/blob/main/man/runc-checkpoint.8.md. The actual executed cmd is 'runc checkpoint --image-path image --shell-job --tcp-established --lazy-pages --page-server localhost:27 --status-fd <fd of p_pipe[1](write end)>'. When the error occurred, criu has completed container's checkpoint. However, without "--status-fd "flags, no error will be print in source, but criu in destination won't work properly. Indeed I'm confused with this flag, when I tried to use runc's post-copy migration like the script shown in https://www.redhat.com/en/blog/container-migration-around-world, I found that the "--status-fd" flag only accept int fd. How can I make criu notify that it has prepared to start lazy migration? |
Thanks for the edits, I understand what you meant now. I'm not familiar with the checkpoint code, so I'll leave this for others to take a look. |
@obsidian0215 I guess we need a full reproducer. |
Description
I want to implement runc's post-copy live migration, so I use following command to use lazy-pages
when I execute my script, I didn't get '\0' read and rather got following error output:
CRIU has created container's checkpoint images successfully, but it also contained pagemap.img and pages.img. Is it expected?
Steps to reproduce the issue
Describe the results you received and expected
What version of runc are you using?
Host OS information
Host kernel information
linux 6.1.111
The text was updated successfully, but these errors were encountered: