How to Use the Oracle Solaris JumpStart Feature on an Oracle Solaris 10 Guest Domain

Note – The Oracle Solaris JumpStart feature is only available for the Oracle Solaris 10 OS. To
perform an automated installation of the Oracle Solaris 11 OS, you can use the Automated
Installer (AI) feature. See Transitioning From Oracle Solaris 10 JumpStart to Oracle Solaris 11.1
Automated Installer.

Modify your JumpStart profile to reflect this change.
A virtual disk can appear either as a full disk or as a single-slice disk. The Oracle Solaris OS can
be installed on a full disk by using a regular JumpStart profile that specifies multiple partitions.
A single-slice disk only has a single partition, s0, that uses the entire disk. To install the Oracle
Solaris OS on a single disk, you must use a profile that has a single partition (/) that uses the
entire disk.

■ JumpStart profile for installing a UFS root file system.
Normal UFS Profile
filesys c1t1d0s0 free /
filesys c1t1d0s1 2048 swap
filesys c1t1d0s5 120 /spare1
filesys c1t1d0s6 120 /spare2
Actual UFS Profile for Installing aDomain on a Full Disk
filesys c0d0s0 free /
filesys c0d0s1 2048 swap
filesys c0d0s5 120 /spare1
filesys c0d0s6 120 /spare2
Actual UFS Profile for Installing aDomain on a Single-Slice Disk
filesys c0d0s0 free /

■ JumpStart profile for installing a ZFS root file system.
Normal ZFS Profile
pool rpool auto 2G 2G c1t1d0s0
Actual ZFS Profile for Installing aDomain
pool rpool auto 2G 2G c0d0s0

Read More

Howto Install the Oracle Solaris OS on aGuest Domain Froman Oracle Solaris ISO File

1. Stop and unbind the guest domain (ldg1).
primary# ldm stop ldg1
primary# ldm unbind ldg1

2. Add the Oracle Solaris ISO file as a secondary volume and virtual disk.
The following uses solarisdvd.iso as the Oracle Solaris ISO file, iso_vol@primary-vds0 as a
secondary volume, and vdisk_iso as a virtual disk:
primary# ldm add-vdsdev /export/solarisdvd.iso iso_vol@primary-vds0
primary# ldm add-vdisk vdisk_iso iso_vol@primary-vds0 ldg1
The following uses solarisdvd.iso as the Oracle Solaris ISO file, which is stored on the
server1 server. iso_vol@primary-vds0 is a secondary volume, and vdisk_iso is a virtual disk.
The lofiadm command attaches a block device to the ISO image.
primary# lofiadm -a /net/server1/solarisdvd.iso
primary# ldm add-vdsdev /dev/lofi/1 iso_vol@primary-vds0
primary# ldm add-vdisk vdisk_iso iso_vol@primary-vds0 ldg1

3. Check to see that the Oracle Solaris ISO file is added as a secondary volume and virtual disk.
primary# ldm list-bindings
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv SP 4 4G 0.2% 22h 45m
...
VDS
NAME VOLUME OPTIONS DEVICE
primary-vds0 vol1 /dev/dsk/c2t1d0s2
iso_vol /export/solarisdvd.iso
....
------------------------------------------------------------------------------
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldg1 inactive ----- 60 6G
...
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
vdisk1 vol1@primary-vds0
vdisk_iso iso_vol@primary-vds0

4. Bind and start the guest domain (ldg1).
primary# ldm bind ldg1
primary# ldm start ldg1
LDom ldg1 started
primary# telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is ’^]’.
Connecting to console "ldg1" in group "ldg1" ....
Press ~? for control options ..

5. Showthe device aliases in the clientOpenBoot PROM.
In this example, see the device aliases for vdisk_iso, which is the Oracle Solaris ISO image, and
vdisk_install, which is the disk space.
ok devalias
vdisk_iso /virtual-devices@100/channel-devices@200/disk@1
vdisk1 /virtual-devices@100/channel-devices@200/disk@0
vnet1 /virtual-devices@100/channel-devices@200/network@0
virtual-console /virtual-devices/console@1
name aliases

