Search

Language:  
Search for:

Available article translations:

Online VE migration is failing with warning message "Insufficient cpu capabilities on destination HN".

APPLIES TO:
  • Parallels Cloud Server
  • Parallels Virtuozzo Containers for Linux
  • Parallels Server
  • Parallels Virtual Automation

Symptoms

Online migration of a virtual environment is failing with the following message:

  • For a container:

    Can not migrate: Insufficient cpu capabilities on destination HN.
    Can't move/copy VE#123 -> VE#123, [], [] : Insufficient cpu capabilities on destination HN.
    
  • For a virtual machine:

    Failed to migrate the VM: You cannot migrate this virtual machine using the live mode. The CPUs on the source and destination servers are not compatible.
    /usr/bin/prlctl failed, exitcode=255
    

Cause

This warning is displayed if the destination hardware node does not have some CPU features available on the source node. If a process inside a VE detected SSE2 extension (or some other CPU/system feature) on startup, this process will assume that SSE2 will be available any time later for its use. If a process requests SSE2 functionality after online migration to a node with CPU not providing such instructions, then a process can fail.

However, if the same process will be started on the node without SSE2, then it will not expect/use it and this process will work correctly after a VE is migrated to a hardware node without SSE2 extensions.

The message warns you about possible problems with VE functionality, if you migrate such VE to a hardware node which does not support any of CPU capabilities available on source node.

Please note that SSE2 is mentioned just as an example, it does not mean that exactly SSE2 is absent on destination hardware node, it could be any other CPU extension or system capability.

Resolution

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

You may also use offline migration.

Search words:

online migration of vm not possible

migration fail

Destination cpu does not have xsave

migration




eb0ea3b827d18de2329b6477e24c1d59 909d99074e442b52ce54cc7b31cf065d 2897d76d56d2010f4e3a28f864d69223 ca05eaf5b843fbd53589c90d7228a6df bf1c3a170005eae151f49ba2720abde9 de15ebe36a547439f84e5981418f36c7

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No
 
 
 
 
 
 
Desktop Virtualization
- Parallels Desktop 9 for Mac
- Parallels Transporter
- Parallels Desktop Switch to Mac Edition
- Parallels Desktop for Mac Enterprise Edition
- Parallels Management-Mac for Microsoft SCCM
Server Virtualization
- Parallels Cloud Server
- Parallels Containers for Windows 6.0 Beta
- Parallels Virtuozzo Containers
Automation
- Parallels Automation
- Parallels Automation for Cloud Infrastructure
- Parallels Business Automation Standard
- Parallels Virtual Automation
- Parallels Plesk Panel Suite
- Web Presence Builder
- Parallels Plesk Automation
- Parallels Small Business Panel
- Value-added Services for Hosters
- Parallels Partner Storefront
Services & Resources
- Cloud Acceleration Services
- Professional Services
- Support Services
- Training & Certification