[Users] vzmigrate --online used to work, now fails with "CPU mismatch"

[Konstantin Khorenko]

On 03/22/2019 07:51 PM, jjs - mainphrame wrote:
However, one is an Intel CPU, the other is AMD. Live migration of containers between them had been working, for about 3 years, but now it balks at "CPUs mismatch".
You know, you are very lucky. We do face issues from time to time when processes die after online migration and
the root cause appears in cpus difference.

I wonder, is there some way to override the paranoia? Ideally, an admin could say "yes, I understand the CPUs aren't identical, but do it anyway"
Here you are:

# man vzmigrate

       -f,         --nodeps[=[all][,cpu_check][,disk_space][,technologies][,license][,rate][,bindmount][,tem‐
       plate_area_sync][,kernel_modules]]
              Ignore  an  absence of required package sets on destination node.  To prevent CT against errors
              in filesystem due to absent template files, it will not be started on  destination  node  after
              migration and must be started manually.
              Additional parameters:
              all - as is -f.
              cpu_check - to pass check of the cpu capabilities.

--
Best regards,

Konstantin Khorenko,
Virtuozzo Linux Kernel Team


Jake

On Fri, Mar 22, 2019 at 9:08 AM jjs - mainphrame <jjs at mainphrame.com<mailto:jjs at mainphrame.com>> wrote:
The output on both hosts is "x86_64"

Jake

On Fri, Mar 22, 2019 at 1:32 AM Narcis Garcia <informatica at actiu.net<mailto:informatica at actiu.net>> wrote:
What is the output of this command in both origin and destination hosts?
$ uname -m


El 21/3/19 a les 23:27, jjs - mainphrame ha escrit:
> Greetings -
>
> vzmigrate --online always worked reliably on my 2 openvz 7 servers, but
> nowadays, vzmigrate fails, for all containers, every time.
>
> ((CPUs mismatch))) -
>
> Apologies if I missed a memo, but why has that only now become an issue?
>
> [root at annie ~]# vzmigrate hachi 1989 --online
> Connection to destination node (hachi) is successfully established
> Moving/copying CT 1989 -> CT 1989, [], [] ...
> locking 1989
> 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/1989
> Live migration stage started
> Compression is enabled
> Phaul service failed to live migrate CT
> Phaul failed to live migrate CT (/var/log/phaul.log)
> Can't move/copy CT 1989 -> CT 1989, [], [] : Phaul failed to live
> migrate CT (/var/log/phaul.log)
> unlocking 1989
> [root at annie ~]# tail /var/log/phaul.log
>     load_entry_point('phaul==0.1', 'console_scripts', 'p.haul')()
>   File "/usr/lib/python2.7/site-packages/phaul/shell/phaul_client.py",
> line 49, in main
>     worker.start_migration()
>   File "/usr/lib/python2.7/site-packages/phaul/iters.py", line 161, in
> start_migration
>     self.__start_live_migration()
>   File "/usr/lib/python2.7/site-packages/phaul/iters.py", line 175, in
> __start_live_migration
>     self.__validate_cpu()
>   File "/usr/lib/python2.7/site-packages/phaul/iters.py", line 114, in
> __validate_cpu
>     raise Exception("CPUs mismatch")
> Exception: CPUs mismatch
> [root at annie ~]#
>
> Regards,
>
> Jake
>
>
> _______________________________________________
> Users mailing list
> Users at openvz.org<mailto:Users at openvz.org>
> https://lists.openvz.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users at openvz.org<mailto:Users at openvz.org>
https://lists.openvz.org/mailman/listinfo/users



_______________________________________________
Users mailing list
Users at openvz.org<mailto:Users at openvz.org>
https://lists.openvz.org/mailman/listinfo/users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20190322/df9ca68c/attachment-0001.html>