subject:"\[Users\] odd issues with vzmigrate"

Re: [Users] odd issues with vzmigrate

2019-05-16 Thread Arjit Chaudhary

Hi,
I was able to resolve the prlctl migrate issue by removing the installed
rsync (was a newer version from epel) and manually installing the one
available from OpenVZs repository.

Re: Live Migrate,
On my side, I have the same issue with live migration, even if both the
servers are 1:1 in configuration.

Same Intel CPU, same RAM, same disks capacity and yet the issue persists.

On Fri, 17 May 2019, 02:03 jjs - mainphrame,  wrote:

> I've noticed that live migration stopped working for me on OVZ 7 as well.
> It used to work. heck, even in openvz 6 it worked.
>
> I posted here after noticing the issue, and was advised that live
> migration between intel and amd CPUs was problematic. So yesterday I bit
> the bullet, and swapped my OVZ amd host for a genuine intel box. Sadly,
> even with intel on both OVZ hosts, live migrate always fails. It still
> claims cpu mismatch, and so I pass -f cpu, but it still crashes and burns.
> Dead migration still works though.
>
> Although both nodes are now running Intel, the CPUs are not identical. Is
> this an issue?
>
> Here are the CPUs on each node:
>
> [root@hachi ~]# lscpu
> Architecture:  x86_64
> CPU op-mode(s):32-bit, 64-bit
> Byte Order:Little Endian
> CPU(s):2
> On-line CPU(s) list:   0,1
> Thread(s) per core:1
> Core(s) per socket:2
> Socket(s): 1
> NUMA node(s):  1
> Vendor ID: GenuineIntel
> CPU family:6
> Model: 23
> Model name:Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
> Stepping:  10
> CPU MHz:   2992.785
> BogoMIPS:  5985.57
> Virtualization:VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache:  6144K
> NUMA node0 CPU(s): 0,1
> Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
> pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf
> eagerfpu pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm
> sse4_1 xsave lahf_lm tpr_shadow vnmi flexpriority dtherm
> [root@hachi ~]#
>
> [root@annie nagios]# cd
> [root@annie ~]# cls
>
> [root@annie ~]# lscpu
> Architecture:  x86_64
> CPU op-mode(s):32-bit, 64-bit
> Byte Order:Little Endian
> CPU(s):8
> On-line CPU(s) list:   0-7
> Thread(s) per core:2
> Core(s) per socket:4
> Socket(s): 1
> NUMA node(s):  1
> Vendor ID: GenuineIntel
> CPU family:6
> Model: 42
> Model name:Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
> Stepping:  7
> CPU MHz:   1599.768
> CPU max MHz:   3800.
> CPU min MHz:   1600.
> BogoMIPS:  6784.18
> Virtualization:VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache:  256K
> L3 cache:  8192K
> NUMA node0 CPU(s): 0-7
> Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
> pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
> xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
> ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic
> popcnt tsc_deadline_timer aes xsave avx lahf_lm epb ssbd ibrs ibpb stibp
> tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts
> spec_ctrl intel_stibp flush_l1d
> [root@annie ~]#
>
> Jake
>
>
>
>
>
>
> On Thu, May 16, 2019 at 1:21 PM Arjit Chaudhary  wrote:
>
>> Oddly enough the issue is present on another server now, I have created a
>> bug report for it now,
>> https://bugs.openvz.org/projects/OVZ/issues/OVZ-7091?filter=allopenissues
>>
>> [root@de23 ~]# prlctl migrate 16764 192.168.0.2  --ssh "-o Port=22"
>> --verbose 10
>> Logging in
>> server uuid={98c783aa-90eb-47c9-99ea-1838ae37124d}
>> sessionid={4cc677b9-ec79-4bb6-9871-2458cbade840}
>> The virtual machine found: 16764
>> Migrate the CT 16764 on 192.168.0.2 ()
>> security_level=0
>> PrlCleanup::register_hook: 4afcdd40
>> EVENT type=100030
>> Migration started.
>> EVENT type=100523
>> Checking preconditions
>> EVENT type=100031
>> Migration cancelled!
>>
>> Failed to migrate the CT: Failed to migrate the Container. An internal
>> error occurred when performing the operation. Try to migrate the Container
>> again. If the problem persists, contact the Virtuozzo support team for
>> assistance.
>> resultCount: 0
>> PrlCleanup::unregister_hook: 4afcdd40
>> Logging off
>>
>>
>> On Wed, May 15, 2019 at 10:23 PM Arjit Chaudhary 
>> wrote:
>>
>>> re: prlctl migrate -- It was my mistake with the command,
>>>
>>> I was applying,
>>> > prlctl migrate 192.168.0.10 5128
>>>
>>> Instead of,
>>> > prlctl migrate 5128 192.168.0.10
>>>
>>> So now, prlctl migrate works fine, vzmigrate has this issue still with

Re: [Users] odd issues with vzmigrate

2019-05-16 Thread jjs - mainphrame

I've noticed that live migration stopped working for me on OVZ 7 as well.
It used to work. heck, even in openvz 6 it worked.

I posted here after noticing the issue, and was advised that live migration
between intel and amd CPUs was problematic. So yesterday I bit the bullet,
and swapped my OVZ amd host for a genuine intel box. Sadly, even with intel
on both OVZ hosts, live migrate always fails. It still claims cpu mismatch,
and so I pass -f cpu, but it still crashes and burns. Dead migration still
works though.

Although both nodes are now running Intel, the CPUs are not identical. Is
this an issue?

Here are the CPUs on each node:

[root@hachi ~]# lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):2
On-line CPU(s) list:   0,1
Thread(s) per core:1
Core(s) per socket:2
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 23
Model name:Intel(R) Core(TM)2 Duo CPU E8400  @ 3.00GHz
Stepping:  10
CPU MHz:   2992.785
BogoMIPS:  5985.57
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  6144K
NUMA node0 CPU(s): 0,1
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf eagerfpu
pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave
lahf_lm tpr_shadow vnmi flexpriority dtherm
[root@hachi ~]#

[root@annie nagios]# cd
[root@annie ~]# cls

[root@annie ~]# lscpu
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list:   0-7
Thread(s) per core:2
Core(s) per socket:4
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 42
Model name:Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Stepping:  7
CPU MHz:   1599.768
CPU max MHz:   3800.
CPU min MHz:   1600.
BogoMIPS:  6784.18
Virtualization:VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache:  256K
L3 cache:  8192K
NUMA node0 CPU(s): 0-7
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx
est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt
tsc_deadline_timer aes xsave avx lahf_lm epb ssbd ibrs ibpb stibp
tpr_shadow vnmi flexpriority ept vpid xsaveopt dtherm ida arat pln pts
spec_ctrl intel_stibp flush_l1d
[root@annie ~]#

Jake

On Thu, May 16, 2019 at 1:21 PM Arjit Chaudhary  wrote:

