test

Logical Domains 1.2 Administration Guide

Upgrading to Logical Domains 1.2 Software

This section shows how to upgrade to Logical Domains 1.2 software.

Perform the procedure Upgrade From LDoms 1.0 Software if you want to use your existing LDoms 1.0 configurations with Logical Domains 1.2 software. Existing LDoms 1.0 configurations do not work with Logical Domains 1.2 software.

If you are upgrading from LDoms 1.0.1, 1.0.2, 1.0.3, or 1.1 software, perform the procedure Upgrade From LDoms 1.0.x or 1.1. Existing LDoms 1.0.1, 1.0.2, 1.0.3, and 1.1 configurations do work with Logical Domains 1.2 software.

ProcedureUpgrade From LDoms 1.0 Software

Existing Logical Domains 1.0 configurations do not work with Logical Domains 1.2 software, so you need to save your Logical Domains 1.0 configurations before the upgrade to use them in Logical Domains 1.2 software. The following procedure describes a method for saving and rebuilding a configuration using XML constraints files and the -i option to the ldm add-domain command.

The basic process is to save the constraints information for each domain into an XML file, which can then be re-issued to the Logical Domains Manager after the upgrade to rebuild a desired configuration.

The procedure in this section works for guest domains, not the control domain. Although you can save the control (primary) domain's constraints to an XML file, you cannot feed it back into the ldm add-domain -i command. However, you can use the resource constraints from the XML file to create the CLI commands to reconfigure your primary domain. See Rebuilding the Control Domain for instructions on how to translate typical XML output from an ldm list-constraints -x primary command into the CLI commands needed to reconfigure a primary domain.

The method that follows does not preserve actual bindings, only the constraints used to create those bindings. This means that, after this procedure, the domains will have the same virtual resources, but will not necessarily be bound to the same physical resources.

  1. For each domain, create an XML file containing the domain's constraints.


    # ldm list-constraints -x ldom > ldom.xml

  2. List all the logical domain configurations stored on the service processor.


    # ldm list-config

  3. Remove each logical domain configuration stored on the service processor.


    # ldm rm-config config-name

  4. Disable the Logical Domains Manager daemon (ldmd).


    # svcadm disable ldmd

  5. Remove the Logical Domains Manager package (SUNWldm).


    # pkgrm SUNWldm

  6. Remove the Solaris Security Toolkit package (SUNWjass).


    # pkgrm SUNWjass

  7. Flash update the system firmware.

    For the entire procedure, see Upgrade System Firmware or Upgrade System Firmware Without an FTP Server.

  8. Reinstall the Logical Domain Manager and the Solaris Security Toolkit.

    See Installing the Logical Domains Manager and Solaris Security Toolkit.

  9. Reconfigure the primary domain manually.

    For instructions, see Set Up the Control Domain.

  10. Run the following commands for each guest domain's XML file you created in Step 1.


    # ldm add-domain -i ldom.xml
# ldm bind-domain ldom
# ldm start-domain ldom

ProcedureUpgrade From LDoms 1.0.x or 1.1

  1. Flash update the system firmware.

    For the entire procedure, see Upgrade System Firmware or Upgrade System Firmware Without an FTP Server.

  2. Disable the Logical Domains Manager daemon (ldmd).


    # svcadm disable ldmd

  3. Remove the old SUNWldm package.


    # pkgrm SUNWldm

  4. Add the new SUNWldm package.

    Specifying the -d option assumes that the package is in the current directory.


    # pkgadd -Gd . SUNWldm

  5. Use the ldm list command to verify that the Logical Domains Manager is running.

    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