[CRIU] About how to use p.haul

[Hui Kang]

Hi,
I have solved this issue, which actually was caused by incorrect permission
in the shared nfs mount.

The step of linking the proto files to criu is unnecessary. I have sent a
patch to that. Please review it if you have a minute. Thanks.

- Hui

On Fri, May 8, 2015 at 4:45 PM, Hui Kang <hkang.sunysb at gmail.com> wrote:

> Hi,
> There is another place in the test/HOWTO, which I do not quite understand.
>
> https://github.com/huikang/p.haul/blob/master/test/mtouch/HOWTO
>
> Step b says "* Make sure that p.haul/*.proto links point to respective  files
> in CRIU sources
>   # ls -l *.proto  ... rpc.proto -> ../criu/protobuf/rpc.proto  ...
> stats.proto -> ../criu/protobuf/stats.proto"
> However, this is not *.proto under p.haul directory. Shall I create the
> link?
>
> Without doing this, I met some issue when doing the living migration.
>
> On the src it report
> Connecting to target host
> Setting up local
> `- Passing (ctl:5, data:4) pair to CRIU
> Initilized shared FS hauler
> Setting up remote
> Checking CPU compatibility
>   `- Dumping CPU info
>   `- Sending CPU info
>   `- Checking CPU info
> Preliminary FS migration
> Starting iterations
> * Iteration 0
>         Making directory
> /var/local/p.haul-fs/dmp-ZYwoEe-15.05.08-20.36/img/1
>         Issuing pre-dump command to service
>         Pre-dump succeeded
> Dumped 18536 pages, 0 skipped
> Checking iteration progress:
>         > Proceed to next iteration
> * Iteration 1
>         Making directory
> /var/local/p.haul-fs/dmp-ZYwoEe-15.05.08-20.36/img/2
>         Issuing pre-dump command to service
>         Pre-dump succeeded
> Dumped 29 pages, 18517 skipped
> Checking iteration progress:
>         > Small dump
> Final dump and restore
>         Making directory
> /var/local/p.haul-fs/dmp-ZYwoEe-15.05.08-20.36/img/3
>         Issuing dump command to service
> Dump complete
> Final FS and images sync
> Sending images to target
>         Pack
>         Add htype images
> Asking target host to restore
> Remote exception
> Traceback (most recent call last):
>   File "/root/p.haul/p.haul", line 41, in <module>
>     worker.start_migration()
>   File "/root/p.haul/phaul/p_haul_iters.py", line 214, in start_migration
>     self.th.restore_from_images()
>   File "/root/p.haul/phaul/xem_rpc.py", line 37, in __call__
>     raise Exception(resp[1])
> Exception: Restore failed
>
> Are these error caused by those proto files? Thanks.
>
> - Hui
>
> On the destination it reports
> Connected
> Data socket (datask) accepted
> Setting up service side ('pid', '10625')
> `- Passing (ctl:8, data:7) pair to CRIU
> Started images server
> Waiting for images to unpack
> Checking cpuinfo
>    `- True
>         Making directory
> /var/local/p.haul-fs/rst-4xRfLz-15.05.08-20.37/img/1
> Starting page server for iter 1
>         Sending criu rpc req
>         Page server started at 12749
>         Making directory
> /var/local/p.haul-fs/rst-4xRfLz-15.05.08-20.37/img/2
> Starting page server for iter 2
>         Sending criu rpc req
>         Page server started at 12751
>         Making directory
> /var/local/p.haul-fs/rst-4xRfLz-15.05.08-20.37/img/3
> Starting page server for iter 3
>         Sending criu rpc req
>         Page server started at 12753
> Started images server
> Waiting for images to unpack
> Restoring from images
>                 Notify (setup-namespaces.12755)
> Traceback (most recent call last):
>   File "/root/p.haul/phaul/xem_rpc.py", line 98, in work
>     res = getattr(self._master, "rpc_" + data[1])(*data[2])
>   File "/root/p.haul/phaul/p_haul_service.py", line 144, in
> rpc_restore_from_images
>     raise Exception("Restore failed")
> Exception: Restore failed
> Disconnected
> Closing images
> Keeping images
> Images are kept in /var/local/p.haul-fs/rst-4xRfLz-15.05.08-20.37
>
>
>
>
>
> On Fri, May 8, 2015 at 10:54 AM, Pavel Emelyanov <xemul at parallels.com>
> wrote:
>
>> On 05/08/2015 01:47 AM, Hui Kang wrote:
>> > Hi,
>> > I am interested in trying p.haul to live migrate process across hosts.
>> However, I am confused about the p.haul's README
>> >
>> > 1. It says "Clone CRIU repository from git://github.com/xemul/criu <
>> http://github.com/xemul/criu>, checkout the 'p.haul' branch and compile
>> it with 'make'  ". However, there is no p.haul branch under criu.
>> >
>> > 2. One steps says  "compile p.haul with /cd p.haul && make/ ". However,
>> there is no Makefile under p.haul.
>> >
>> > Could anyone have an updated readme about using p.haul? Thanks.
>>
>> Yup, thanks for the feedback. Both docs updated, you can use master
>> criu branch.
>>
>> -- Pavel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20150508/9118551d/attachment.html>