Article ID: 6324, created on May 13, 2009, last review on May 11, 2014

  • Applies to:
  • Virtuozzo hypervisor 4.0
  • Virtuozzo hypervisor 4.0 for Mac Bare Metal


You can take advantage of hardware and operating system virtualization features, including, for example:
  • the ability to run multiple operating systems on the same hardware simultaneously
  • the ability to increase the reliability of services and applications by separating and isolating them into different Containers
  • the ability to improve stability using failover options
  • features facilitating system administration and management
  • cost and human resources savings

You may want to virtualize some of your physical computers, or convert Virtual Machines (VMs) to Containers (CTs) and vice versa.
These actions can now be easily performed with the Parallels "pmigrate" utility -- a new, unified tool that allows you to manage all types of migrations/conversions. This tool enables the migration of Containers and Virtual Machines, as long Containers, Virtual Machines, and Hardware Nodes (HNs) are converted to each other.

pmigrate combines the advantages of traditional Parallels Virtuozzo Containers (PVC) utilities vzmigrate and vzp2v, while also adding new functionality. For greater convenience and usability, no special knowledge is required: pmigrate provides a user-friendly CLI resembling that of the widely used "scp" tool.

General syntax

The syntax of the pmigrate command is as follows:

pmigrate <source> <destination> [<arguments>]

where <source>|<destination> = <type> <address>
<type> is one of these options:
h - for Host
c - for Container
v - for Virtual Machine

<address>  = <host>[/<name>]
<host> = [<user>[:<password>]@]<destination_node_address>[:<destination_port>]
<name> should be used when addressing Virtual Machine or Container

When a user is not specified, the root one is used.
When the destination Container of the Virtual Machine name is not specified, that of the destination is used.
When the source or destination Container or Virtual Machine host is omitted, the localhost one is assumed.

System requirements

To ensure successful conversion, both source and destination computers should meet the system requirements given below:

Source computer:

The main requirement for the source machine concerns the operating system installed. Currently, the following Guest operating systems are supported:
Windows 2000 (x32)
Windows Server® 2003 (x32, x64)
Windows XP® (x32, x64)
Windows Vista® (x32, x64)
Windows Server 2008 (x32, x64)

Red Hat® Enterprise Linux 5 (x32, x64)
Red Hat Enterprise Linux 4 (x32, x64)
Red Hat Enterprise Linux 3 (x32, x64)
SUSE® Linux Enterprise Server 10 (x32, x64)
SUSE Linux Enterprise Server 9 (x32, x64)
Debian GNU/Linux 4.0 (x32, x64)
Debian GNU/Linux 3.1 (x32, x64)
Ubuntu Linux 7.10 (x32, x64)


Destination computer:

The destination computer should address all Parallels Server system requirements, and also have the following attributes:

- enough hard drive space to store and run the resulting Virtual Machine/Container, depending on its current size and growth prospectives;
- sufficient memory and processor resources;
- stable network connectivity with the source machine.

Usage examples

Converting Physical Computer to Parallels Server Virtual Machine

Assume the following test case: you are converting a remote host ( to a virtual machine (VM "Physical_Converted"), which will be placed locally.
The pmigrate syntax in this case should be:

pmigrate h root@ v localhost/"Physical_Converted"

or simply

pmigrate h v "Physical_Converted"

First, you need to install a special Parallels Transporter Agent on the source computer. The installation packages for both the Linux and Windows operating systems can be found in the


directory of the destination PSBM.

Copy the corresponding file to the source computer, run it, and follow the on-screen instructions to complete the installation.

NOTE: Administrative rights and a subsequent computer reboot are required for proper Transporter Agent setup.

After the installation and reboot, start the Transporter Agent on the source computer so that the PSBM on the destination node will be able to establish a connection. Now you are ready to run the pmigrate utility to initialize the conversion process.

The resulting "Physical_Converted" Virtual Machine will be placed in the /var/parallels directory.

Converting Physical Computer to Parallels Server Container

As a test case, we are converting a physical computer ( to a Container (CT#101), which will eventually reside on the current server.
The pmigrate syntax in this case should be:

pmigrate h root@ c localhost/101

or simply

pmigrate h c 101

For this type of conversion, no manual Transporter Agent installation is required -- it is installed automatically during the conversion process.

NOTE: Currently, there is no option to convert a Windows physical computer to a Container.
Converting a Container to a Virtual Machine:

In this third usage scenario, we will convert a Container (CT#101) to a Virtual Machine (Test VM) residing on the localhost:
The appropriate pmigrate syntax reads:

pmigrate c localhost/101 v localhost/'Test VM'

or simply

pmigrate c 101 v 'Test VM'

NOTE: The only supported destination type for converting a Container is the localhost. Additionally, it is possible to specify a Parallels Virtuozzo Containers (PVC) Hardware Node as a source for the Containers to be converted into Virtual Machines. For this purpose, the PVC Node should meet the following requirements:

* 4.5 version RC build for PVC for Windows and later versions.
* 4.0 version TU-4.0.0-464 update for PVC for Linux.
* Parallels Transporter Agent for Containers installed (the installation package for both Windows and Linux can be found in the same /usr/share/pmigrate/tools/ directory on any Parallels Server Bare Metal host).

Converting a Container does not require the installation of any additional tools (except in the case with PVC described above). Launch the above-given command, and it will proceed directly to the conversion routine.

a26b38f94253cdfbf1028d72cf3a498b d245cfd276e66749824316e20bfd8ade 0fe456bdc1f41aefe37dd2554a60437e 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF