<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">On Fri, 22 Mar 2019 at 13:16, Konstantin Khorenko <<a href="mailto:khorenko@virtuozzo.com">khorenko@virtuozzo.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
On 03/22/2019 07:51 PM, jjs - mainphrame wrote:<br>
<blockquote type="cite">
<div dir="ltr">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".<br>
</div>
</blockquote>
You know, you are very lucky. We do face issues from time to time when processes die after online migration and<br>
the root cause appears in cpus difference.<br>
<br>
<blockquote type="cite">
<div dir="ltr">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"<br>
</div>
</blockquote>
Here you are:<br>
<br>
# man vzmigrate<br>
<br>
-f, --nodeps[=[all][,cpu_check][,disk_space][,technologies][,license][,rate][,bindmount][,tem‐<br>
plate_area_sync][,kernel_modules]]<br>
Ignore an absence of required package sets on destination node. To prevent CT against errors<br>
in filesystem due to absent template files, it will not be started on destination node after<br>
migration and must be started manually.<br>
Additional parameters:<br>
all - as is -f.<br>
cpu_check - to pass check of the cpu capabilities.<br></div></blockquote><div><br></div><div>That's a pity that all this is written in such incomprehensible way...</div><div>but it's Friday and so I took some time to fix this. Please see the attached patch.</div><div><div><br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF">
<br>
--<br>
Best regards,<br>
<br>
Konstantin Khorenko,<br>
Virtuozzo Linux Kernel Team<br>
<br>
<blockquote type="cite">
<div dir="ltr"><br>
Jake</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Mar 22, 2019 at 9:08 AM jjs - mainphrame <<a href="mailto:jjs@mainphrame.com" target="_blank">jjs@mainphrame.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div dir="ltr">The output on both hosts is "x86_64"</div>
<div dir="ltr"><br>
</div>
<div>Jake</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Mar 22, 2019 at 1:32 AM Narcis Garcia <<a href="mailto:informatica@actiu.net" target="_blank">informatica@actiu.net</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
What is the output of this command in both origin and destination hosts?<br>
$ uname -m<br>
<br>
<br>
El 21/3/19 a les 23:27, jjs - mainphrame ha escrit:<br>
> Greetings - <br>
> <br>
> vzmigrate --online always worked reliably on my 2 openvz 7 servers, but<br>
> nowadays, vzmigrate fails, for all containers, every time. <br>
> <br>
> ((CPUs mismatch))) -<br>
> <br>
> Apologies if I missed a memo, but why has that only now become an issue?<br>
> <br>
> [root@annie ~]# vzmigrate hachi 1989 --online<br>
> Connection to destination node (hachi) is successfully established<br>
> Moving/copying CT 1989 -> CT 1989, [], [] ...<br>
> locking 1989<br>
> Checking bindmounts<br>
> Check cluster ID<br>
> Checking keep dir for private area copy<br>
> Check of requires kernel modules<br>
> Checking technologies<br>
> Checking IP addresses on destination node<br>
> Checking RATE parameters in config<br>
> Checking ploop format 2<br>
> copy CT private /vz/private/1989<br>
> Live migration stage started<br>
> Compression is enabled<br>
> Phaul service failed to live migrate CT<br>
> Phaul failed to live migrate CT (/var/log/phaul.log)<br>
> Can't move/copy CT 1989 -> CT 1989, [], [] : Phaul failed to live<br>
> migrate CT (/var/log/phaul.log)<br>
> unlocking 1989<br>
> [root@annie ~]# tail /var/log/phaul.log<br>
> load_entry_point('phaul==0.1', 'console_scripts', 'p.haul')()<br>
> File "/usr/lib/python2.7/site-packages/phaul/shell/phaul_client.py",<br>
> line 49, in main<br>
> worker.start_migration()<br>
> File "/usr/lib/python2.7/site-packages/phaul/iters.py", line 161, in<br>
> start_migration<br>
> self.__start_live_migration()<br>
> File "/usr/lib/python2.7/site-packages/phaul/iters.py", line 175, in<br>
> __start_live_migration<br>
> self.__validate_cpu()<br>
> File "/usr/lib/python2.7/site-packages/phaul/iters.py", line 114, in<br>
> __validate_cpu<br>
> raise Exception("CPUs mismatch")<br>
> Exception: CPUs mismatch<br>
> [root@annie ~]# <br>
> <br>
> Regards,<br>
> <br></blockquote></div></blockquote></div></blockquote></div>
</blockquote></div></div></div></div>