> Oddly enough the issue is present on another server now, I have created a
> bug report for it now,
> https://bugs.openvz.org/projects/OVZ/issues/OVZ-7091?filter=allopenissues
>
> [root@de23 ~]# prlctl migrate 16764 192.168.0.2  --ssh "-o Port=22"
> --verbose 10
> Logging in
> server uuid={98c783aa-90eb-47c9-99ea-1838ae37124d}
> sessionid={4cc677b9-ec79-4bb6-9871-2458cbade840}
> The virtual machine found: 16764
> Migrate the CT 16764 on 192.168.0.2 ()
> security_level=0
> PrlCleanup::register_hook: 4afcdd40
> EVENT type=100030
> Migration started.
> EVENT type=100523
> Checking preconditions
> EVENT type=100031
> Migration cancelled!
>
> Failed to migrate the CT: Failed to migrate the Container. An internal
> error occurred when performing the operation. Try to migrate the Container
> again. If the problem persists, contact the Virtuozzo support team for
> assistance.
> resultCount: 0
> PrlCleanup::unregister_hook: 4afcdd40
> Logging off
>
>
> On Wed, May 15, 2019 at 10:23 PM Arjit Chaudhary 
> wrote:
>
>> re: prlctl migrate -- It was my mistake with the command,
>>
>> I was applying,
>> > prlctl migrate 192.168.0.10 5128
>>
>> Instead of,
>> > prlctl migrate 5128 192.168.0.10
>>
>> So now, prlctl migrate works fine, vzmigrate has this issue still with
>> the same output as before.
>>
>> On Mon, May 13, 2019 at 11:23 AM Vasily Averin  wrote:
>>
>>> Dear Arjit,
>>> it looks liek some bug for me,
>>> and I would like to advise you to submit bug into openvz bug tracker
>>> https://bugs.openvz.org/ on openVZ project
>>>
>>> thank you,
>>> Vasily Averin
>>>
>>> On 5/11/19 3:16 PM, Arjit Chaudhary wrote:
>>> > Hello,
>>> > I've been using vzmigrate without issues for a couple of years on VZ6,
>>> but on VZ7 I run into this odd issue,
>>> >
>>> > I am able to migrate from a newer kernel to a older kernel
>>> > BUT
>>> > I am unable to migrate from same kernel to same kernel?
>>> >
>>>

Re: [Users] odd issues with vzmigrate

2019-05-16 Thread Arjit Chaudhary

Oddly enough the issue is present on another server now, I have created a
bug report for it now,
https://bugs.openvz.org/projects/OVZ/issues/OVZ-7091?filter=allopenissues

[root@de23 ~]# prlctl migrate 16764 192.168.0.2  --ssh "-o Port=22"
--verbose 10
Logging in
server uuid={98c783aa-90eb-47c9-99ea-1838ae37124d}
sessionid={4cc677b9-ec79-4bb6-9871-2458cbade840}
The virtual machine found: 16764
Migrate the CT 16764 on 192.168.0.2 ()
security_level=0
PrlCleanup::register_hook: 4afcdd40
EVENT type=100030
Migration started.
EVENT type=100523
Checking preconditions
EVENT type=100031
Migration cancelled!

Failed to migrate the CT: Failed to migrate the Container. An internal
error occurred when performing the operation. Try to migrate the Container
again. If the problem persists, contact the Virtuozzo support team for
assistance.
resultCount: 0
PrlCleanup::unregister_hook: 4afcdd40
Logging off


On Wed, May 15, 2019 at 10:23 PM Arjit Chaudhary  wrote:

> re: prlctl migrate -- It was my mistake with the command,
>
> I was applying,
> > prlctl migrate 192.168.0.10 5128
>
> Instead of,
> > prlctl migrate 5128 192.168.0.10
>
> So now, prlctl migrate works fine, vzmigrate has this issue still with the
> same output as before.
>
> On Mon, May 13, 2019 at 11:23 AM Vasily Averin  wrote:
>
>> Dear Arjit,
>> it looks liek some bug for me,
>> and I would like to advise you to submit bug into openvz bug tracker
>> https://bugs.openvz.org/ on openVZ project
>>
>> thank you,
>> Vasily Averin
>>
>> On 5/11/19 3:16 PM, Arjit Chaudhary wrote:
>> > Hello,
>> > I've been using vzmigrate without issues for a couple of years on VZ6,
>> but on VZ7 I run into this odd issue,
>> >
>> > I am able to migrate from a newer kernel to a older kernel
>> > BUT
>> > I am unable to migrate from same kernel to same kernel?
>> >
>> > ie,
>> > 3.10.0-957.10.1.vz7.85.17 --to--> 3.10.0-957.10.1.vz7.85.17 == Fail
>> >
>> > but,
>> > 3.10.0-957.10.1.vz7.85.17 --to-->  3.10.0-862.20.2.vz7.73.29 == Success
>> >
>> > This is the error I get when I try to migrate to 192.168.0.10 which
>> runs 3.10.0-957.10.1.vz7.85.17,
>> >
>> >> [root@source  ~]# vzmigrate 192.168.0.10 5128
>> >> ssh exited with code 255
>> >> ssh wait daemon exited with code 1
>> >> vzsock_open() return 1
>> >>
>> >> Can not create connection to 192.168.0.10
>> >
>> > I am able to SSH into 192.168.0.10 via the command ssh
>> root@192.168.0.10   without any issue.
>> >
>> > I did try prlctl migrate but that too is returning an error,
>> >
>> >> [root@source ~]# prlctl migrate 192.168.0.10 5128
>> >> Failed to get VM config: The virtual machine could not be found. The
>> virtual machine is > not registered in the virtual machine directory on
>> this server. Contact your Virtuozzo administrator for assistance.
>> >
>> > prlctl version 7.0.173
>> > vzmigrate version 7.0.119-1.vz7
>> >
>> > Any help would be appreciated on this.
>> >
>> > --
>> > Thanks,
>> > Arjit Chaudhary
>> >
>> > ___
>> > Users mailing list
>> > Users@openvz.org
>> > https://lists.openvz.org/mailman/listinfo/users
>> >
>> ___
>> Users mailing list
>> Users@openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
>>
>
>
> --
> Thanks,
> Arjit Chaudhary
>


