Error compiling CRtools-0.1..

Error compiling CRtools-0.1..

[Muralidhar, Rajeev D]

OK it seems like one error was that 

#include "restorer.h" 

Was missing from syscall-common-x86-64., which has the definition of rcx.

Now I can proceed one step further in compilation, but I get these errors:

In file included from ./include/types.h:7,
                 from ./include/restorer.h:8,
                 from syscall-common-x86-64.S:2,
                 from syscall-x86-64.S:3:
./include/bitops.h:50:3: error: #error x86-32 is not implemented yet
In file included from ./include/restorer.h:8,
                 from syscall-common-x86-64.S:2,
                 from syscall-x86-64.S:3:
./include/types.h:180:3: error: #error x86-32 bit mode not yet implemented
In file included from ./include/syscall.h:4,
                 from ./include/lock.h:11,
                 from ./include/restorer.h:10,
                 from syscall-common-x86-64.S:2,
                 from syscall-x86-64.S:3:
./include/syscall-types.h:17:3: error: #error x86-32 bit mode not yet implemented
In file included from syscall-common-x86-64.S:2,
                 from syscall-x86-64.S:3:
./include/restorer.h:20:3: error: #error Only x86-64 is supported

I have a Core i5 laptop, running Ubuntu 10.04. uname -m shows "i686". 

Does this mean that CR tools will run only on x86_64, but will never work on 32-bit systems? (Isnt Intel x86_64 is backward compatible with 32-bit?)

Thanks for your help in advance. 
Rajeev


-----Original Message-----
From: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org [mailto:containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org] On Behalf Of Muralidhar, Rajeev D
Sent: Tuesday, August 28, 2012 2:12 PM
To: Serge Hallyn
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: RE: Linux C/R: VNC server/Xterm checkpoint/recovery

I forgot to mention that I am doing on this on a Ubuntu 10.04, and uname -a shows "i686"

Thanks
Rajeev


-----Original Message-----
From: Muralidhar, Rajeev D 
Sent: Tuesday, August 28, 2012 1:56 PM
To: Serge Hallyn
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org; Muralidhar, Rajeev D
Subject: RE: Linux C/R: VNC server/Xterm checkpoint/recovery

Hi all,

I got started with the information on http://criu.org/Main_Page 

I installed the linux-cr.git tree, compiled & have that ready. 

For CR-tools, I got all the required packages, but I am not able to compile crtools. This is the error I am seeing. Can someone pls let me know why I am getting this error?

rdmurali@ubuntu:~/Linux-CR/crtools$ make
  PROTOBUF inventory.pb-c.c
  CC       inventory.pb-c.o
  PROTOBUF fdinfo.pb-c.c
  CC       fdinfo.pb-c.o
  PROTOBUF fown.pb-c.c
  CC       fown.pb-c.o
  PROTOBUF regfile.pb-c.c
  CC       regfile.pb-c.o
  PROTOBUF ghost-file.pb-c.c
  CC       ghost-file.pb-c.o
  PROTOBUF fifo.pb-c.c
  CC       fifo.pb-c.o
  PROTOBUF remap-file-path.pb-c.c
  CC       remap-file-path.pb-c.o
  PROTOBUF eventfd.pb-c.c
  CC       eventfd.pb-c.o
  PROTOBUF eventpoll.pb-c.c
  CC       eventpoll.pb-c.o
  PROTOBUF fh.pb-c.c
  CC       fh.pb-c.o
  PROTOBUF inotify.pb-c.c
  CC       inotify.pb-c.o
  PROTOBUF signalfd.pb-c.c
  CC       signalfd.pb-c.o
  PROTOBUF fs.pb-c.c
  CC       fs.pb-c.o
  PROTOBUF pstree.pb-c.c
  CC       pstree.pb-c.o
  PROTOBUF pipe.pb-c.c
  CC       pipe.pb-c.o
  PROTOBUF tcp-stream.pb-c.c
  CC       tcp-stream.pb-c.o
  PROTOBUF sk-packet.pb-c.c
  CC       sk-packet.pb-c.o
  PROTOBUF mnt.pb-c.c
  CC       mnt.pb-c.o
  PROTOBUF pipe-data.pb-c.c
  CC       pipe-data.pb-c.o
  PROTOBUF sa.pb-c.c
  CC       sa.pb-c.o
  PROTOBUF itimer.pb-c.c
  CC       itimer.pb-c.o
  PROTOBUF mm.pb-c.c
  CC       mm.pb-c.o
  PROTOBUF sk-opts.pb-c.c
  CC       sk-opts.pb-c.o
  PROTOBUF sk-unix.pb-c.c
  CC       sk-unix.pb-c.o
  PROTOBUF sk-inet.pb-c.c
  CC       sk-inet.pb-c.o
  PROTOBUF packet-sock.pb-c.c
  CC       packet-sock.pb-c.o
packet-sock.pb-c.c: In function 'packet_sock_entry__init':
packet-sock.pb-c.c:98: warning: this decimal constant is unsigned only in ISO C90
packet-sock.pb-c.c: At top level:
packet-sock.pb-c.c:318: warning: this decimal constant is unsigned only in ISO C90
  PROTOBUF ipc-var.pb-c.c
  CC       ipc-var.pb-c.o
  PROTOBUF ipc-desc.pb-c.c
  CC       ipc-desc.pb-c.o
  PROTOBUF ipc-shm.pb-c.c
  CC       ipc-shm.pb-c.o
  PROTOBUF ipc-msg.pb-c.c
  CC       ipc-msg.pb-c.o
  PROTOBUF ipc-sem.pb-c.c
  CC       ipc-sem.pb-c.o
  PROTOBUF utsns.pb-c.c
  CC       utsns.pb-c.o
  PROTOBUF creds.pb-c.c
  CC       creds.pb-c.o
  PROTOBUF vma.pb-c.c
  CC       vma.pb-c.o
  PROTOBUF core.pb-c.c
  CC       core.pb-c.o
  PROTOBUF netdev.pb-c.c
  CC       netdev.pb-c.o
  LINK     protobuf-lib.o
  GEN      syscall-x86-64.S
  CC       syscall-x86-64.o
syscall-common-x86-64.S: Assembler messages:
syscall-common-x86-64.S:13: Error: bad register name `%rcx'
make[1]: *** [syscall-x86-64.o] Error 1
make: *** [pie] Error 2


thanks
Rajeev

-----Original Message-----
From: Serge Hallyn [mailto:serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org] 
Sent: Tuesday, August 21, 2012 3:04 AM
To: Muralidhar, Rajeev D
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Linux C/R: VNC server/Xterm checkpoint/recovery

See http://criu.org/Main_Page

Quoting Muralidhar, Rajeev D (rajeev.d.muralidhar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org):
> Hi,
> 
> Any help on this? 
> 
> Thanks
> Rajeev
> 
> 
> -----Original Message-----
> From: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org [mailto:containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org] On Behalf Of Muralidhar, Rajeev D
> Sent: Tuesday, August 14, 2012 4:00 PM
> To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> Subject: Linux C/R: VNC server/Xterm checkpoint/recovery
> 
> HI all,
> 
> I am a newbie to Linux C/R. Can someone please tell me if I can checkpoint and restart VNC sessions with Linux C/R? what is the easiest way to test this out? Also, if the VNC session was running Xterms, will they be restored with Linux C/R? 
> 
> Thanks,
> Rajeev
> 
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linuxfoundation.org/mailman/listinfo/containers
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linuxfoundation.org/mailman/listinfo/containers
_______________________________________________
Containers mailing list
Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

RE: Error compiling CRtools-0.1..

[Muralidhar, Rajeev D]

OK I could fix all compilation issues by moving to a x86_64 OS and having the following packages (it would be good to update the wiki page, I can provide the detailed steps I had to take to the owner, pls let me know)

			§ Sudo apt-get install libprotobuf-dev
			§ Sudo apt-get install libprotoc-dev
			§ sudo apt-get install protobuf-c-compiler
			§ sudo apt-get install libprotobuf-c0
			§ sudo apt-get install libprotobuf-c0-dev

Now, when trying to test crtools, I get the following error:

$ ./crtools check
Error (sk-unix.c: 283): Can't stat socket 12547 (./var/run/sdp): Bad file descriptor

And a whole bunch of such errors.

What might the problem be? Am I missing some netlink library? I have installed libnetlink, libnl, libnl-dev.

Thanks
Rajeev

-----Original Message-----
From: Muralidhar, Rajeev D 
Sent: Tuesday, August 28, 2012 4:40 PM
To: Muralidhar, Rajeev D; Serge Hallyn
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Error compiling CRtools-0.1..

OK it seems like one error was that 

#include "restorer.h" 

Was missing from syscall-common-x86-64., which has the definition of rcx.

Now I can proceed one step further in compilation, but I get these errors:

In file included from ./include/types.h:7,
                 from ./include/restorer.h:8,
                 from syscall-common-x86-64.S:2,
                 from syscall-x86-64.S:3:
./include/bitops.h:50:3: error: #error x86-32 is not implemented yet In file included from ./include/restorer.h:8,
                 from syscall-common-x86-64.S:2,
                 from syscall-x86-64.S:3:
./include/types.h:180:3: error: #error x86-32 bit mode not yet implemented In file included from ./include/syscall.h:4,
                 from ./include/lock.h:11,
                 from ./include/restorer.h:10,
                 from syscall-common-x86-64.S:2,
                 from syscall-x86-64.S:3:
./include/syscall-types.h:17:3: error: #error x86-32 bit mode not yet implemented In file included from syscall-common-x86-64.S:2,
                 from syscall-x86-64.S:3:
./include/restorer.h:20:3: error: #error Only x86-64 is supported

I have a Core i5 laptop, running Ubuntu 10.04. uname -m shows "i686". 

Does this mean that CR tools will run only on x86_64, but will never work on 32-bit systems? (Isnt Intel x86_64 is backward compatible with 32-bit?)

Thanks for your help in advance. 
Rajeev


-----Original Message-----
From: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org [mailto:containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org] On Behalf Of Muralidhar, Rajeev D
Sent: Tuesday, August 28, 2012 2:12 PM
To: Serge Hallyn
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: RE: Linux C/R: VNC server/Xterm checkpoint/recovery

I forgot to mention that I am doing on this on a Ubuntu 10.04, and uname -a shows "i686"

Thanks
Rajeev


-----Original Message-----
From: Muralidhar, Rajeev D
Sent: Tuesday, August 28, 2012 1:56 PM
To: Serge Hallyn
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org; Muralidhar, Rajeev D
Subject: RE: Linux C/R: VNC server/Xterm checkpoint/recovery

Hi all,

I got started with the information on http://criu.org/Main_Page 

I installed the linux-cr.git tree, compiled & have that ready. 

For CR-tools, I got all the required packages, but I am not able to compile crtools. This is the error I am seeing. Can someone pls let me know why I am getting this error?

rdmurali@ubuntu:~/Linux-CR/crtools$ make
  PROTOBUF inventory.pb-c.c
  CC       inventory.pb-c.o
  PROTOBUF fdinfo.pb-c.c
  CC       fdinfo.pb-c.o
  PROTOBUF fown.pb-c.c
  CC       fown.pb-c.o
  PROTOBUF regfile.pb-c.c
  CC       regfile.pb-c.o
  PROTOBUF ghost-file.pb-c.c
  CC       ghost-file.pb-c.o
  PROTOBUF fifo.pb-c.c
  CC       fifo.pb-c.o
  PROTOBUF remap-file-path.pb-c.c
  CC       remap-file-path.pb-c.o
  PROTOBUF eventfd.pb-c.c
  CC       eventfd.pb-c.o
  PROTOBUF eventpoll.pb-c.c
  CC       eventpoll.pb-c.o
  PROTOBUF fh.pb-c.c
  CC       fh.pb-c.o
  PROTOBUF inotify.pb-c.c
  CC       inotify.pb-c.o
  PROTOBUF signalfd.pb-c.c
  CC       signalfd.pb-c.o
  PROTOBUF fs.pb-c.c
  CC       fs.pb-c.o
  PROTOBUF pstree.pb-c.c
  CC       pstree.pb-c.o
  PROTOBUF pipe.pb-c.c
  CC       pipe.pb-c.o
  PROTOBUF tcp-stream.pb-c.c
  CC       tcp-stream.pb-c.o
  PROTOBUF sk-packet.pb-c.c
  CC       sk-packet.pb-c.o
  PROTOBUF mnt.pb-c.c
  CC       mnt.pb-c.o
  PROTOBUF pipe-data.pb-c.c
  CC       pipe-data.pb-c.o
  PROTOBUF sa.pb-c.c
  CC       sa.pb-c.o
  PROTOBUF itimer.pb-c.c
  CC       itimer.pb-c.o
  PROTOBUF mm.pb-c.c
  CC       mm.pb-c.o
  PROTOBUF sk-opts.pb-c.c
  CC       sk-opts.pb-c.o
  PROTOBUF sk-unix.pb-c.c
  CC       sk-unix.pb-c.o
  PROTOBUF sk-inet.pb-c.c
  CC       sk-inet.pb-c.o
  PROTOBUF packet-sock.pb-c.c
  CC       packet-sock.pb-c.o
packet-sock.pb-c.c: In function 'packet_sock_entry__init':
packet-sock.pb-c.c:98: warning: this decimal constant is unsigned only in ISO C90
packet-sock.pb-c.c: At top level:
packet-sock.pb-c.c:318: warning: this decimal constant is unsigned only in ISO C90
  PROTOBUF ipc-var.pb-c.c
  CC       ipc-var.pb-c.o
  PROTOBUF ipc-desc.pb-c.c
  CC       ipc-desc.pb-c.o
  PROTOBUF ipc-shm.pb-c.c
  CC       ipc-shm.pb-c.o
  PROTOBUF ipc-msg.pb-c.c
  CC       ipc-msg.pb-c.o
  PROTOBUF ipc-sem.pb-c.c
  CC       ipc-sem.pb-c.o
  PROTOBUF utsns.pb-c.c
  CC       utsns.pb-c.o
  PROTOBUF creds.pb-c.c
  CC       creds.pb-c.o
  PROTOBUF vma.pb-c.c
  CC       vma.pb-c.o
  PROTOBUF core.pb-c.c
  CC       core.pb-c.o
  PROTOBUF netdev.pb-c.c
  CC       netdev.pb-c.o
  LINK     protobuf-lib.o
  GEN      syscall-x86-64.S
  CC       syscall-x86-64.o
syscall-common-x86-64.S: Assembler messages:
syscall-common-x86-64.S:13: Error: bad register name `%rcx'
make[1]: *** [syscall-x86-64.o] Error 1
make: *** [pie] Error 2


thanks
Rajeev

-----Original Message-----
From: Serge Hallyn [mailto:serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org]
Sent: Tuesday, August 21, 2012 3:04 AM
To: Muralidhar, Rajeev D
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Linux C/R: VNC server/Xterm checkpoint/recovery

See http://criu.org/Main_Page

Quoting Muralidhar, Rajeev D (rajeev.d.muralidhar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org):
> Hi,
> 
> Any help on this? 
> 
> Thanks
> Rajeev
> 
> 
> -----Original Message-----
> From: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org 
> [mailto:containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org] On Behalf Of 
> Muralidhar, Rajeev D
> Sent: Tuesday, August 14, 2012 4:00 PM
> To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> Subject: Linux C/R: VNC server/Xterm checkpoint/recovery
> 
> HI all,
> 
> I am a newbie to Linux C/R. Can someone please tell me if I can checkpoint and restart VNC sessions with Linux C/R? what is the easiest way to test this out? Also, if the VNC session was running Xterms, will they be restored with Linux C/R? 
> 
> Thanks,
> Rajeev
> 
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linuxfoundation.org/mailman/listinfo/containers
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linuxfoundation.org/mailman/listinfo/containers
_______________________________________________
Containers mailing list
Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

Re: Error compiling CRtools-0.1..

[Serge Hallyn]

