Logical Domains 1.3 Reference Manual

ldmp2v(1M)

Name

ldmp2v– command-line interface for the Logical Domains Physical-to-Virtual (P2V) Migration Tool

Synopsis

ldmp2v collect [-a ufsdump|flash|none] [-v] [-x exclude-fs [-x ...]] -d data-dir
ldmp2v prepare [-b zvol | file] [-c cpu] [-o keep-hostid] [-o keep-mac]
  [-m mountpoint:size [-m ...]] [-M memsize] [-p prefix] [-s] [-v]
  [-x no-auto-adjust-fs] [-x remove-unused-slices] -d data-dir domain
ldmp2v prepare -R guest-root  [-c cpu] [-o keep-hostid] [-o keep-mac]
  [-m mountpoint:size [-m ...]] [-M memsize] [-v] [-x no-auto-adjust-fs]
  [-x remove-unused-slices] -d data-dir domain
ldmp2v prepare -C domain
ldmp2v convert -i install-image -d data-dir [-v] domain
ldmp2v convert [-j] -n interface -d data-dir [-v] domain

Description

Version 1.0 of the Logical Domains Physical-to-Virtual (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 sun4u SPARC system that runs at least the Solaris 8 Operating System, or a non-Logical Domains sun4v system that runs the Solaris 10 OS.

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

Collection phase. Runs on the physical source system. collect creates a file system image of the source system based on the configuration information that it collects about the source system.
Preparation phase. Runs on the control domain of the target system. prepare creates the logical domain on the target system based on the configuration information collected in the collect phase. The file system image is restored to one or more virtual disks. The image is modified to enable it to run as a logical domain.
Conversion phase. Runs on the control domain of the target system. In the convert phase, the created logical domain is converted into a logical domain that runs the Solaris 10 OS by using the standard Solaris upgrade process.

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

Collection Phase

ldmp2v collect [-a ufsdump|flash|none] [-v] [-x exclude-fs [-x ...]] -d data-dir

The ldmp2v collect command uses the following options:

-a archive-method: Specifies the archiving method to use. Valid values are ufsdump, flash, or none. The default is ufsdump.
-d data-dir: Specifies the per-system directory in which to store P2V files. For the collection phase, this directory must be writable by root. Any intermediate directories are created automatically.
-v: Uses verbose mode, which increases the verbosity of the messages that are issued by ldmp2v.
-x exclude-fs: Excludes the file system, exclude-fs, from the archive.

Preparation Phase

ldmp2v prepare [-b zvol | file] [-c cpu] [-o keep-hostid] [-o keep-mac]
  [-m mountpoint:size [-m ...]] [-M memsize] [-p prefix] [-s] [-v]
  [-x no-auto-adjust-fs] [-x remove-unused-slices] -d data-dir domain
ldmp2v prepare -R guest-root  [-c cpu] [-o keep-hostid] [-o keep-mac]
  [-m mountpoint:size [-m ...]] [-M memsize] [-v] [-x no-auto-adjust-fs]
  [-x remove-unused-slices] -d data-dir domain
ldmp2v prepare -C domain

The ldmp2v prepare command uses the following operand and options:

domain

Specifies the logical domain on which to operate.

-b backend-type

Overrides the setting for BACKEND_TYPE in /etc/ldmp2v.conf. The virtual disks can be backed by ZFS volumes, zvol, or plain files, file.

-c cpu

Allocates the number of VCPUs to the logical domain. By default, ldmp2v allocates a VCPU for each CPU on the physical system.

-C

Cleans up the specified domain.

-d data-dir

Specifies the per-system directory where the files required for P2V are located.

-m mountpoint:size

Resizes the underlying slice and disk for the file system at mountpoint. The size is specified as numunit, where unit is b for blocks, k for kilobytes, m for megabytes, or g for gigabytes. You can specify this option more than one time. Using this option disables the automatic resizing of /, /usr, and /var.

-M memsize

Specifies the amount of memory in megabytes to allocate to the logical domain. By default, ldmp2v assigns the same amount that the physical system has.

-o keep-hostid

Transfers the host ID of the physical system to the logical domain. By default, the Logical Domains Manager assigns a new unique host ID.

-o keep-mac

Transfers the MAC addresses of the physical system to the logical domain. By default the Logical Domains Manager assigns a new unique MAC address.

-p prefix

Specifies the location where backend devices will be created. Denotes the ZFS dataset for the zvol backend, or a directory relative to / for the file backend. This option overrides the BACKEND_PREFIX parameter in /etc/ldmp2v.conf.

-R guest-root

Selects non-automatic mode. The OS image modification steps are applied to the file system rooted at guest-root. Updates the /etc/vfstab of the logical domain to match the file system layout below guest-root.

-s

Creates sparse backend devices. This option overrides the BACKEND_SPARSE parameter in /etc/ldmp2v.conf.

-v

Uses verbose mode, which increases the verbosity of the messages that are issued by ldmp2v.

-x no-auto-adjust-fs

Prevents the automatic size adjustment of the /, /usr, and /var file systems to 10 Gbytes total. Use this option with care because the size of the existing file systems might not be sufficient to upgrade to a newer Solaris release.

You can manually resize file system sizes by using the -m option.

-x remove-unused-slices

Reduces the size of the virtual disk by not creating slices that do not hold a file system or a swap partition.

Conversion Phase

ldmp2v convert -i install-image -d data-dir [-v] domain
ldmp2v convert [-j] -n interface -d data-dir [-v] domain

The ldmp2v convert command uses the following options:

-d data-dir: Specifies the per-system directory where the files required for P2V are located.
-i install-image: Specifies the path to the Solaris 10 OS DVD ISO image to use for upgrade.
-j: Uses Custom JumpStart, which requires that a JumpStart server and JumpStart client are properly configured.
-n interface: Specifies the virtual network interface from which to boot when using a network install server.
-v: Uses verbose mode, which increases the verbosity of the messages issued by ldmp2v.

Before you begin the conversion phase, shut down the original physical system, as the logical domain uses the same IP addresses, and possibly also MAC addresses, as the physical system.

If any IP address of the physical system is active, the ldmp2v convert command exits with an error message.

Examples

This section includes examples for the three phases.

Example 1 Collection Phase Examples

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

Sharing an NFS-mounted file system. The following example shows the simplest way to perform the collect phase, where the source and target systems share an NFS-mounted file system.
# ldmp2v collect -d /home/dana/p2v/volumia
Not sharing an NFS-mounted file system. When the source and target systems do not share an NFS-mounted file system, the file system image can be written to local storage and then later copied to the control domain. Since it is not possible to use ufsdump to exclude files, use the flash archiving method that is provided by ldmp2v. The flash tool automatically excludes the archive it creates.
# ldmp2v collect -d /home/dana/p2v/volumia -a flash
Skip file-system backup step. If backups of the system are already available using a third-party backup tool such as NetBackup, you can skip the file system backup step by using the none archiving method. When you use this option, only the system configuration manifest is created.
# ldmp2v collect -d /home/dana/p2v/volumia -a none
Note –
If the directory specified by -d is not shared by the source and target systems, copy the contents of that directory to the control domain. The directory contents must be copied to the control domain prior to beginning the preparation phase.

Example 2 Preparation Phase Examples

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

The following example creates a logical domain called volumia by using the defaults configured in /etc/ldmp2v.conf while keeping the MAC addresses of the physical system:
# ldmp2v prepare -d /home/dana/p2v/volumia -o keep-mac volumia
The following shows how to completely remove a domain and its backend devices by using the -C option:
# ldmp2v prepare -C volumia
The following shows how to resize one or more file systems during P2V by specifying the mount point and the new size with the -m option:
# ldmp2v prepare -d /home/dana/p2v/normaal -m /:8g normaal

Example 3 Conversion Phase Examples

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

Using a network install server. The ldmp2v convert command boots the Logical Domain over the network by using the specified virtual network interface. You must run the setup_install_server and add_install_client scripts on the install server.

Optionally, you can use the Custom JumpStart feature to perform a completely hands-off conversion.

The following shows how to use a network install server to upgrade your system:
# ldmp2v convert -n vnet0 -d /p2v/volumia volumia
The following shows how to use Custom JumpStart to upgrade your system:
# ldmp2v convert -j -n vnet0 -d /p2v/volumia volumia
Using an ISO image. The ldmp2v convert command attaches the Solaris DVD ISO image to the logical domain and boots from it. To upgrade, answer all sysid prompts and select Upgrade.

Note –
The answers to the sysid questions are only used during the upgrade process, so you can select the simplest options (non-networked, no naming service, and so on). The system's original identity is preserved by the upgrade and takes effect on the reboot after the upgrade is complete. The time required to perform the upgrade depends on the Solaris cluster that is installed on the original system.
# ldmp2v convert -i /tank/iso/s10s_u5.iso -d /home/dana/p2v/volumia volumia

Exit Status

The following exit values are returned:

0: Successful completion.
>0: An error occurred.

Attributes

See the attributes(5) man page for a description of the following attributes:

Attribute Types	Attribute Values
Availability	`SUNWldmp2v`
Interface Stability	Uncommitted