-- 
Thanks,
Arjit Chaudhary
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] odd issues with vzmigrate

2019-05-15 Thread Arjit Chaudhary

re: prlctl migrate -- It was my mistake with the command,

I was applying,
> prlctl migrate 192.168.0.10 5128

Instead of,
> prlctl migrate 5128 192.168.0.10

So now, prlctl migrate works fine, vzmigrate has this issue still with the
same output as before.

On Mon, May 13, 2019 at 11:23 AM Vasily Averin  wrote:

> Dear Arjit,
> it looks liek some bug for me,
> and I would like to advise you to submit bug into openvz bug tracker
> https://bugs.openvz.org/ on openVZ project
>
> thank you,
> Vasily Averin
>
> On 5/11/19 3:16 PM, Arjit Chaudhary wrote:
> > Hello,
> > I've been using vzmigrate without issues for a couple of years on VZ6,
> but on VZ7 I run into this odd issue,
> >
> > I am able to migrate from a newer kernel to a older kernel
> > BUT
> > I am unable to migrate from same kernel to same kernel?
> >
> > ie,
> > 3.10.0-957.10.1.vz7.85.17 --to--> 3.10.0-957.10.1.vz7.85.17 == Fail
> >
> > but,
> > 3.10.0-957.10.1.vz7.85.17 --to-->  3.10.0-862.20.2.vz7.73.29 == Success
> >
> > This is the error I get when I try to migrate to 192.168.0.10 which runs
> 3.10.0-957.10.1.vz7.85.17,
> >
> >> [root@source  ~]# vzmigrate 192.168.0.10 5128
> >> ssh exited with code 255
> >> ssh wait daemon exited with code 1
> >> vzsock_open() return 1
> >>
> >> Can not create connection to 192.168.0.10
> >
> > I am able to SSH into 192.168.0.10 via the command ssh root@192.168.0.10
>   without any issue.
> >
> > I did try prlctl migrate but that too is returning an error,
> >
> >> [root@source ~]# prlctl migrate 192.168.0.10 5128
> >> Failed to get VM config: The virtual machine could not be found. The
> virtual machine is > not registered in the virtual machine directory on
> this server. Contact your Virtuozzo administrator for assistance.
> >
> > prlctl version 7.0.173
> > vzmigrate version 7.0.119-1.vz7
> >
> > Any help would be appreciated on this.
> >
> > --
> > Thanks,
> > Arjit Chaudhary
> >
> > ___
> > Users mailing list
> > Users@openvz.org
> > https://lists.openvz.org/mailman/listinfo/users
> >
> ___
> Users mailing list
> Users@openvz.org
> https://lists.openvz.org/mailman/listinfo/users
>


-- 
Thanks,
Arjit Chaudhary
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] odd issues with vzmigrate

2019-05-12 Thread Vasily Averin

Dear Arjit,
it looks liek some bug for me,
and I would like to advise you to submit bug into openvz bug tracker
https://bugs.openvz.org/ on openVZ project

thank you,
Vasily Averin

On 5/11/19 3:16 PM, Arjit Chaudhary wrote:
> Hello,
> I've been using vzmigrate without issues for a couple of years on VZ6, but on 
> VZ7 I run into this odd issue,
> 
> I am able to migrate from a newer kernel to a older kernel
> BUT
> I am unable to migrate from same kernel to same kernel?
> 
> ie,
> 3.10.0-957.10.1.vz7.85.17 --to--> 3.10.0-957.10.1.vz7.85.17 == Fail
> 
> but,
> 3.10.0-957.10.1.vz7.85.17 --to-->  3.10.0-862.20.2.vz7.73.29 == Success
> 
> This is the error I get when I try to migrate to 192.168.0.10 which runs 
> 3.10.0-957.10.1.vz7.85.17,
> 
>> [root@source  ~]# vzmigrate 192.168.0.10 5128
>> ssh exited with code 255
>> ssh wait daemon exited with code 1
>> vzsock_open() return 1
>>   
>> Can not create connection to 192.168.0.10 
>  
> I am able to SSH into 192.168.0.10 via the command ssh root@192.168.0.10 
>   without any issue.
> 
> I did try prlctl migrate but that too is returning an error,
> 
>> [root@source ~]# prlctl migrate 192.168.0.10 5128
>> Failed to get VM config: The virtual machine could not be found. The virtual 
>> machine is > not registered in the virtual machine directory on this server. 
>> Contact your Virtuozzo administrator for assistance.
> 
> prlctl version 7.0.173
> vzmigrate version 7.0.119-1.vz7
> 
> Any help would be appreciated on this.
> 
> -- 
> Thanks,
> Arjit Chaudhary
> 
> ___
> Users mailing list
> Users@openvz.org
> https://lists.openvz.org/mailman/listinfo/users
> 
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

[Users] odd issues with vzmigrate

2019-05-11 Thread Arjit Chaudhary

Hello,
I've been using vzmigrate without issues for a couple of years on VZ6, but
on VZ7 I run into this odd issue,

I am able to migrate from a newer kernel to a older kernel
BUT
I am unable to migrate from same kernel to same kernel?

ie,
3.10.0-957.10.1.vz7.85.17 --to--> 3.10.0-957.10.1.vz7.85.17 == Fail

but,
3.10.0-957.10.1.vz7.85.17 --to-->  3.10.0-862.20.2.vz7.73.29 == Success

This is the error I get when I try to migrate to 192.168.0.10 which runs
3.10.0-957.10.1.vz7.85.17,

> [root@source  ~]# vzmigrate 192.168.0.10 5128
> ssh exited with code 255
> ssh wait daemon exited with code 1
> vzsock_open() return 1
>
> Can not create connection to 192.168.0.10

I am able to SSH into 192.168.0.10 via the command ssh root@192.168.0.10
without any issue.

I did try prlctl migrate but that too is returning an error,

> [root@source ~]# prlctl migrate 192.168.0.10 5128
> Failed to get VM config: The virtual machine could not be found. The
virtual machine is > not registered in the virtual machine directory on
this server. Contact your Virtuozzo administrator for assistance.

prlctl version 7.0.173
vzmigrate version 7.0.119-1.vz7

Any help would be appreciated on this.

-- 
Thanks,
Arjit Chaudhary
___
Users mailing list
Users@openvz.org
https://lists.openvz.org/mailman/listinfo/users

Re: [Users] odd issues with vzmigrate

Re: [Users] odd issues with vzmigrate

Re: [Users] odd issues with vzmigrate

Re: [Users] odd issues with vzmigrate

Re: [Users] odd issues with vzmigrate

[Users] odd issues with vzmigrate

6 matches

Site Navigation

Mail list logo

Footer information