[Users] Vzmigrate fails (unsupported filesystem nfsd)

[Corrado Fiore]

Hi Roman,

thanks for the advice.  The CPU are actually the very same model on both nodes:

[...]
processor       : 23
vendor_id       : GenuineIntel
cpu family      : 6
model           : 62
model name      : Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
[...]
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 pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms

[...]
processor       : 23
vendor_id       : GenuineIntel
cpu family      : 6
model           : 62
model name      : Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
[...]
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 pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms

The error, actually, refers to the NFS file system (which is present on both nodes), hence my question whether it was a false positive (= bug in vzmigrate) or not.

Thanks,
Corrado

________________________________
On 12/09/2014, at 7:00 PM, Roman Haefeli wrote:

> Hi
> 
> This might be not a bug, but a problem of having different CPU models on
> both host nodes. You cannot always live-migrate between different CPU
> models as not all have similar capabilities. 
> 
> It's still possible to offline-migrate, because when a CT starts on a
> mode with lesser capabilities, it would simply not use those.
> 
> Compare the output of 'cat /proc/cpuinfo' of both hostnodes.
> 
> Roman
> 
> 
> On Thu, 2014-09-11 at 21:43 +0800, Corrado Fiore wrote:
>> Dear All,
>> 
>> I have two OpenVZ nodes running the following:
>> 
>> ploop.x86_64         1.12.1-1
>> ploop-lib.x86_64     1.12.1-1
>> vzctl.x86_64         4.7.2-1
>> vzctl-core.x86_64    4.7.2-1
>> vzkernel.x86_64      2.6.32-042stab093.4
>> vzkernel-devel.x86_64
>> vzquota.x86_64       3.1-1
>> 
>> I'm trying to live migrate a container which runs nfsd.  Both nodes are configured in the same way, therefore nfsd module is loaded:
>> 
>> # lsmod | grep nfs
>> pio_nfs                17576  0 
>> ploop                 116256  32 pio_nfs,pio_direct,pfmt_raw,pfmt_ploop1
>> nfsd                  311145  13 
>> nfs                   442468  7 pio_nfs,vzrst,vzcpt
>> lockd                  77189  3 vzrst,nfsd,nfs
>> fscache                55684  1 nfs
>> auth_rpcgss            44949  2 nfsd,nfs
>> nfs_acl                 2663  2 nfsd,nfs
>> sunrpc                268245  37 pio_nfs,nfsd,nfs,lockd,auth_rpcgss,nfs_acl
>> 
>> Whenever I try to live migrate the container, I get the following error:
>> 
>> # vzmigrate -r yes --ssh="-p 16501" --keep-dst --online -v destination_host 161
>> Locked CT 
>> Starting live migration of CT 161 to destination_host
>> OpenVZ is running...
>>   Checking for CPT version compatibility
>>   Checking for CPU flags compatibility
>> Error: Unsupported filesystem nfsd
>> Insufficient CPU capabilities: can't migrate
>> Error: Error: CPU capabilities check failed!
>> Error: Destination node CPU is not compatible
>> Error: Can't continue live migration
>> 
>> At that point, the lock file remains and has to be manually deleted.
>> 
>> On the other hand, offline migration of that container works fine.
>> 
>> The funny thing is that if I try to live migrate the container back to the original host, I get the same error (Unsupported filesystem nfsd / Insufficient CPU capabilities: can't migrate).
>> 
>> Shall I open a bug report for this?
>> 
>> Regards,
>> Corrado Fiore
>> 
>> 
>> _______________________________________________
>> Users mailing list
>> Users at openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
> 
> 
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://lists.openvz.org/mailman/listinfo/users