[Users] Fwd: Re: Latest news in Virtuozzo 7 development 20160428

[Nikita Spiridonov]

On Fri, 2016-05-13 at 10:29 +0300, Cyrill Gorcunov wrote:
> > -------- Forwarded Message --------
> > Subject: Re: [Users] Latest news in Virtuozzo 7 development 20160428
> > Date: Thu, 12 May 2016 19:42:18 -0700
> > From: jjs - mainphrame <jjs at mainphrame.com>
> > Reply-To: OpenVZ users <users at openvz.org>
> > To: OpenVZ users <users at openvz.org>
> > 
> > Aw shucks, I've spoken too soon. After today's updates, live migration
> > is back to not working:
> > 
> > [root at hachi ~]# time vzmigrate annie 888 --online
> > Connection to destination node (annie) is successfully established
> > Moving/copying CT 888 -> CT 888, [], [] ...
> > locking 888
> > Checking bindmounts
> > Check cluster ID
> > Checking keep dir for private area copy
> > Check of requires kernel modules
> > Checking technologies
> > Checking templates for CT
> > Checking IP addresses on destination node
> > Checking RATE parameters in config
> > Checking ploop format 2
> > copy CT private /vz/private/888
> > Live migration stage started
> > Phaul service failed to live migrate CT
> > Can't move/copy CT 888 -> CT 888, [], [] : Phaul service failed to
> > live migrate CT
> > 
> > real 2m51.840s
> > user 0m0.385s
> > sys 0m3.457s
> > [root at hachi ~]#
> 
> Hi Jake! Could you please show the log files from phaul service?
> It should be in /var/log/. Does plain vcztl suspend/resume on
> this container works fine?
> 
> Also I think we might need to take a look on migration details
> from criu service work. Nikita, could you please point us where
> these logs are sitting?

On source side phaul write output to /var/log/phaul.log, on destination
- /var/log/phaul-service.log. These two files contain paths to image
directories (c/r criu images), and phaul preserve images if migration
failed. 

So, in your case, open /var/log/phaul-service.log, find proper migration
run, find images location (e.g. "Images are kept
in /vz/dump/rst-vaw50G-16.05.18-14.39") and examine proper criu log
(e.g. /vz/dump/rst-vaw50G-16.05.18-14.39/criu_restore.4.log).