See Prepare a Shared Storage Location for the Archive.
root@TargetControlDomain:Shared_Storage# ls -rlth -rw-r--r-- 1 root root 97G Feb 13 22:15 solaris10.ova
The ovmtdeploy command reads the contents of the .ova archive and creates an operational logical domain.
Example A – Deploying a Guest Domain with Default CPU and Memory Resources
In this example, the cores option (-C) is omitted so that the deployed guest domain is assigned CPU and memory resources based on what is specified in the archive. The result is that the guest domain is deployed with the same resources that it had on the source system.
For the -v option, specify the same number of virtual disks that were captured using the ovmtcreate command in Create the Source Archive (Alternate Method).
The following command line is shown in multiple lines for readability, but is entered on one line.
root@TargetControlDomain:/ovas# ovmtdeploy -d solaris10 -t primary-vsw0 -E vnet0 -v /dev/rdsk/c0t600144F09F2C0BFD00005A2865A20004d0s2,/dev/rdsk/c0t600144F09F2C0BFD00005A2865B50005d0s2 /ovas/solaris10.ova Oracle VM for SPARC Deployment Utility ovmtdeploy Version 3.5.0.2.1 STAGE 1 - EXAMINING SYSTEM AND ENVIRONMENT ------------------------------------------ Checking user privileg Performing platform & prerequisite checks Checking for required services Named resources available STAGE 2 - ANALYZING ARCHIVE & RESOURCE REQUIREMENTS --------------------------------------------------- Checking .ova format and contents Validating archive configuration Checking sufficient resources present STAGE 3 - EXTRACTING ARCHIVE ---------------------------- Extracting archive Validating checksums Decompressing disk image(s) Disk /dev/rdsk/c0t600144F09F2C0BFD00005A2865A20004d0s2 was automatically expanded to use entire device Decompressing disk image(s) Disk /dev/rdsk/c0t600144F09F2C0BFD00005A2865B50005d0s2 was automatically expanded to use entire device STAGE 4 - DEPLOYING DOMAIN -------------------------- Creating domain and adding resources Validating deployment
Example B – Deploying a Guest Domain While Specifying the Number of Cores
In this example, the target control domain's cores are listed to see what cores are available. Then the core option (-C) is used to specify the number of cores to assign to the guest domain. In this example, the deployed guest domain is assigned 8 cores instead of the 10 cores that it had on the source system.
For the -v option, specify the same number of virtual disks that were captured using the ovmtcreate command in Create the Source Archive (Alternate Method).
The second command line is shown in multiple lines for readability, but is entered on one line.
root@TargetControlDomain# ldm ls-devices core
CORE
ID %FREE CPUSET
8 100 (64, 65, 66, 67, 68, 69, 70, 71)
9 100 (72, 73, 74, 75, 76, 77, 78, 79)
10 100 (80, 81, 82, 83, 84, 85, 86, 87)
11 100 (88, 89, 90, 91, 92, 93, 94, 95)
64 100 (512, 513, 514, 515, 516, 517, 518, 519)
65 100 (520, 521, 522, 523, 524, 525, 526, 527)
66 100 (528, 529, 530, 531, 532, 533, 534, 535)
67 100 (536, 537, 538, 539, 540, 541, 542, 543)
72 100 (576, 577, 578, 579, 580, 581, 582, 583)
73 100 (584, 585, 586, 587, 588, 589, 590, 591)
74 100 (592, 593, 594, 595, 596, 597, 598, 599)
75 100 (600, 601, 602, 603, 604, 605, 606, 607)
root@TargetControlDomain# ovmtdeploy -d solaris10 -C 64-67,72-75 -t primary-vsw0 -E vnet0
-v /dev/rdsk/c0t600144F09F2C0BFD00005A2865A20004d0s2,/dev/rdsk/c0t600144F09F2C0BFD00005A2865B50005d0s2,
/ovas/solaris10.ova
. . .