Logical Domains 1.3 Administration Guide

Appendix C Logical Domains Physical-to-Virtual Migration Tool

This appendix covers the following topics:

Logical Domains P2V Migration Tool Overview

The Logical Domains P2V Migration Tool automatically converts an existing physical system to a virtual system that runs in a logical domain on a chip multithreading (CMT) system. The source system can be any of the following:

The conversion from a physical system to a virtual system is performed in the following phases:

For information about the P2V migration tool, see the ldmp2v(1M) man page.

The following sections describe how the conversion from a physical system to a virtual system is performed in phases.

Collection Phase

This phase runs on the system to be converted. To create a consistent file system image, ensure that the system is as quiet as possible and that all applications are stopped. ldmp2v creates a backup of all mounted UFS file systems, so ensure that any file systems to be migrated to the logical domain are mounted. You can exclude mounted file systems by using the -x.

No changes are required on the source system. The only thing required is the ldmp2v script that was installed on the control domain. Depending on the selected archiving method you intend to use, ensure that the ufsdump or flarcreate utility is present on the source system.

Preparation Phase

The preparation phase uses the data collected during the collection phase to create a logical domain that is comparable to the source system.

You can use the ldmp2v prepare command in one of the following ways:

Conversion Phase

In the conversion phase, the logical domain uses the Solaris upgrade process to upgrade to the Solaris 10 OS. The upgrade operation removes all existing packages and installs the Solaris 10 sun4v packages, which automatically performs a sun4u-to-sun4v conversion. The convert phase can use a Solaris DVD iso image or a network install image. You can also use Custom JumpStart to perform a fully automated hands-off upgrade operation.

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.


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

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.


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

ProcedureInstall 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.

Using the ldmp2v Command

This section includes examples for the three phases.

Example C–1 Collection Phase Examples

The following examples show how you might use the ldmp2v collect command.

Example C–2 Preparation Phase Examples

The following examples show how you might use the ldmp2v prepare command.

Example C–3 Conversion Phase Examples

The following examples show how you might use the ldmp2v convert command.