The target system is the system where the guest domain will be deployed.
In this example, the target system is an Oracle SPARC S7-2 running the Oracle Solaris 11 OS. At this point, the Oracle VM Server for SPARC configuration has been initialized with one control domain. All the CPU and memory resources are allocated to the control domain.
As you perform this procedure, take into account the state of your target system and adjust or omit steps as needed.
Capturing the commands and output provides a means to refer back to the collected data.
There are a variety of methods to capture output. You can run the script(1M) command to make a record of a terminal session, or use a terminal window with command and output collection capabilities.
For example:
root@TargetControlDomain# prtdiag |head -1 System Configuration: Oracle Corporation sun4v SPARC S7-2
The Oracle Solaris 11.3 SRU version should be SRU 31 or later to ensure that the latest ovmtutils package is installed. The latest package provides utilities that are used in this lift and shift scenario.
For the alternate method, the target must run Oracle Solaris 11.4 with SRU 7 or later.
For additional details about Oracle Solaris 11 SRUs, refer to MOS Doc IDs 2385753.1 and 2045311.1 on https://support.oracle.com.
In this example, the output of 0.5.11-0.175.3.31.0.6.0 (key numbers are bold) indicates that the target system is running Oracle Solaris 11 with SRU 31.
root@TargetControlDomain# pkg list entire NAME (PUBLISHER) VERSION IFO entire 0.5.11-0.175.3.31.0.6.0 i--
In this example, the target machine is on a different subnet (198.51.100.x) than the Source environment (192.0.2.x). This change in the network topology is addressed in Reconfigure the Target Guest Domain.
root@TargetControlDomain# netstat -rn Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ---------- --------- default 198.51.100.1 UG 10 90185345 198.51.100.0 198.51.100.36 U 9 489772632 aggr0 127.0.0.1 127.0.0.1 UH 5 13612 lo0 203.0.113.0 203.0.113.77 U 3 3515034 net4
root@TargetControlDomain# ldm -V
Logical Domains Manager (v 3.5.0.0.31)
Hypervisor control protocol v 1.12
Using Hypervisor MD v 1.4
System PROM:
Hostconfig v. 1.8.3.a @(#)Hostconfig 1.8.3.a 2016/09/16 14:15
Hypervisor v. 1.17.3.a @(#)Hypervisor 1.17.3.a 2016/09/16 13:38
OpenBoot v. 4.40.3 @(#)OpenBoot 4.40.3 2016/08/17 12:17
root@TargetControlDomain# uname -a SunOS TargetControlDomain 5.11 11.3 sun4v sparc sun4v
The purpose of these commands is to show that available CPU resources in the target system might be entirely in the control domain if the target system is freshly installed. The psrinfo command provides information about the CPU type, vCPUs per core, and the processor speed for the purpose of estimating the required resources for the target guest domain.
root@TargetControlDomain# ldm ls
NAME STATE FLAGS CONS VCPU MEMORY UTIL NORM UPTIME
primary active -n-c-- UART 128 260352M 0.3% 0.3% 2m
root@TargetControlDomain# psrinfo -pv
The physical processor has 8 cores and 64 virtual processors (0-63)
The core has 8 virtual processors (0-7)
The core has 8 virtual processors (8-15)
The core has 8 virtual processors (16-23)
The core has 8 virtual processors (24-31)
The core has 8 virtual processors (32-39)
The core has 8 virtual processors (40-47)
The core has 8 virtual processors (48-55)
The core has 8 virtual processors (56-63)
SPARC-S7 (chipid 0, clock 4267 MHz)
The physical processor has 8 cores and 64 virtual processors (64-127)
The core has 8 virtual processors (64-71)
The core has 8 virtual processors (72-79)
The core has 8 virtual processors (80-87)
The core has 8 virtual processors (88-95)
The core has 8 virtual processors (96-103)
The core has 8 virtual processors (104-111)
The core has 8 virtual processors (112-119)
The core has 8 virtual processors (120-127)
SPARC-S7 (chipid 1, clock 4267 MHz)
In this example, the Oracle VM Server for SPARC services have been configured, and the purpose of this step is to confirm that they are configured.
root@TargetControlDomain# ldm ls-services
VCC
NAME LDOM PORT-RANGE
ovmt-vcc0 primary 5001-5100
VSW
NAME LDOM MACADDRESS NET-DEV DVID|PVID|VIDs
---- ---- ---------- ------- --------------
primary-vsw0 primary 01:00:5E:90:10:72 aggr0 1|1|--
VDS
NAME LDOM VOLUME OPTIONS MPGROUP DEVICE
ovmt-vds0 primary
root@TargetControlDomain# ldm ls -o net
NAME
primary
MAC
01:00:5E:90:10:e6
VSW
NAME MACADDRESS NET-DEV DVID|PVID|VIDs
---- ---------- ------- --------------
primary-vsw0 01:00:5E:90:10:72 aggr0 1|1|--
DEVICE :switch@0 ID :0
LINKPROP :phys-state MTU :1500
INTER-VNET-LINK :on/auto MODE :--
VSW-RELAY-MODE :local
root@TargetControlDomain# ldm ls -o disk
NAME
primary
VDS
NAME VOLUME OPTIONS MPGROUP DEVICE
ovmt-vds0
The source archive (.ova file) can be quite large. In this example scenario, the file is approximately 97GB, and it created in a shared storage location (see Prepare a Shared Storage Location for the Archive).
root@TargetControlDomain# zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT rpool 1.09T 200G 912G 18% 1.00x ONLINE - vpool 1.09T 284G 828G 25% 1.00x ONLINE -
root@TargetControlDomain# zpool status
pool: rpool
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c0t5000CCA0804047E8d0 ONLINE 0 0 0
c0t5000CCA080405774d0 ONLINE 0 0 0
errors: No known data errors
pool: vpool
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
vpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
c0t5000CCA080408CFCd0 ONLINE 0 0 0
c0t5000CCA080401028d0 ONLINE 0 0 0