Greetings, Following up on my own post -
After today's updates: ------------------------------ criu-2.1.0.40-1.vz7.x86_64 libvzctl-7.0.230-1.vz7.x86_64 phaul-0.1.14-4.vz7.noarch python-criu-2.1.0.40-1.vz7.x86_64 spfs-0.06.9-1.vz7.x86_64 vzkernel-3.10.0-327.18.2.vz7.14.15.x86_64 vzkernel-headers-3.10.0-327.18.2.vz7.14.15.x86_64 vzmigrate-7.0.40-1.vz7.x86_64 Live migration of all containers is reliably working again. So I guess it was a known issue, and I don't need to file a bug report. Jake On Fri, Jun 10, 2016 at 10:56 PM, jjs - mainphrame <j...@mainphrame.com> wrote: > Greetings, > > First of all, allow me to point out that the ubuntu container in which the > mysqld socket had been unable to dump/restore remains fully functional > after the fix. > > However a different ubuntu container, one which had been working > previously, now consistently fails to live migrate, though it does > successfully suspend/restore. > > Is this an area known to be still a work in progress at this point, or > should I submit another bug report? > > [root@hachi ~]# vzmigrate annie 1111 --online > Connection to destination node (annie) is successfully established > Moving/copying CT 1111 -> CT 1111, [], [] ... > locking 1111 > Checking bindmounts > Check cluster ID > Checking keep dir for private area copy > Check of requires kernel modules > Checking technologies > Checking IP addresses on destination node > Checking RATE parameters in config > Checking ploop format 2 > copy CT private /vz/private/1111 > Live migration stage started > Phaul service failed to live migrate CT > Phaul failed to live migrate CT (/var/log/phaul.log) > Can't move/copy CT 1111 -> CT 1111, [], [] : Phaul failed to live migrate > CT (/var/log/phaul.log) > [root@hachi ~]# > > Jake >
_______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
