https://bugzilla.suse.com/show_bug.cgi?id=1203854 https://bugzilla.suse.com/show_bug.cgi?id=1203854#c1 --- Comment #1 from Takashi Iwai --- I checked criu on Leap 15.4 with 5.19 kernel from OBS Kernel:stable:Backport, and this combination worked. So it's not a regression due to the newer kernel, but rather a breakage of criu on TW, likely due to a newer gcc. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1203854 https://bugzilla.suse.com/show_bug.cgi?id=1203854#c3 Jos� Iv�n L�pez Gonz�lez changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jlopez@suse.com) |needinfo?(tiwai@suse.com) --- Comment #3 from Jos� Iv�n L�pez Gonz�lez --- (In reply to Takashi Iwai from comment #2)

It seems to be a breakage due to the LTO enablement. I turned off the LTO build, and it worked, at least for the local est with simple-loop.

The fix was submitted to TW.

Could you verify with the package in OBS devel:tools/criu?

I have tested the new packages for TW [1] and ALP [2]. In TW everything works as expected (using Btrfs file system). In ALP (also Btrfs but read-only), the criu simple-loop test works, but podman-checkpoint still complains: $ podman container checkpoint distracted_babbage ERRO[0000] container still running ERRO[0000] criu failed: type NOTIFY errno 0 log file: /var/lib/containers/storage/btrfs-containers/ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239/userdata/dump.log Error: `/usr/bin/runc checkpoint --image-path /var/lib/containers/storage/btrfs-containers/ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239/userdata/checkpoint --work-path /var/lib/containers/storage/btrfs-containers/ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239/userdata ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239` failed: exit status 1 $ tail -n 10 /var/lib/containers/storage/btrfs-containers/ee203bab8fadb391481ec3179657eccd3970e3f9acc087ab8869890cd7938239/userdata/dump.log (00.185430) sockets: Sockects collect procedure family AF_INET6 proto IPPROTO_UDPLITE: -2 (00.189057) sockets: Sockects collect procedure family AF_INET6 proto IPPROTO_RAW: -2 (00.192736) sockets: Sockects collect procedure family AF_PACKET proto IPPROTO_IP: -2 (00.196484) sockets: Sockects collect procedure family AF_NETLINK proto IPPROTO_RAW: -2 (00.196555) Unlock network (00.196566) Running network-unlock scripts (00.196587) RPC (00.201989) Unfreezing tasks into 1 (00.202011) Unseizing 1377 into 1 (00.202053) Error (criu/cr-dump.c:2053): Dumping FAILED. I have also tried this workaround [2] without success. Any further idea? Thanks! [1] https://build.opensuse.org/package/show/devel:tools/criu [2] https://build.opensuse.org/package/show/SUSE:ALP/criu [3] https://criu.org/Filesystems_pecularities#BTRFS_Workaround -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1203854 https://bugzilla.suse.com/show_bug.cgi?id=1203854#c5 --- Comment #5 from Takashi Iwai --- That's errors from criu with -ENOENT, indicating the lack of the corresponding modules. Are the kernel modules present on ALP? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1203854 https://bugzilla.suse.com/show_bug.cgi?id=1203854#c6 --- Comment #6 from Jos�� Iv��n L��pez Gonz��lez --- There are quite some kernel modules missing in ALP if you compare it with TW. As pointed by Takashi, some of the missing *diag modules could be needed to make criu to work properly. I asked to Jiri Srain about the missing modules in ALP. The reason is because ALP is using kernel-defaults-base, which only includes a reduced number of modules. Righ now we have two images for ALP (non-encrypted and encrypted). The non-encrypted one includes kernel-defaults-base, and the encrypted one uses kernel-defaults. With the encrypted image criu does not complain when creating a podman container checkpoint. The *diag modules missing in the non-encypted image are: raw_diag, tcp_diag, udp_diag, unix_diag. This issue is relevant even for TW in virtual environments (where you don���t need all drivers). Probably we will need to fix the packaging of kernel to include those missing modules with kernel-defaults-base. -- You are receiving this mail because: You are on the CC list for the bug.