6. On the guest domain's console, boot fromvdisk_iso (disk@1) on slice f.
ok boot vdisk_iso:f
Boot device: /virtual-devices@100/channel-devices@200/disk@1:f File and args: -s
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright (c) 1983-2010, Oracle and/or its affiliates. All rights reserved.

7. Continue with the Oracle Solaris OS installation menu.

Read More

Installing Oracle Solaris OS on a Guest Domain

1. Insert the Oracle Solaris 10 OS or Oracle Solaris 11 OS DVD into the DVD drive.

2. Stop the volume management daemon, vold(1M), on the primary domain.
primary# svcadm disable volfs

3. Stop and unbind the guest domain (ldg1).
primary# ldm stop ldg1
primary# ldm unbind ldg1

4. Add the DVD with the DVD-ROM media as a secondary volume and virtual disk.
The following uses c0t0d0s2 as theDVDdrive in which the Oracle Solaris media resides,
dvd_vol@primary-vds0 as a secondary volume, and vdisk_cd_media as a virtual disk.
primary# ldm add-vdsdev options=ro /dev/dsk/c0t0d0s2 dvd_vol@primary-vds0
primary# ldm add-vdisk vdisk_cd_media dvd_vol@primary-vds0 ldg1

5. Check to see that the DVD is added as a secondary volume and virtual disk.
primary# ldm list-bindings
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv SP 4 4G 0.2% 22h 45m
...
VDS
NAME VOLUME OPTIONS DEVICE
primary-vds0 vol1 /dev/dsk/c2t1d0s2
dvd_vol /dev/dsk/c0t0d0s2
....
------------------------------------------------------------------------------
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldg1 inactive ----- 60 6G
...
DISK
NAME VOLUME TOUT DEVICE SERVER
vdisk1 vol1@primary-vds0
vdisk_cd_media dvd_vol@primary-vds0
....

6. Bind and start the guest domain (ldg1).
primary# ldm bind ldg1
primary# ldm start ldg1
LDom ldg1 started
primary# telnet localhost 5000
Trying 127.0.0.1...
Connected to localhost.
Escape character is ’^]’.
Connecting to console "ldg1" in group "ldg1" ....
Press ~? for control options ..

7. Show the device aliases in the clientOpenBoot PROM.
In this example, see the device aliases for vdisk_cd_media, which is the Oracle SolarisDVD,
and vdisk1, which is a virtual disk on which you can install the Oracle Solaris OS.
ok devalias
vdisk_cd_media /virtual-devices@100/channel-devices@200/disk@1
vdisk1 /virtual-devices@100/channel-devices@200/disk@0
vnet1 /virtual-devices@100/channel-devices@200/network@0
virtual-console /virtual-devices/console@1
name aliases

8. On the guest domain's console, boot fromvdisk_cd_media (disk@1) on slice f.
ok boot vdisk_cd_media:f
Boot device: /virtual-devices@100/channel-devices@200/disk@1:f File and args: -s
SunOS Release 5.10 Version Generic_139555-08 64-bit
Copyright (c), 1983-2010, Oracle and/or its affiliates. All rights reserved.

9. Continue with the Oracle Solaris OS installation menu.

Read More

Enabling Networking Between the Control/Service Domain andOther Domains

By default, networking between the control domain and other domains in the system is
disabled. To enable this, the virtual switch device should be configured as a network device. The
virtual switch can either replace the underlying physical device (nxge0 in this example) as the
primary interface or be configured as an additional network interface in the domain.
Guest domains can automatically communicate with the control domain or service domain as
long as the corresponding network back-end device is configured in the same virtual LANor
virtual network.

How to Configure theVirtual Switch as the Primary Interface
1. Print the addressing information for all interfaces.
primary# ifconfig -a

2. Configure the virtual switch network interface.
primary# ifconfig vsw0 plumb

3. Remove the physical interface for the device that is assigned to the virtual switch (net-dev).
primary# ifconfig nxge0 down unplumb

4. To migrate properties of the physical network device (nxge0) to the virtual switch device (vsw0),
do one of the following:

■ If networking is configured by using a static IP address, reuse the IP address and netmask of
nxge0 for the virtual switch.
primary# ifconfig vsw0 IP-of-nxge0 netmask netmask-of-nxge0 broadcast + up

■ If networking is configured by using DHCP, enable DHCP for the virtual switch.
primary# ifconfig vsw0 dhcp start

5 Make the required configuration file modifications to make this change permanent.
primary# mv /etc/hostname.nxge0 /etc/hostname.vsw0
primary# mv /etc/dhcp.nxge0 /etc/dhcp.vsw0

Enabling the Virtual Network Terminal Server Daemon
Use the svcadm command to enable the virtual network terminal server daemon, vntsd.
primary# svcadm enable vntsd

Use the svcs command to verify that the vntsd daemon is enabled.
primary# svcs vntsd
STATE      STIME    FMRI
online       Oct_08     svc:/ldoms/vntsd:default

Read More

Rebooting toUse Logical Domains

You must reboot the control domain for the configuration changes to take effect and for the
resources to be released for other logical domains to use.

Shut downand reboot the control domain.
primary# shutdown -y -g0 -i6

Note – Either a reboot or power cycle instantiates the new configuration. Only a power cycle
actually boots the configuration saved to the service processor (SP), which is then reflected in
the list-config output.

Read More

How to Set Up the Control Domain

1. Determine whether you have cryptographic devices in the control domain.
Note that only UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 platforms have
cryptographic devices (MAUs). Because newer platforms, such as SPARC T4 systems and
Fujitsu M10 systems, do not have separate cryptographic units, there is no need to assign a
cryptographic accelerator on these platforms.
primary# ldm list -o crypto primary

2. Assign cryptographic resources to the control domain, if applicable.
The following example would assign one cryptographic resource to the control domain,
primary. This leaves the remainder of the cryptographic resources available to a guest domain.
primary# ldm set-mau 1 primary

3. Assign virtual CPUs to the control domain.
For example, the following command would assign 8 virtual CPUs to the control domain,
primary. This leaves the remainder of the virtual CPUs available to a guest domain.
primary# ldm set-vcpu 8 primary

4. Initiate a delayed reconfiguration on the control domain.
primary# ldm start-reconf primary

5. Assign memory to the control domain.
For example, the following command would assign 4 gigabytes of memory to the control
domain, primary. This leaves the remainder of the memory available to a guest domain.
primary# ldm set-memory 4G primary

6. Add a logical domain machine configuration to the service processor (SP).
For example, the following command would add a configuration called initial.
primary# ldm add-config initial

7. Verify that the configuration is ready to be used at the next reboot.
primary# ldm list-config
factory-default
initial [current]
This ldm list-config command shows that the initial configuration set will be used after
you perform a power cycle.

Create Primary Control Domain:-

root@proddb01:~# svcadm enable ldmd

root@proddb01:~# ldm add-vcc port-range=5000-5100 primary-vcc0 primary

root@proddb01:~# ldm add-vds primary-vds0 primary

root@proddb01:~# ldm add-vsw net-dev=net1 primary-vsw0 primary

root@proddb01:~# ldm list-services primary

root@proddb01:~# ldm set-vcpu 32 primary

root@proddb01:~# ldm start-reconf primary

root@proddb01:~# ldm set-memory 64G primary

root@proddb01:~# ldm add-config initial

root@proddb01:~# ldm list-config

factory-default

initial [current]

root@proddb01:~# shutdown -y -i 6

Read More

Initial Configuration of the Control Domain

Initially, all system resources are allocated to the control domain. To allow the creation of other
logical domains, you must release some of these resources.

Do not attempt to use memory dynamic reconfiguration (DR) to perform the initial
configuration of the control domain. Although you can use memoryDR to perform this
configuration without needing a reboot, it is not recommended. The memoryDR approach
might take a very long time (longer than a reboot) and could even potentially fail. Instead, use
the ldm start-reconf command to place the control domain in delayed reconfiguration mode
before you change the memory configuration. Then, you can reboot the control domain after
you complete all the configuration steps.

Read More