Please cc: criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org (I've cc:d them here) on crtools questions.

-serge

Quoting Muralidhar, Rajeev D (rajeev.d.muralidhar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org):
> OK I could fix all compilation issues by moving to a x86_64 OS and having the following packages (it would be good to update the wiki page, I can provide the detailed steps I had to take to the owner, pls let me know)
> 
> 			§ Sudo apt-get install libprotobuf-dev
> 			§ Sudo apt-get install libprotoc-dev
> 			§ sudo apt-get install protobuf-c-compiler
> 			§ sudo apt-get install libprotobuf-c0
> 			§ sudo apt-get install libprotobuf-c0-dev
> 
> Now, when trying to test crtools, I get the following error:
> 
> $ ./crtools check
> Error (sk-unix.c: 283): Can't stat socket 12547 (./var/run/sdp): Bad file descriptor
> 
> And a whole bunch of such errors.
> 
> What might the problem be? Am I missing some netlink library? I have installed libnetlink, libnl, libnl-dev.
> 
> Thanks
> Rajeev
> 
> -----Original Message-----
> From: Muralidhar, Rajeev D 
> Sent: Tuesday, August 28, 2012 4:40 PM
> To: Muralidhar, Rajeev D; Serge Hallyn
> Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> Subject: Error compiling CRtools-0.1..
> 
> OK it seems like one error was that 
> 
> #include "restorer.h" 
> 
> Was missing from syscall-common-x86-64., which has the definition of rcx.
> 
> Now I can proceed one step further in compilation, but I get these errors:
> 
> In file included from ./include/types.h:7,
>                  from ./include/restorer.h:8,
>                  from syscall-common-x86-64.S:2,
>                  from syscall-x86-64.S:3:
> ./include/bitops.h:50:3: error: #error x86-32 is not implemented yet In file included from ./include/restorer.h:8,
>                  from syscall-common-x86-64.S:2,
>                  from syscall-x86-64.S:3:
> ./include/types.h:180:3: error: #error x86-32 bit mode not yet implemented In file included from ./include/syscall.h:4,
>                  from ./include/lock.h:11,
>                  from ./include/restorer.h:10,
>                  from syscall-common-x86-64.S:2,
>                  from syscall-x86-64.S:3:
> ./include/syscall-types.h:17:3: error: #error x86-32 bit mode not yet implemented In file included from syscall-common-x86-64.S:2,
>                  from syscall-x86-64.S:3:
> ./include/restorer.h:20:3: error: #error Only x86-64 is supported
> 
> I have a Core i5 laptop, running Ubuntu 10.04. uname -m shows "i686". 
> 
> Does this mean that CR tools will run only on x86_64, but will never work on 32-bit systems? (Isnt Intel x86_64 is backward compatible with 32-bit?)
> 
> Thanks for your help in advance. 
> Rajeev
> 
> 
> -----Original Message-----
> From: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org [mailto:containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org] On Behalf Of Muralidhar, Rajeev D
> Sent: Tuesday, August 28, 2012 2:12 PM
> To: Serge Hallyn
> Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> Subject: RE: Linux C/R: VNC server/Xterm checkpoint/recovery
> 
> I forgot to mention that I am doing on this on a Ubuntu 10.04, and uname -a shows "i686"
> 
> Thanks
> Rajeev
> 
> 
> -----Original Message-----
> From: Muralidhar, Rajeev D
> Sent: Tuesday, August 28, 2012 1:56 PM
> To: Serge Hallyn
> Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org; Muralidhar, Rajeev D
> Subject: RE: Linux C/R: VNC server/Xterm checkpoint/recovery
> 
> Hi all,
> 
> I got started with the information on http://criu.org/Main_Page 
> 
> I installed the linux-cr.git tree, compiled & have that ready. 
> 
> For CR-tools, I got all the required packages, but I am not able to compile crtools. This is the error I am seeing. Can someone pls let me know why I am getting this error?
> 
> rdmurali@ubuntu:~/Linux-CR/crtools$ make
>   PROTOBUF inventory.pb-c.c
>   CC       inventory.pb-c.o
>   PROTOBUF fdinfo.pb-c.c
>   CC       fdinfo.pb-c.o
>   PROTOBUF fown.pb-c.c
>   CC       fown.pb-c.o
>   PROTOBUF regfile.pb-c.c
>   CC       regfile.pb-c.o
>   PROTOBUF ghost-file.pb-c.c
>   CC       ghost-file.pb-c.o
>   PROTOBUF fifo.pb-c.c
>   CC       fifo.pb-c.o
>   PROTOBUF remap-file-path.pb-c.c
>   CC       remap-file-path.pb-c.o
>   PROTOBUF eventfd.pb-c.c
>   CC       eventfd.pb-c.o
>   PROTOBUF eventpoll.pb-c.c
>   CC       eventpoll.pb-c.o
>   PROTOBUF fh.pb-c.c
>   CC       fh.pb-c.o
>   PROTOBUF inotify.pb-c.c
>   CC       inotify.pb-c.o
>   PROTOBUF signalfd.pb-c.c
>   CC       signalfd.pb-c.o
>   PROTOBUF fs.pb-c.c
>   CC       fs.pb-c.o
>   PROTOBUF pstree.pb-c.c
>   CC       pstree.pb-c.o
>   PROTOBUF pipe.pb-c.c
>   CC       pipe.pb-c.o
>   PROTOBUF tcp-stream.pb-c.c
>   CC       tcp-stream.pb-c.o
>   PROTOBUF sk-packet.pb-c.c
>   CC       sk-packet.pb-c.o
>   PROTOBUF mnt.pb-c.c
>   CC       mnt.pb-c.o
>   PROTOBUF pipe-data.pb-c.c
>   CC       pipe-data.pb-c.o
>   PROTOBUF sa.pb-c.c
>   CC       sa.pb-c.o
>   PROTOBUF itimer.pb-c.c
>   CC       itimer.pb-c.o
>   PROTOBUF mm.pb-c.c
>   CC       mm.pb-c.o
>   PROTOBUF sk-opts.pb-c.c
>   CC       sk-opts.pb-c.o
>   PROTOBUF sk-unix.pb-c.c
>   CC       sk-unix.pb-c.o
>   PROTOBUF sk-inet.pb-c.c
>   CC       sk-inet.pb-c.o
>   PROTOBUF packet-sock.pb-c.c
>   CC       packet-sock.pb-c.o
> packet-sock.pb-c.c: In function 'packet_sock_entry__init':
> packet-sock.pb-c.c:98: warning: this decimal constant is unsigned only in ISO C90
> packet-sock.pb-c.c: At top level:
> packet-sock.pb-c.c:318: warning: this decimal constant is unsigned only in ISO C90
>   PROTOBUF ipc-var.pb-c.c
>   CC       ipc-var.pb-c.o
>   PROTOBUF ipc-desc.pb-c.c
>   CC       ipc-desc.pb-c.o
>   PROTOBUF ipc-shm.pb-c.c
>   CC       ipc-shm.pb-c.o
>   PROTOBUF ipc-msg.pb-c.c
>   CC       ipc-msg.pb-c.o
>   PROTOBUF ipc-sem.pb-c.c
>   CC       ipc-sem.pb-c.o
>   PROTOBUF utsns.pb-c.c
>   CC       utsns.pb-c.o
>   PROTOBUF creds.pb-c.c
>   CC       creds.pb-c.o
>   PROTOBUF vma.pb-c.c
>   CC       vma.pb-c.o
>   PROTOBUF core.pb-c.c
>   CC       core.pb-c.o
>   PROTOBUF netdev.pb-c.c
>   CC       netdev.pb-c.o
>   LINK     protobuf-lib.o
>   GEN      syscall-x86-64.S
>   CC       syscall-x86-64.o
> syscall-common-x86-64.S: Assembler messages:
> syscall-common-x86-64.S:13: Error: bad register name `%rcx'
> make[1]: *** [syscall-x86-64.o] Error 1
> make: *** [pie] Error 2
> 
> 
> thanks
> Rajeev
> 
> -----Original Message-----
> From: Serge Hallyn [mailto:serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org]
> Sent: Tuesday, August 21, 2012 3:04 AM
> To: Muralidhar, Rajeev D
> Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> Subject: Re: Linux C/R: VNC server/Xterm checkpoint/recovery
> 
> See http://criu.org/Main_Page
> 
> Quoting Muralidhar, Rajeev D (rajeev.d.muralidhar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org):
> > Hi,
> > 
> > Any help on this? 
> > 
> > Thanks
> > Rajeev
> > 
> > 
> > -----Original Message-----
> > From: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org 
> > [mailto:containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org] On Behalf Of 
> > Muralidhar, Rajeev D
> > Sent: Tuesday, August 14, 2012 4:00 PM
> > To: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> > Subject: Linux C/R: VNC server/Xterm checkpoint/recovery
> > 
> > HI all,
> > 
> > I am a newbie to Linux C/R. Can someone please tell me if I can checkpoint and restart VNC sessions with Linux C/R? what is the easiest way to test this out? Also, if the VNC session was running Xterms, will they be restored with Linux C/R? 
> > 
> > Thanks,
> > Rajeev
> > 
> > _______________________________________________
> > Containers mailing list
> > Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> > https://lists.linuxfoundation.org/mailman/listinfo/containers
> > _______________________________________________
> > Containers mailing list
> > Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> > https://lists.linuxfoundation.org/mailman/listinfo/containers
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linuxfoundation.org/mailman/listinfo/containers

Re: [CRIU] Re: Error compiling CRtools-0.1..

[Cyrill Gorcunov]

On Thu, Aug 30, 2012 at 07:55:58AM -0500, Serge Hallyn wrote:
> Please cc: criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org (I've cc:d them here) on crtools questions.
> 

Thanks, Serge!

We support x86-64 only for a while. Please make sure you're running branch
"crtools-3.6-rc1" of the kernel, we've moved our kernel to kernel.org,
so fetch it here

	git://git.kernel.org/pub/scm/linux/kernel/git/gorcunov/linux-cr.git

Also make sure you've all needed CONFIG_ options turned on,
see Kernel configuration in http://criu.org/CR_tools. Does it help?

RE: [CRIU] Re: Error compiling CRtools-0.1..

[Muralidhar, Rajeev D]

Hi Cyril

Yes, that is the branch I am running - 3.6-rc1. And I have all the config options turned on in the kernel as documented in the crui.org website. 

The errors I am seeing seem to be coming from netlink. What are the dependencies on netlink packages? Error seems to be suggesting that it cant stat any of the netlink sockets. 

Thanks
Rajeev


-----Original Message-----
From: Cyrill Gorcunov [mailto:gorcunov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org] On Behalf Of Cyrill Gorcunov
Sent: Thursday, August 30, 2012 6:41 PM
To: Serge Hallyn
Cc: Muralidhar, Rajeev D; criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org; containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [CRIU] Re: Error compiling CRtools-0.1..

On Thu, Aug 30, 2012 at 07:55:58AM -0500, Serge Hallyn wrote:
> Please cc: criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org (I've cc:d them here) on crtools questions.
> 

Thanks, Serge!

We support x86-64 only for a while. Please make sure you're running branch "crtools-3.6-rc1" of the kernel, we've moved our kernel to kernel.org, so fetch it here

	git://git.kernel.org/pub/scm/linux/kernel/git/gorcunov/linux-cr.git

Also make sure you've all needed CONFIG_ options turned on, see Kernel configuration in http://criu.org/CR_tools. Does it help?

Re: [CRIU] Re: Error compiling CRtools-0.1..

[Cyrill Gorcunov]

On Thu, Aug 30, 2012 at 01:16:27PM +0000, Muralidhar, Rajeev D wrote:
> Hi Cyril
> 
> Yes, that is the branch I am running - 3.6-rc1. And I have all the config options turned
> on in the kernel as documented in the crui.org website. 
> 
> The errors I am seeing seem to be coming from netlink. What are the dependencies on netlink packages?
> Error seems to be suggesting that it cant stat any of the netlink sockets.

Could you please clarify, you're running exactly version 0.1 or current git
snapshot from crtools repo? (Don't think it's problem with netlink, there
is something else failing).

	Cyrill

RE: [CRIU] Re: Error compiling CRtools-0.1..

[Muralidhar, Rajeev D]

Hi Cyril

I took the current git snapshot from crtools repo. Should I try version 0.1 from the tar file?

Thanks
Rajeev


-----Original Message-----
From: Cyrill Gorcunov [mailto:gorcunov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org] On Behalf Of Cyrill Gorcunov
Sent: Thursday, August 30, 2012 7:01 PM
To: Muralidhar, Rajeev D
Cc: Serge Hallyn; criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org; containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org; Andrey Vagin
Subject: Re: [CRIU] Re: Error compiling CRtools-0.1..

On Thu, Aug 30, 2012 at 01:16:27PM +0000, Muralidhar, Rajeev D wrote:
> Hi Cyril
> 
> Yes, that is the branch I am running - 3.6-rc1. And I have all the 
> config options turned on in the kernel as documented in the crui.org website.
> 
> The errors I am seeing seem to be coming from netlink. What are the dependencies on netlink packages?
> Error seems to be suggesting that it cant stat any of the netlink sockets.

Could you please clarify, you're running exactly version 0.1 or current git snapshot from crtools repo? (Don't think it's problem with netlink, there is something else failing).

	Cyrill

Re: [CRIU] Re: Error compiling CRtools-0.1..

[Cyrill Gorcunov]

On Thu, Aug 30, 2012 at 01:43:05PM +0000, Muralidhar, Rajeev D wrote:
> Hi Cyril
> 
> I took the current git snapshot from crtools repo. Should I try version 0.1 from the tar file?

No no, that's fine. I'm cooking a patch. Please wait a bit.

	Cyrill

Re: [CRIU] Re: Error compiling CRtools-0.1..

[Cyrill Gorcunov]

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

On Thu, Aug 30, 2012 at 05:45:13PM +0400, Cyrill Gorcunov wrote:
> On Thu, Aug 30, 2012 at 01:43:05PM +0000, Muralidhar, Rajeev D wrote:
> > Hi Cyril
> > 
> > I took the current git snapshot from crtools repo. Should I try version 0.1 from the tar file?
> 
> No no, that's fine. I'm cooking a patch. Please wait a bit.

Does the patch below helps for you?

Andrew, why did we mangle the paths to unix names?

	Cyrill

[-- Attachment #2: 0001-sk-unix.c-Don-t-mangle-name-provided-by-fiag-message.patch --]
[-- Type: text/plain, Size: 992 bytes --]

From 0b01d629e136b328fe4ce85f50d54dea9aaa0728 Mon Sep 17 00:00:00 2001
From: Cyrill Gorcunov <gorcunov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Date: Thu, 30 Aug 2012 17:43:34 +0400
Subject: [PATCH] sk-unix.c: Don't mangle name provided by fiag message

Otherwise we can't fetch stat.

Reported-by: "Muralidhar, Rajeev D" <rajeev.d.muralidhar-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Signed-off-by: Cyrill Gorcunov <gorcunov-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
---
 sk-unix.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/sk-unix.c b/sk-unix.c
index 9a9323c..605e32b 100644
--- a/sk-unix.c
+++ b/sk-unix.c
@@ -277,7 +277,7 @@ static int unix_collect_one(const struct unix_diag_msg *m,
 			}
 
 			uv = RTA_DATA(tb[UNIX_DIAG_VFS]);
-			snprintf(rpath, sizeof(rpath), ".%s", name);
+			snprintf(rpath, sizeof(rpath), "%s", name);
 			if (fstatat(mntns_root, rpath, &st, 0)) {
 				pr_perror("Can't stat socket %d(%s)",
 						m->udiag_ino, rpath);
-- 
1.7.7.6


[-- Attachment #3: Type: text/plain, Size: 205 bytes --]

_______________________________________________
Containers mailing list
Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
https://lists.linuxfoundation.org/mailman/listinfo/containers

RE: [CRIU] Re: Error compiling CRtools-0.1..

[Muralidhar, Rajeev D]

Hi Cyril

OK I will wait for your advice. 

If I try exactly 0.1 version, this is the error I get:

rdmurali@tapovan:~/Linux-CR/crtools-0.1$ sudo ./crtools check
Error (cr-check.c:174): Counter mismatch (or not met) 0 want 13
Error (cr-check.c:224): TFD mismatch (or not met) 0 want 4
Error (cr-check.c:263): WD mismatch (or not met) -1 want 1

Thanks
Rajeev


-----Original Message-----
From: Cyrill Gorcunov [mailto:gorcunov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org] On Behalf Of Cyrill Gorcunov
Sent: Thursday, August 30, 2012 7:15 PM
To: Muralidhar, Rajeev D
Cc: Serge Hallyn; criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org; containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org; Andrey Vagin
Subject: Re: [CRIU] Re: Error compiling CRtools-0.1..

On Thu, Aug 30, 2012 at 01:43:05PM +0000, Muralidhar, Rajeev D wrote:
> Hi Cyril
> 
> I took the current git snapshot from crtools repo. Should I try version 0.1 from the tar file?

No no, that's fine. I'm cooking a patch. Please wait a bit.

	Cyrill

Re: [CRIU] Re: Error compiling CRtools-0.1..

[Cyrill Gorcunov]

On Thu, Aug 30, 2012 at 01:59:16PM +0000, Muralidhar, Rajeev D wrote:
> Hi Cyril
> 
> OK I will wait for your advice. 
> 
> If I try exactly 0.1 version, this is the error I get:
> 
> rdmurali@tapovan:~/Linux-CR/crtools-0.1$ sudo ./crtools check
> Error (cr-check.c:174): Counter mismatch (or not met) 0 want 13
> Error (cr-check.c:224): TFD mismatch (or not met) 0 want 4
> Error (cr-check.c:263): WD mismatch (or not met) -1 want 1

This rather a symptom for wrong kernel version. It's important
to run "crtools-3.6-rc1" kernel, not vanilla v3.6-rc1.

	Cyrill

RE: [CRIU] Re: Error compiling CRtools-0.1..

[Muralidhar, Rajeev D]

Hi Cyril,

Here is output of uname -a

rdmurali@tapovan:~/Linux-CR/crtools-0.1$ uname -a
Linux tapovan 3.6.0-rc1 #2 SMP Thu Aug 30 08:38:17 IST 2012 x86_64 x86_64 x86_64 GNU/Linux

I got the kernel repo from: http://git.kernel.org/?p=linux/kernel/git/gorcunov/linux-cr.git;a=summary 

But I guess I didn't take crtools-3.6-rc1. OK let me get that branch and try. 

Will keep you posted. 

Thanks!
Rajeev



-----Original Message-----
From: Cyrill Gorcunov [mailto:gorcunov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org] On Behalf Of Cyrill Gorcunov
Sent: Thursday, August 30, 2012 7:35 PM
To: Muralidhar, Rajeev D
Cc: Serge Hallyn; criu-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org; containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org; Andrey Vagin
Subject: Re: [CRIU] Re: Error compiling CRtools-0.1..

On Thu, Aug 30, 2012 at 01:59:16PM +0000, Muralidhar, Rajeev D wrote:
> Hi Cyril
> 
> OK I will wait for your advice. 
> 
> If I try exactly 0.1 version, this is the error I get:
> 
> rdmurali@tapovan:~/Linux-CR/crtools-0.1$ sudo ./crtools check Error 
> (cr-check.c:174): Counter mismatch (or not met) 0 want 13 Error 
> (cr-check.c:224): TFD mismatch (or not met) 0 want 4 Error 
> (cr-check.c:263): WD mismatch (or not met) -1 want 1

This rather a symptom for wrong kernel version. It's important to run "crtools-3.6-rc1" kernel, not vanilla v3.6-rc1.

	Cyrill

Re: [CRIU] Re: Error compiling CRtools-0.1..

[Cyrill Gorcunov]

On Thu, Aug 30, 2012 at 02:27:17PM +0000, Muralidhar, Rajeev D wrote:
> Hi Cyril,
> 
> Here is output of uname -a
> 
> rdmurali@tapovan:~/Linux-CR/crtools-0.1$ uname -a
> Linux tapovan 3.6.0-rc1 #2 SMP Thu Aug 30 08:38:17 IST 2012 x86_64 x86_64 x86_64 GNU/Linux
> 
> I got the kernel repo from: http://git.kernel.org/?p=linux/kernel/git/gorcunov/linux-cr.git;a=summary 
> 
> But I guess I didn't take crtools-3.6-rc1. OK let me get that branch and try. 
> 
> Will keep you posted. 

OK. As to your initial message -- we don't yet support terminals c/r, there are
experimental patches flying around but they are not yet merged into main
crtools repo. Hope this will be implemented pretty soon.

	Cyrill