Installing the Logical Domains P2V Migration Tool

The Logical Domains P2V Migration Tool must only be installed and configured on the control domain. If the P2V tool is not installed in a directory that is shared between the source and target systems, you must copy the bin/ldmp2v script to the source system.

Prerequisites

Before you can run the Logical Domains P2V Migration Tool, ensure that the following are true:

• Target system runs at least Logical Domains 1.1 on the following:

  • Solaris 10 10/08 OS

  • Solaris 10 5/08 OS with the appropriate Logical Domains 1.1 patches

• Guest domains run at least the Solaris 10 5/08 OS

• Source system runs at least the Solaris 8 OS

In addition to these prerequisites, configure an NFS file system to be shared by both the source and target systems. This file system should be writable by root. However, if a shared file system is not available, use a local file system that is large enough to hold a file system dump of the source system on both the source and target systems.

Limitations

Version 1.0 of the Logical Domains P2V Migration Tool has the following limitations:

• Only UFS file systems are supported.

• Each guest domain can have only a single virtual switch and virtual disk service.

• The flash archiving method silently ignores excluded file systems.

Install the Logical Domains P2V Migration Tool

1. Go to the Logical Domains download page at http://www.sun.com/servers/coolthreads/ldoms/get.jsp.

2. Download the P2V software package, SUNWldmp2v.

   Starting with the Logical Domains 1.2 release, the SUNWldmp2v package is included in the Logical Domains zip file.

3. Become superuser or assume an equivalent role.

   Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.

4. Use the pkgadd command to install the SUNWldmp2v package.

   # pkgadd -d . SUNWldmp2v

5. Create the /etc/ldmp2v.conf file to configure the following properties:

   • VDS – Name of the virtual disk service, such as VDS="primary-vds0"

   • VSW – Name of the virtual switch, such as VSW="primary-vsw0"

   • VCC – Name of the virtual console concentrator, such as VCC="primary-vcc0"

   • BACKEND_TYPE – Backend type of zvol or file

   • BACKEND_SPARSE – Whether to create backend devices as sparse volumes or files BACKEND_SPARSE="yes", or non-sparse volumes or files BACKEND_SPARSE="no"

   • BACKEND_PREFIX – Location to create virtual disk backend devices

     When BACKEND_TYPE="zvol", specify the BACKEND_PREFIX value as a ZFS dataset name. When BACKEND_TYPE="files", the BACKEND_PREFIX value is interpreted as a path name of a directory that is relative to /.

     For example, BACKEND_PREFIX="tank/ldoms" would result in having ZVOLs created in the tank/ldoms/domain-name dataset, and files created in the /tank/ldoms/domain-name subdirectory.

   • BOOT_TIMEOUT – Timeout for Solaris OS boot in seconds

   For more information, see the ldmp2v.conf.sample configuration file that is part of the downloadable bundle.