Article ID: 1283, created on Oct 6, 2008, last review on May 11, 2014

  • Applies to:
  • Virtuozzo containers for Windows


In addition to using our native migration capability of a virtual environment from one hardware node to another, these machines can be moved manually.

NOTE: make sure that application templates from the source node are installed on the destination as well.

  1. Before attempting this manual movement, we recommend that your environment have unique VE IDs across all of your servers. By doing this, it will avoid any possible renaming of the VEs. By using the Virtuozzo Cluster feature, it can take care of the automatic assignment of VE IDs. However, if there are VEs that have the same IDs, please change the ID prior to this manual move.

  2. Stop the VE and disable the offline management through our command line interface (CLI). In the example below, the VE that will be migrated manually will be VE ID 101. The Virtuozzo program is also assumed to be installed under the default directory (C:\VZ directory)

    vzctl stop 101
    vzctl set 101 --save --offline_management no
  3. Move the content of C:\vz\private\101 folder from the source node to the same place on the secondary node.

    3.1. Check whether the migrated VE resides in an alternative location or if it has additional drives, which are on the non-default folder VZROOT\private\VEID. The easiest way to check is to run command vzquota stat VEID in Hardware Node CLI. In case the VE is in a different folder, or has disks placed on a different node's drives, it is necessary to correct the VE's conf file after step 4. In order to change VE's private area location VzPrivate=path_to_CT_private_dir , the variable should be corrected in the conf file. To define the correct location for additional drives of the VE, it is required to modify corresponding DRIVE_...= variable in the conf file.

    3.2. The additional drives (efd-files) might be “shared”. In this case, it is necessary to move such drives with the disk’s primary owner (the owner is the VE, which exclusively uses the disk at this time). It is also recommended to migrate all VEs, which use the shared disks to the same node.

    3.3. The migrated VE can have a vzcache template installed. VzcacheTemplates= variable in VE's conf file points to the fact that VE uses the vzcache template. This template can be found in C:\vz\Templates\__vzcache folder of the HW node and needs copying to the target node.

  4. Move the file C:\vz\conf\101.conf

  5. Just after you moved the files, run the following command to the DESTINATION node:

    vzcfgt set 101 IsMigrated 1
  6. If the VE you move is “bound” to a specific network adapter, you should either “unbind” it by executing

    vzcfgt delete 101 NetPreferredHostAdapterMac

    Or, bind it to corresponding interface on the target node by executing

    vzcfgt set 101 NetPreferredHostAdapterMac=”AA-BB-CC-DD-EE-FF” 

    where the string AA-BB-…-FF is just the MAC address of the required interface on the destination node.

  7. Once this is done, you may see that 101 is present on the destination node. You can verify this by running

    vzlist –a

    You may also start the VE by running

    vzctl start 101

Search Words





965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF