-
Notifications
You must be signed in to change notification settings - Fork 554
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
criu dump failed for /dev/fb0 #527
Comments
You hit one of the 'what cannot be dumped' points https://criu.org/What_cannot_be_checkpointed#Devices What does your program do with |
Hello, Thanks for the reply, I dont exactly know the detail but I believe it is frame buffer where our SoC uses it to draw things to screen / or maybe it is SoC GPU device. Based on the info you provided to me, does it means all UI based application that uses gpu to draw cant be dumped? Thanks a lot |
It is not possible to dump applications using the GPU, as CRIU does not know how to extract the state of the GPU, which CRIU needs for the restore. If your application is writing to a VNC session it is possible (https://criu.org/VNC). CRIU also offers the possibility to write plugins: https://criu.org/Plugins So if you know how to get the state of the GPU dumped you could solve your problem with a CRIU plugin. |
okay then, Thanks a lot for your help and info |
Hello I'm trying to use criu on my custom embedded (arm) project.
I'm able to dump and restore simple loop example and now I'm trying to dump my real example and I got failed with following error:
when I check the process map, this is what I got:
86aaa000-86ab4000 rw-s 86aaa000 fe:01 1691 /dev/fb/0
86ab4000-8a67f000 rw-s 86ab4000 fe:01 1691 /dev/fb/0
Could you help me on this issue? Thanks
The text was updated successfully, but these errors were encountered: