cri-o: `test/checkpoint.bats` tests don't work on `linux/arm64`

https://github.com/cri-o/cri-o/pull/7620 shows that the tests have to be disabled to let the CI pass on the linux/arm64 platform.

Goal of this issue is to investigate why the tests fail and fix them appropriately.

/help /good-first-issue

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 31 (22 by maintainers)

Commits related to this issue

Most upvoted comments

Cool. From my point of view that should be an acceptable workaround for now. Disabling “restartable sequences” from my understanding should not be a problem.

Those settings were added as requested.

Firecracker runs a very minimal Kernel, we had to work really hard to add everything in for containers, then for BPF, then for BTF etc.

That was a quick turnaround, nice.

To fix the next errors something like this might be needed:

CONFIG_UNIX_DIAG=y CONFIG_INET_DIAG=y CONFIG_INET_UDP_DIAG=y CONFIG_PACKET_DIAG=y CONFIG_NETLINK_DIAG=y CONFIG_NETFILTER_XT_MARK=y CONFIG_INET_TCP_DIAG=y CONFIG_INET_UDP_DIAG=y CONFIG_INET_RAW_DIAG=y

There is an outdated page what needs to exist: https://criu.org/Linux_kernel

From that page I know that CONFIG_MEM_SOFT_DIRTY=y does not exist on arm64. Besides that most of those options should be turned on.

Error (compel/src/lib/ptrace.c:27): suspending seccomp failed: Invalid argument

Yes, that is the problem. Looking at

https://github.com/torvalds/linux/blob/master/kernel/ptrace.c#L363

I am pretty sure they do not have CONFIG_CHECKPOINT_RESTORE=y in their kernel config.

Do you have any way to request that?

# (00.000084) File /run/criu.kdat does not exist, and couldn't get the file to sneak in

@prakrit55 that is irrelevant

@saschagrunert, I would like to give it a try