Article ID: 118365, created on Nov 1, 2013, last review on Jun 17, 2016

  • Applies to:
  • Operations Automation 6.0
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor


  1. Online migration runs for 24 hours, and fails. The command output might look as follows:

    [root@vz4 ~]# pmigrate c 7215332 c --online
    root@'s password:
    Connection to destination node ( is successfully established
    Moving/copying CT#7215332 -> CT#7215332, [], [] ...
    Checking external bind mounts
    Check cluster ID
    Source and target CT private resides on the same shared partition
    Checking license restrictions
    Check of requires kernel modules
    Checking CPT image version for online migration
    Checking capabilities for online migration
    Checking technologies
    Checking templates for CT
    Checking IP addresses on destination node
    Check target CT name: test-ct
    /usr/libexec/vzvmiter exited with code 5
    can not prepare vm for CT#7215332 : /usr/libexec/vzvmiter exited with code 5
    Iterative migration is not available
    write() : Broken pipe
    vzsock_send() return 5
    Suspending CT#7215332 ...
    Dumping CT#7215332 ...
    Syncing dump file...
    OfflineManagement CT#7215332 ...
    Killing CT#7215332 ...
    Umounting CT#7215332 ...

    In the output above the following lines are especially significant:

    /usr/libexec/vzvmiter exited with code 5
    can not prepare vm for CT#7215332 : /usr/libexec/vzvmiter exited with code 5
    Iterative migration is not available
  2. The hardware node does not have a swap partition or the size is too small to store the memory related to container's processes:

    ~# free -mt
                 total       used       free     shared    buffers     cached
    Mem:         48157      43042       5115          0       4119      18839
    -/+ buffers/cache:      20083      28074
    Swap:            0          0          0
    Total:       48157      43042       5115


During online migration container's RAM state is saved to node's swap memory in order to simplify moving CT's state to another node. If source or destination hosts have insufficient swap then the online migration might fail and hang till timeout (24 hours) is reached.

This design was considered for improvement in scope of the request PSBM-20622.


This design has been improved in scope of the request PSBM-20622, it is fixed in PCS 6.0 - Update 4. Please install all updates to ensure old design is not affecting your migration.

Alternatively to make migration possible you may add more swap to source and destination hosts. It shouldn't be less than memory limit of a container you are migrating.

You may follow Red Hat guide if you want to know how can you add more swap (both swap partition and swap file are fine.

Search Words

24 hours


Failure in DBService

vzvmiter exited with code 5

vzctl : Can not get the context: File exists


migration hang


prlctl migrate

/usr/libexec/vzvmiter exited with code 5

Iterative migration is not available

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 a26b38f94253cdfbf1028d72cf3a498b e8e50b42231236b82df27684e7ec0beb c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 614fd0b754f34d5efe9627f2057b8642 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF