Perform this procedure on the Oracle Solaris 10 system that is hosting the guest domain that you plan to migrate to another system.
Refer to this Oracle website for further details:https://www.oracle.com/security-alerts/
Installation of the patch provides ovmtcreate and supporting utilities that are required for this lift and sift scenario.
Use the patchadd command. For example:
# patchadd -p | grep 151934
Tip – Use 151934- (number with a dash) as the search string so that all versions of the patch are displayed.
The patching process installs the ovmtcreate utility in the /opt/SUNWldm/lib/contrib directory.
The ovmtcreate command requires temporary space in a working directory to compress the guest domain's storage. As a conservative best practice, create a directory that has space equal to the guest domain's virtual disk storage, divided by 2. For the alternative method, you only need the half the space of the virtual disks you plan to include in the archive.
For best performance, create the working directory on a source system local disk. This avoids copying the disk images over the network. If local storage is not available, you can create a working directory on network storage.
These command line examples display the available space in the working directory called /WorkingDirectory.
root@SourceControlDomain# zfs list wpool NAME USED AVAIL REFER MOUNTPOINT wpool 1.63M 650G 39K /WorkingDirectory root@SourceControlDomain# df -h /WorkingDirectory Filesystem size used avail capacity Mounted on wpool 650G 39K 650G 1% /WorkingDirectory
Rebooting a domain helps to ensure that it is in a healthy state. If there is a problem, it is easier to troubleshoot before the domain is moved to another system.
Ensuring that the control domain has the maximum amount of virtual CPU and memory resources improves the performance of the archive creation. After the archive is created, return the control domain's resources to their original values. As a general rule, the control domain should have a minimum of two CPU cores.
To perform this step, there must be available vCPUs and memory in the source system which are not used or can be borrowed from guest domains that can be shutdown for a temporary period of time.
For more information about CPU and memory allocation, refer to the Oracle VM Server for SPARC Administration Guide based on the version of the virtualization software that is running on the source system. The documentation libraries are available at: https://docs.oracle.com/en/virtualization/oracle-vm-server-sparc/
For example:
root@SourceControlDomain# ldm set-core 4 primary root@SourceControlDomain# ldm set-mem 24G primary