Article ID: 123620, created on Nov 20, 2014, last review on Jun 17, 2016

  • Applies to:
  • Operations Automation
  • Virtuozzo


I would like to import existing Parallels Cloud Server infrastructure into Flexiant Cloud Orchestrator. How do I achieve it?


There is no automatic import procedure as of yet.

The manual procedure includes the following steps:

  1. Create a FCO subscription that includes a virtual server of the same specifications (CPU, RAM, Diskspace, etc). Please note, that FCO manages diskspace in 5GB units, therefore adjust properties of the source server to match this criteria.

    Created Virtual Environment

  2. A new virtual server (CT (container) or VM (virtual machine)) will be created on some server with sufficient resources, this might be some other server and not the one which holds the environment to import. Start this virtual environment as the owner of the server. The virtual server needs to be started in order to be registered in Parallels Cloud Server.

    Manage: Start

  3. While starting the server, find out UUID of the server in the box "Related Resources & UUIDs".

    UUID of Virtual Environment

  4. Login to FCO Control Panel as the system administrator, open 'System > Virtual Machines', paste UUID of the virtual server in the search field located in the block which shows running VMs, find an IP address of the physical server which runs this virtual environment. Change the list of fields and add 'Node IP' if it is absent.

    Look for Node IP

  5. Click on 'Manage' button and note 'ID' of this VM/CT. The name of the environment on the PCS server will be 'ID-ct' or 'ID-vm', e.g. '49-vm'.

    Find out Virtual Environment ID

  6. Login to the PCS server determined on the step 4 and replace the hard disk of the newly created server with the old one.

    Further instructions are slightly different for a container and a virtual machine. The steps assume that the diskspace is identical.

    • For a container, assuming that the original container is migrated to this node.

      1. Stop the newly created container:

        ~# prlctl stop ID-ct
      2. Replace the root.hds file in the directory root.hdd of the container:

        ~# cp $(vzlist -Ho private CTID)/root.hdd/root.hds $(vzlist -Ho private ID-ct)/root.hdd/root.hds

        (Replace "CTID" with the ID of the original container.)

      3. Start the container:

        ~# prlctl start ID-ct
    • For a virtual machine, assuming that the machine is migrated to (accessible from) this server,

      1. Stop the newly created virtual machine:

        ~# prlctl stop ID-vm
      2. Find the path to the VM's disk files, for both original and new VMs:

        ~# prlctl list -i VMNAME | grep '^  hdd'
        ~# prlctl list -i ID-vm | grep '^  hdd'
      3. Replace the file 'UUID.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds' with the original VM's .hds file:

        ~# cp PATH_TO_VMNAME.hdd/DISKNAME.hds.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds PATH_TO_ID-vm.hdd/UUID.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds
      4. Start the virtual machine:

        ~# prlctl start ID-vm
  7. Destroy the old virtual environment if everything is correct:

    • For a container:

      ~# prlctl destroy CTID
    • For a virtual machine:

      ~# prlctl destroy VNMANE

Note 1: The import procedure should be done on stopped CTs and VMs.

Note 2: CTs and VMs should not have existing snapshots. It can be checked with prlctl snapshot-list command. If snapshots exist, it is required to delete them first with prlctl snapshot-delete.

Search Words




5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 614fd0b754f34d5efe9627f2057b8642 0dd5b9380c7d4884d77587f3eb0fa8ef 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF