|Skip Navigation Links|
|Exit Print View|
|Oracle VM Server for SPARC 2.2 Administration Guide Oracle VM Server for SPARC|
This section describes the process of upgrading the Oracle Solaris OS, firmware, and Logical Domains Manager components on a system that is already using the Oracle VM Server for SPARC software.
If your system is already configured with the Oracle VM Server for SPARC software, upgrade the control domain and the existing domains. Such an upgrade enables the use of all the Oracle VM Server for SPARC 2.2 features on those domains.
Note - Before you upgrade the Oracle VM Server for SPARC software, perform the following steps:
Upgrade the system with the required system firmware.
Apply the required Oracle Solaris 10 OS patches or Oracle Solaris 11 OS SRU.
Save the configurations to the SP.
Refer to Required Software and Patches in Oracle VM Server for SPARC 2.2 Release Notes to find the Oracle Solaris 10 or Oracle Solaris 11 OS that you should use for this version of the Oracle VM Server for SPARC software, and the required and recommended patches for the different domains. Refer to the Oracle Solaris 10 and Oracle Solaris 11 installation guides for complete instructions on upgrading the Oracle Solaris OS.
When reinstalling the Oracle Solaris OS in the control domain, you must save and restore the Logical Domains autosave configuration data and the constraints database file, as described in this section.
You can save and restore autosave configuration directories prior to reinstalling the operating system on the control domain. Whenever you reinstall the operating system on the control domain, you must save and restore the Logical Domains autosave configuration data, which is found in the /var/opt/SUNWldm/autosave-autosave-name directories.
You can use the tar or cpio command to save and restore the entire contents of the directories.
Note - Each autosave directory includes a timestamp for the last SP configuration update for the related configuration. If you restore the autosave files, the timestamp might be out of sync. In this case, the restored autosave configurations are shown in their previous state, either [newer] or up to date.
For more information about autosave configurations, see Managing Logical Domains Configurations.
This procedure shows how to save and restore the autosave directories.
# cd / # tar -cvpf autosave.tar var/opt/SUNWldm/autosave-*
Sometimes an autosave directory might include extraneous files, perhaps left over from a previous configuration, that might corrupt the configuration that was downloaded to the SP. In such cases, clean the autosave directory prior to the restore operation as shown in this example:
# cd / # rm -rf var/opt/SUNWldm/autosave-*
These commands restore the files and directories in the /var/opt/SUNWldm directory.
# cd / # tar -xvpf autosave.tar
Whenever you upgrade the operating system on the control domain, you must save and restore the Logical Domains constraints database file that can be found in /var/opt/SUNWldm/ldom-db.xml.
Note - Also, save and restore the /var/opt/SUNWldm/ldom-db.xml file when you perform any other operation that is destructive to the control domain's file data, such as a disk swap.
If you are using the Oracle Solaris 10 Live Upgrade feature on the control domain, consider adding the following line to the /etc/lu/synclist file:
This line causes the database to be copied automatically from the active boot environment to the new boot environment when you switch boot environments. For more information about /etc/lu/synclist and synchronizing files between boot environments, refer to Synchronizing Files Between Boot Environments in Oracle Solaris 10 8/11 Installation Guide: Live Upgrade and Upgrade Planning.
This section shows how to upgrade to Oracle VM Server for SPARC 2.2 software.
First download the Logical Domains Manager to the control domain. See Downloading the Logical Domains Manager.
Then stop all domains (except the control domain) running on the platform:
Perform this task only if you plan to perform a power cycle of the system or upgrade the firmware. Performing this task is not required if you only upgrade the Logical Domains Manager software.
primary# ldm stop-domain -a
primary# ldm unbind-domain ldom
This section explains how to upgrade to the Oracle VM Server for SPARC 2.2 software.
# svcadm disable ldmd
# pkgrm SUNWldm
# pkgadd -Gd . SUNWldm.v
Specifying the -d option indicates that the package is in the current directory.
The ldm list command should list all domains that are currently defined on the system. In particular, the primary domain should be listed and be in the active state. The following sample output shows that only the primary domain is defined on the system.
# ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active ---c- SP 32 3264M 0.3% 19d 9m
Performing the following steps enables you to “roll back” to a boot environment (BE) that runs the Oracle VM Server for SPARC 2.1 software, if necessary.
# ldm add-config config-name
The following example saves the configuration called ldoms-2.1-config:
# ldm add-config ldoms-2.1-config
# beadm create snapshot-name
The following example creates a snapshot called S10811@ldoms-2.1-backup:
# beadm create S10811@ldoms-2.1-backup
# beadm create -e snapshot-name BE-name
The following example creates a new BE called ldoms-2.1-backup from the snapshot called S10811@ldoms-2.1-backup:
# beadm create -e S10811@ldoms-2.1-backup ldoms-2.1-backup
# pkg update Packages to install: 1 Packages to update: 89 Create boot environment: No Create backup boot environment: No Services to change: 3 PHASE ACTIONS Removal Phase 517/517 Install Phase 806/806 Update Phase 5325/5325 PHASE ITEMS Package State Update Phase 179/179 Package Cache Update Phase 89/89 Image State Update Phase 2/2
Note - For information about Oracle Solaris 11 SRUs, see Oracle Solaris 11 Support Repository Updates (SRU) Index.
# pkg info ldomsmanager Name: system/ldoms/ldomsmanager Summary: Logical Domains Manager Description: LDoms Manager - Virtualization for SPARC T-Series Category: System/Virtualization State: Installed Publisher: solaris Version: 220.127.116.11 Build Release: 5.11 Branch: 0.175.0.0.0.1.0 Packaging Date: Thu Mar 01 23:06:35 2011 Size: 2.34 MB FMRI: pkg://solaris/system/ldoms/ldomsmanager@ 18.104.22.168,5.11-0.175.0.0.0.1.0:20120221T141945Z
# svcadm restart ldmd
# ldm -V
# ldm add-config config-name
The following example saves the configuration called ldoms-2.2-config:
# ldm add-config ldoms-2.2-config