OpenVZ Forum: Support » vzmigrate failed - Insufficient CPU capabilities

Home » General » Support » vzmigrate failed - Insufficient CPU capabilities

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

vzmigrate failed - Insufficient CPU capabilities [message #51160]

Thu, 27 February 2014 16:40

postcd
Messages: 73
Registered: April 2013

Member

Hi, just tried to use vzmigrate to move my VMs from one server ot another

Quote:

Starting live migration of CT 190 to xxx
OpenVZ is running...
Checking for CPT version compatibility
Checking for CPU flags compatibility
Error: IPv6 not loaded on destination node
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

OLD node:
Quote:

CPU model: Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz
1 CPU, 4 physical cores per CPU, total 8 logical CPU units

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 syscall nx rdtscp lm constant_tsc ida nonstop_tsc arat pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm

CPUINFO: http://ark.intel.com/products/65729/

NEW node:
Quote:

CPU model: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
1 CPU, 4 physical cores per CPU, total 8 logical CPU units

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 syscall nx rdtscp lm constant_tsc ida nonstop_tsc arat pni monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr sse4_1 sse4_2 popcnt lahf_lm

CPUINFO: http://ark.intel.com/products/65719/

These figures are based on /proc/cpuinfo

The comparison of the CPUs: http://cpuboss.com/cpus/Intel-Xeon-E3-1245V2-vs-Intel-Core-i 7-3770#specs

I dont believe that this I7 dont support virtualisation?

The quotation from:http://kb.parallels.com/en/3032
Quote:

You may forcibly migrate VE (use '-f' switch of 'vzmigrate' utility) and after VE is migrated, just check if it works correctly on destination node, if not - restart VE, it should correctly detect all available CPU extensions.

[Updated on: Thu, 27 February 2014 17:03]

Report message to a moderator