|Skip Navigation Links|
|Exit Print View|
|Oracle VM Server for SPARC 3.0 Administration Guide Oracle VM Server for SPARC|
The Oracle VM Server for SPARC P2V Tool package must be installed and configured only on the control domain of the target system. You do not need to install the package on the source system. Instead, you can simply copy the /usr/sbin/ldmp2v script from the target system to the source system.
Note - The ldmp2v is installed on an Oracle Solaris 10 system from the SUNWldmp2v package, while the ldmp2v is installed by default on an Oracle Solaris 11 system from the ldomsmanager package.
Before you can run the Oracle VM Server for SPARC P2V tool, ensure that the following conditions are met:
The following Flash Archive patches are installed on the source system:
For the Solaris 8 OS: At least patch ID 109318-34
For the Solaris 9 OS: At least patch ID 113434-06
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.
The Oracle VM Server for SPARC P2V tool has the following limitations:
Only UFS file systems are supported.
Only plain disks (/dev/dsk/c0t0d0s0), Oracle Solaris Volume Manager metadevices (/dev/md/dsk/dNNN), and VxVM encapsulated boot disks are supported on the source system.
During the P2V process, each guest domain can have only a single virtual switch and virtual disk server. You can add more virtual switches and virtual disk servers to the domain after the P2V conversion.
Support for VxVM volumes is limited to the following volumes on an encapsulated boot disk: rootvol, swapvol, usr, var, opt, and home. The original slices for these volumes must still be present on the boot disk. The P2V tool supports Veritas Volume Manager 5.x on the Oracle Solaris 10 OS. However, you can also use the P2V tool to convert Solaris 8 and Solaris 9 operating systems that use VxVM.
Oracle Solaris 10 systems that have zones can be converted if the zones are detached by using the zoneadm detach command prior to running the ldmp2v collect operation. After the P2V conversion completes, use the zoneadm attach command to reattach the zones that have been created on the guest domain. For information about performing these steps on a guest domain, see Migrating a Non-Global Zone to a Different Machine in Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management.
Note - The P2V tool does not update any zone configuration, such as the zone path or network interface. Nor does the tool move or configure the storage for the zone path. You must manually update the zone configuration and move the zone path on the guest domain. See Migrating a Non-Global Zone to a Different Machine in Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management.
This procedure describes how to install the ldmp2v command on an Oracle Solaris 10 system by using the SUNWldmp2v package.
If you want to install the ldmp2v command on an Oracle Solaris 11 system, the command is installed by default when you install the ldomsmanager package.
The SUNWldmp2v package is included in the Oracle VM Server for SPARC zip file.
For Oracle Solaris 10, see Configuring RBAC (Task Map) in System Administration Guide: Security Services. For Oracle Solaris 11.1, see Part III, Roles, Rights Profiles, and Privileges, in Oracle Solaris 11.1 Administration: Security Services.
# pkgadd -d . SUNWldmp2v
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 – Back-end type of zvol, file, or disk
BACKEND_SPARSE – Whether to create back-end 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 back-end 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.
The BACKEND_PREFIX property is not applicable to the disk back end.
BOOT_TIMEOUT – Timeout for Oracle Solaris OS boot in seconds
For more information, see the ldmp2v.conf.sample configuration file that is part of the downloadable bundle.