[CRIU] VNC Server + GUI applications question

[Pavel Emelyanov]

On 05/24/2014 02:36 AM, J F wrote:
> CRIU team,
> 
> I watched the cool CRIU video on youtube and presentation:
> https://www.youtube.com/watch?v=j4wlYY7lTDw
> http://lvee.org/uploads/image_upload/file/311/fedora-test-day.odp.pdf
> 
> I'm using vnc4server with a shell and a UI app running like this:
> 
>  1770 pts/2    S      0:04 Xvnc4 :2 -desktop ip-16-118-238-44:2 (ubuntu) -auth /
>  1776 pts/2    S      0:00 vncconfig -iconic
>  1777 pts/2    S      0:00 xterm -class UXTerm -title uxterm -u8 -geometry 80x24
>  1784 pts/3    Ss     0:00  \_ -bash
>  2119 pts/3    Sl+    1:51      \_ /mnt/mydata/MYAPP
> 
> I then do a dump on "1770", but get an error:
> 
> Error (parasite-syscall.c:387): si_code=1 si_pid=2328 si_status=0
> Error (parasite-syscall.c:387): si_code=1 si_pid=2330 si_status=0
> Error (cr-dump.c:386): Task 1770 with SysVIPC shmem map @7f3a4de0b000 doesn't live in IPC ns

Here it is. X apps use SysVIPC shmem to communicate. The problem with SysVIPC is that
tasks do not _explicitly_ reference any object in it, and we shouldn't dump all the IPC
stuff. Thus, for such things we require IPC namespace to be involved.

Here's a HOWTO article that describes how to do what is shown on a video:
http://criu.org/VNC

> Error (cr-dump.c:1588): Dump mappings (pid: 1770) failed with -1
> Error (cr-dump.c:1870): Dumping FAILED.
> 
> I can post the -v4 log, but wanted to check if my fundamental setup is correct or if there are
> any limitations. I'm open to any kind of vncserver, window manager, etc. 

Thanks,
Pavel