2.2 Installing Oracle VM Server on SPARC Hardware

In addition to x86-based hardware, this release of Oracle VM Manager can manage SPARC-based host hardware. This chapter discusses installing and configuring the software required to support management of server pools, Oracle VM Servers, and guest virtual machines on SPARC systems in Oracle VM Manager. This chapter is intended for system administrators who want to install the software required to manage Oracle VM Server for SPARC systems in Oracle VM Manager.

Note

Access the Oracle VM Server for SPARC documentation at http://www.oracle.com/technetwork/documentation/vm-sparc-194287.html. To determine the version of the Oracle VM Server for SPARC documentation to reference, run the pkg list ldomsmanager command.

2.2.1 Preinstallation Tasks and Requirements

Your SPARC server must meet the minimum hardware and software requirements listed in this section.

2.2.1.1 Hardware Requirements

To install Oracle VM Server for SPARC, you need a SPARC T-series, SPARC M-series, or SPARC S-series server. See Supported Platforms in the Oracle VM Server for SPARC Installation Guide.

2.2.1.2 Software and System Firmware Requirements

The software required to configure your SPARC server so that it is discoverable by Oracle VM Manager is as follows:

Table 2.2 Required Software and System Firmware for SPARC Servers

Software and System Firmware

Description

Oracle Solaris OS

Install the latest Oracle Solaris 11.3 SRU OS on the control domain.

See the following sections in the Oracle VM Server for SPARC Installation Guide:

  • Oracle Solaris 11.3 OS requirements, see Oracle Solaris OS Versions.

  • Oracle Solaris OS installation and upgrade procedures, see Installing and Upgrading the Software.

    Note

    Oracle VM Agent for SPARC Release 3.4.6 supports Oracle Solaris 11.4. For information about upgrading to this Release 3.4.6, see Section 5.8.2.2, “Updating to Oracle Solaris 11.3 Manually ”.

SPARC System Firmware

The firmware for your SPARC servers must match the required version to support Oracle VM Server for SPARC.

See the following sections in the Oracle VM Server for SPARC Installation Guide:
  • SPARC system firmware requirements for Oracle Solaris 11.3 or Solaris 11.4 OS, see System Firmware Versions and Oracle Solaris OS Versions.

  • Upgrade procedures for SPARC system firmware, see Upgrading the System Firmware.

Oracle VM Server for SPARC

Install at least Oracle VM Server for SPARC 3.3 on your SPARC server. Note that this software is included by default with the Oracle Solaris 11.3 OS. The Oracle VM Server for SPARC 3.4 software is included by default with the Oracle Solaris 11.3 SRU 8 OS.

Note

Run the pkg list ldomsmanager command to obtain the version of the Oracle VM Server for SPARC software.

Oracle VM Agent for SPARC

Oracle VM Agent for SPARC must be installed in the control domain. Oracle VM Agent for SPARC enables systems running Oracle VM Server for SPARC to be discovered and managed by Oracle VM Manager.

Note

As of Oracle VM Release 3.4.3, the Oracle VM Agent for SPARC runs with Python 2.7.

See Section 2.2.1.6, “Obtaining the Oracle VM Agent for SPARC Software” for information on downloading and installing Oracle VM Agent for SPARC.

Oracle Solaris Image Package System (IPS) Repositories

An IPS repository must be configured to host the Oracle VM Agent for SPARC software when using an automated installer for Oracle VM Server for SPARC. For more information, see Section 3.2.2, “Setting up an IPS repository”.

When upgrading Oracle VM Servers running on SPARC hardware, two Oracle Solaris IPS repositories are required to ensure you have access to the Oracle Solaris updates and the Oracle VM Agent for SPARC software. For more information, see Section 5.8.3.1, “Setting Up IPS Repositories” in the Upgrading from Oracle VM Agent for SPARC Release 3.3.x or Between 3.4.x Errata Releases section.


2.2.1.3 Network Requirements

Oracle VM Server for SPARC has the same basic network requirements as specified for x86 hardware in Section 2.1.1.3, “Network Requirements”.

Oracle VM Server for SPARC has the following additional network requirements:

Network Configuration Profile.  In Oracle Solaris 11.3, the Oracle VM Agent for SPARC requires the control domain to be configured with the DefaultFixed network configuration profile. If this network configuration profile is not enabled on the control domain then, during the installation of the Oracle VM Agent for SPARC software, the Oracle VM Agent for SPARC setup tool offers the opportunity to enable this network configuration profile and to reconfigure the network.

Alternatively, you can manually configure the DefaultFixed network configuration profile and the network on the control domain before installing the Oracle VM Agent for SPARC. For more information about network configuration profiles, see Configuring and Administering Network Components in Oracle Solaris 11.3 available at:

http://docs.oracle.com/cd/E53394_01/

Note

This section applies only to Oracle Solaris 11.3. In Oracle Solaris 11.4, the Default Fixed network configuration profile has been removed.

Server Hostname.  The server hostname should be different from "localhost" and it should resolve to an IP address different from 127.0.0.1.

You can check the hostname of the server with the hostname command:

# hostname
  foo.example.com

If the command returns "localhost" then use the hostname command to change the hostname.

You can check that the hostname resolves to an IP address with the getent command:

# getent hosts `hostname`
  192.168.1.1

If the command does not return an IP address or returns 127.0.0.1 then update the /etc/hosts file or your name service so that the hostname resolves to a valid IP address. For more information about naming services, see the Working With Oracle Solaris 11.3 Naming and Directory Services: DNS and NIS documentation at:

http://docs.oracle.com/cd/E53394_01/

2.2.1.4 Storage Requirements

Although not a strict requirement, Solaris I/O Multipathing should be enabled for all storage used on the server (SAS, FC, iSCSI). Solaris I/O Multipathing provides higher availability for storage devices through the use of multipathed connections. On a default Solaris installation, Solaris I/O Multipathing is enabled only for SAS controllers using the mpt_sas driver, but it is not enabled for Fibre Channel and iSCSI controller ports. For more information about Solaris I/O Multipathing, refer to Managing SAN Devices and Multipathing in Oracle Solaris 11.3 at:

http://docs.oracle.com/cd/E53394_01/

Enabling Solaris I/O Multipathing.  To enable Solaris I/O multipathing on all supported multipath capable controller ports, use the stmsboot command:

# stmsboot -e

Note

Note that device names change once under Solaris I/O multipathing control, and a reboot is required for changes to take effect.

For more information about enabling Solaris I/O Multipathing, refer to section Enabling and Disabling Multipathing in Managing SAN Devices and Multipathing in Oracle Solaris 11.3 available at:

http://docs.oracle.com/cd/E53394_01/html/E54792/gpiio.html#scrolltoc

Third-Party Storage Devices.  Using Solaris I/O Multipathing with a third-party storage device may require additional configuration. If you have enabled Solaris I/O multipathing using the stmsboot and you are using a third-party storage device and Solaris I/O Multipathing is not effectively enabled for that storage device, then refer to Configuring Third-Party Storage Devices in Managing SAN Devices and Multipathing in Oracle Solaris 11.3 available at:

http://docs.oracle.com/cd/E53394_01/html/E54792/gfjtx.html#scrolltoc

2.2.1.5 Oracle VM Agent for SPARC Configuration Requirements

Before you install the Oracle VM Agent for SPARC, ensure that the server is in the factory-default configuration. During installation, the Oracle VM Agent for SPARC setup tool creates and stores a configuration that is suitable for use with Oracle VM Manager.

Use the following procedure to configure the platform with the factory-default configuration:

  1. If there are domains other than the primary domain, then stop and unbind all domains except the primary domain.

    # ldm stop-domain -a
    # ldm unbind-domain <domain>
  2. Specify the factory-default configuration and shut down the primary domain.

    # ldm set-spconfig factory-default
    # shutdown -i5 -g0 -y
  3. From the service processor, perform a power cycle of the system to load the factory-default configuration.

    -> stop /SYS
    -> start /SYS

2.2.1.6 Obtaining the Oracle VM Agent for SPARC Software

If you do not already have the Oracle VM Agent for SPARC software, download Oracle VM Agent for SPARC from the Oracle Software Delivery Cloud:

https://edelivery.oracle.com/oraclevm

See Section 1.2, “Getting Installation ISOs and Packages”, in the appendix, for more information.

Use of Oracle VM Agent for SPARC is licensed under the GNU General Public License, version 2 license at:

http://www.gnu.org/licenses/gpl-2.0.html

Since SPARC systems already include a hypervisor within the firmware by default, installation of Oracle VM Server for SPARC does not replace the existing operating system. Therefore, it is possible to perform the installation from within the existing control domain. Save the Oracle VM Agent for SPARC archive file in the control domain.

2.2.2 Installing the Distributed Lock Manager (DLM) Package

If you have not already installed the DLM package, you should download and install it before you install Oracle VM Agent. The DLM package is required to support server pool clustering.

Download the DLM package, ovs-dlm-3.4.1-bxxx.p5p, from https://edelivery.oracle.com/oraclevm. For more information about downloading software, see Section 1.2, “Getting Installation ISOs and Packages”.

To install the DLM package, do the following:

  1. Stop the ovs-config service:

    # svcadm disable -s ovs-config
  2. Install the DLM package:

    # pkg install -g ovs-dlm-3.4.x-bxxx.p5p dlm
  3. Restart the ovs-config service:

    # svcadm enable ovs-config

2.2.3 Installing Oracle VM Agent for SPARC

Before you install Oracle VM Agent for SPARC, configure the solaris publisher on the system, for example:

# pkg set-publisher -P -g https://pkg.oracle.com/solaris/support/ solaris

For detailed instructions, refer to the repository documentation at https://pkg-register.oracle.com/register/product_info/1/. In addition, for more information about configuring publishers, see http://docs.oracle.com/cd/E53394_01/html/E54739/publisher-config.html#scrolltoc.

To install Oracle VM Agent for SPARC, do the following:

  1. On the control domain, unpack the Oracle VM Agent for SPARC archive file:

    # tar xzf ovs-ldoms-xx.tar.gz
  2. Run the Oracle VM Agent for SPARC installer:

    # cd ovs-ldoms-xx
    # ./install
    Oracle VM Agent Release 3.x.x Installer 

    The installer includes a check to determine whether or not you are running a supported version of Solaris. If the Solaris version is below 11, the installer exits with an error message.

  3. The installer installs all required packages

    - Installing Packages
    
               Packages to install:  6
           Create boot environment: No
    Create backup boot environment: No
                Services to change:  1
    
    DOWNLOAD                                PKGS         FILES    XFER (MB)   SPEED
    Completed                                6/6       226/226      1.6/1.6    0B/s
    
    PHASE                                          ITEMS
    Installing new actions                       353/353
    Updating package state database                 Done
    Updating image state                            Done
    Creating fast lookup database                   Done
    Reading search index                            Done
    Updating search index                            6/6
  4. The installer runs the Oracle VM Agent setup tool, ovs-agent-setup. For more information about the Oracle VM Agent setup tool, see Section 2.2.4, “Configuring Oracle VM Agent for SPARC”.

    - Configuring the OVS Agent
  5. The installer enables all required SMF services. See Section 2.2.6, “Using the Oracle VM Agent for SPARC Service” for information on using the Oracle VM Agent for SPARC service.

    - Enabling Required Services
    Installation Completed.

The Oracle VM Agent for SPARC is installed in the control domain. Oracle VM Server for SPARC is now configured and ready to be discovered and managed by Oracle VM Manager.

2.2.4 Configuring Oracle VM Agent for SPARC

The Oracle VM Agent for SPARC can be configured using the Oracle VM Agent for SPARC setup command, ovs-agent-setup. This command checks that the system is properly configured to run the Oracle VM Agent . If the system is not properly configured then the command attempts to fix the configuration. The ovs-agent-setup command is automatically run when installing the Oracle VM Agent.

It is possible to run this command manually to control the configuration of the Oracle VM Agent for SPARC, run the ovs-agent-setup command on the control domain:

# ovs-agent-setup configure

2.2.4.1 Configuring the Network

  1. If the server is not configured with the DefaultFixed network configuration profile, then the network profile configuration menu is displayed.

    Network Configuration
    *** ERROR: The DefaultFixed network profile is not enabled.
    
    ----------------------------------------------------------------------
    
    Network Profile Configuration
    
    The system must be configured with the DefaultFixed network
    profile. You can manually configured the DefaultFixed network
    or you can use this tool to do the configuration. This tool
    will configure a single network interface, all other network
    interfaces will be unconfigured.
    
    Do you want to use this tool to configure the network?
    
      1) Yes, use this tool to configure the network
      2) No, I will configure the network manually
    
    Choice (1-2) [1]:

    To use the tool to enable the DefaultFixed network configuration profile and configure the network, select 1.

    To skip the configuration of the network, select 2. In which case, you must manually enable the DefaultFixed network configuration profile and configure the network.

  2. When configuring the network, if you are not connected to the system console then a warning is displayed.

    !!! WARNING !!!
    
    You are not connected to the system console. Reconfiguring
    the network can disrupt your remote connection to the server
    and you can lose the remote access to the server.
    
    !!! WARNING !!!
    
    Are you sure that you want to continue?
    
      1) Yes, continue and configure the network
      2) No, cancel the configuration of the network
    
    Choice (1-2):

    To continue the network configuration, select 1.

    Warning

    Configuring the network can disrupt current network connections to the server and you can potentially lose your connection to the server. So it is safer to configure the network from the system console.

    To cancel the configuration of the network, select 2. Then connect to the system console, and restart the configuration by running the ovs-agent-setup configure again.

  3. The Oracle VM Management Interface menu is displayed.

    Collecting information about network interfaces...
    
    ----------------------------------------------------------------------
    
    Oracle VM Management Interface
    
    Choose the network interface to use for the management of this
    machine.
    
      1) net0: 00:14:4f:e3:0f:12 (nxge0)
      2) net1: 00:14:4f:e3:0f:13 (nxge1)
      3) net2: 00:14:4f:e3:0f:14 (nxge2)
      4) net3: 00:14:4f:e3:0f:15 (nxge3)
    
    Interface (1-4) [1]:

    Select the network interface to use for the management of the server.

  4. The Network Interface Configuration menu is displayed.

    IPv4 Configuration for net0
    
      1) Dynamic IP configuration (DHCP)
      2) Manual address configuration
    
    IPv4 Configuration (1-2) [1]:

    To configure the network interface with DHCP, select 1. To configure the network interface with a static IP address, select 2.

    Configuring the Network with DHCP
    1. If the network interface is to be configured with DHCP, then the Hostname Configuration menu is displayed.

      Hostname Configuration
      
      If your system is part of a larger network where hostnames
      are assigned by DHCP, select automatically via DHCP.
      Otherwise, select manually and enter a hostname for your
      system.
      
        1) automatically via DHCP
        2) manually
      
      Hostname Configuration (1-2) [1]:

      If the server uses DHCP to assign its hostname, select 1. If the server has its own hostname, select 2. Then, at 'Hostname' prompt, enter the hostname to be used.

    2. The Oracle VM management interface configuration is displayed:

      Oracle VM Management Interface
      
        Interface: net0
        IP Address: DHCP
        Hostname: DHCP
      
      Are these parameters correct?
      
        1) Yes, configure the network with these parameters
        2) No, enter new parameters for the network configuration
      
      Choice (1-2):

      Select 1 to confirm that parameters are correct. The tool then configures the network. Select 2 if you want to enter new parameters, the process to configure the network then restarts from the beginning.

    Configuring the Network With a Static IP
    1. If the network interface is to be configured with a static IP configuration, then the tool requests to enter IP configuration information.

      IP Address [192.168.1.10]:
        Prefix (Netmask) [255.255.255.0]:
        Gateway [192.168.1.1]:
        Primary DNS [192.168.168.168]:
        Secondary DNS [192.168.169.169]:
        Hostname [foo.example.com]:
    2. The Oracle VM management interface configuration is displayed:

      Oracle VM Management Interface
      
        Interface: net0
        IP Address: 192.168.1.10
        Prefix (Netmask): 255.255.255.0
        Gateway: 192.168.1.1
        Primary DNS: 192.168.168.168
        Secondary DNS: 192.168.169.169
        Hostname: foo.example.com
      
      Are these parameters correct?
      
        1) Yes, configure the network with these parameters
        2) No, enter new parameters for the network configuration
      
      Choice (1-2):

      Select 1 to confirm that parameters are correct. The tool then configures the network. Select 2 if you want to enter new parameters, the process to configure the network then restarts from the beginning.

    Configuring the Hostname

    The setup tool checks if the server is configured with a valid hostname, that is a hostname different from "localhost" and that resolves to an IP address different from 127.0.0.1.

    1. If the hostname of the server is set to localhost, then an error is displayed.

      *** ERROR: The server has an invalid hostname (localhost).
      
      ----------------------------------------------------------------------
      
      Server Hostname
      
      The server has no hostname or an invalid hostname. Use
      the "hostname" command to check and configure the hostname
      of the server. You might also want to check the network
      configuration of the server.
      
      Press <return> to continue...
      *** ERROR: The server has an invalid hostname (localhost).

      After the setup tool exists, you must use the hostname command to configure the hostname of the server.

    2. If the hostname resolves to the 127.0.0.1 then an error is displayed and the /etc/hosts file is updated to not resolve the hostname to 127.0.0.1.

      *** ERROR: The server hostname (foo) should not resolve to 127.0.0.1.
      Configuring /etc/hosts to not resolve foo to 127.0.0.1
      Updating /etc/inet/hosts, the previous file is backed up as /etc/inet/hosts.20121128190648

      When the setup tool updates the /etc/hosts file, the original /etc/hosts file is backup as /etc/inet/hosts.<date-and-time>.

    3. If the hostname does not resolve to an IP address then an error is displayed.

      *** ERROR: The server hostname (foo) does not resolve to an IP address.
      
      ----------------------------------------------------------------------
      
      Server IP Address
      
      The server hostname does not resolve to an IP address.
      
        hostname: foo
      
      Update the /etc/hosts file or the name service so that the
      hostname of the server is resolved to a valid IP address.
      You might also want to check the network configuration of
      the server.
      
      Press <return> to continue...
      *** ERROR: The server hostname (fooxxx) does not resolve to an IP address.

      After the setup tool exits, you must update the /etc/hosts file or your name service so that the hostname resolves to a valid IP address. For more information about naming services, see the Working With Oracle Solaris 11.3 Naming and Directory Services: DNS and NIS documentation at:

      http://docs.oracle.com/cd/E53394_01/

2.2.4.2 Configure the Storage

The setup tool checks if all disks are configured with Solaris I/O Multipathing. If some disks are not configured with Solaris I/O Multipathing, then the tool prints warning messages, and displays instructions for enabling Solaris I/O Multipathing.

Storage Configuration
*** WARNING: disk c6t216000C0FF8089D5d4s2 is not configured with I/O multipathing
*** WARNING: disk c5t216000C0FF8089D5d4s2 is not configured with I/O multipathing
*** WARNING: disk c3t4d0s2 is not configured with I/O multipathing
*** WARNING: disk c3t0d0s2 is not configured with I/O multipathing
*** WARNING: disk c3t1d0s2 is not configured with I/O multipathing

*** WARNING: Some disks are not configured with I/O multipathing, the usage of Solaris
I/O multipathing is recommended.

----------------------------------------------------------------------
Solaris I/O Multipathing
The usage of Solaris I/O multipathing is recommended. To enable Solaris
I/O multipathing on all supported multipath capable controller ports, run
the following command:
    stmsboot -e
Note that a device will have a different name from its orginal name when
it is under Solaris I/O multipathing control, and a reboot is required for
changes to take effect.
Refer to the stmsboot(1M) man page for more information.
Press <return> to continue...
Note

The setup tool does not automatically enable Solaris I/O Multipathing. For more information about enabling Solaris I/O Multipathing, refer to Section 2.2.1.4, “Storage Requirements”.

2.2.4.3 Configure Clustering

The setup tool checks the clustering software is correctly configured.

If the clustering software is not correctly configured then its configuration is automatically updated.

Cluster Configuration
Cluster Configuration OK

2.2.4.4 Oracle VM Agent Configuration

If the Oracle VM Agent password is not defined then the Oracle VM Agent password menu is displayed.

*** ERROR: The Oracle VM Agent password is not defined.

----------------------------------------------------------------------

Oracle VM Agent password

Enter a password for the Oracle VM Agent (ovs-agent)
This password is used in Oracle VM manager to manage
and monitor this server and its guest VMs. You must
type it twice to ensure you know what it is and
didn't make a mistake in typing.

Password:
Password (confirm):

Enter a password to be used for the Oracle VM Agent. This password is used by Oracle VM Manager to manage and monitor the Oracle VM Server for SPARC, and the guests created and running within it. This is the password you use when discovering Oracle VM Servers in Oracle VM Manager.

Then re-enter the password.

The password characters are not echoed to the screen. If the two passwords do not match, the tool prompts you to enter them again.

2.2.4.5 Configuring the Logical Domains Manager

The setup tool checks if the Logical Domains Manager is correctly configured.

If the Logical Domains Manager is not correctly configured then its configuration is automatically updated.

LDoms Manager Configuration
*** WARNING: The LDoms Manager is not configured for outgoing migration.
Configuring the domain manager
LDoms Manager Configuration OK

2.2.4.6 Activating a Logical Domain Configuration

The setup tool checks if the logical domain configuration is correct. If the logical domain configuration is not correct then it is automatically updated and saved on the Service Processor:

LDoms Configuration
*** ERROR: The vcc service is not configured on the primary domain.
*** ERROR: The vds service is not configured on the primary domain.
*** WARNING: The primary domain is configured with too many cpus for creating guest virtual
  machines.
*** WARNING: The primary domain is configured with too much memory for creating guest
  virtual machines.
*** WARNING: The primary domain is not configured with the recommended number of cpus (8).
*** WARNING: The primary domain is not configured with the recommended amount of memory (8GB).
*** WARNING: The system is not using the ovm-initial configuration.
Configuring the vcc service
Configuring the vds service
Configuring the primary domain
Saving the ovm-initial configuration on the service processor
LDoms Configuration OK

If the logical domain configuration has been updated then the logical domain configuration menu is displayed.

LDoms Configuration

The LDoms configuration has been created and stored on the
service processor. To activate this configuration, you need
to reboot the system.

Do you want to reboot the system now?

  1) Yes, reboot the system now
  2) No, I will reboot the system later

Choice (1-2):

Select 2 to exit the installer so that you can manually reboot the system to activate the logical domain configuration.

2.2.4.7 Configuring Virtual I/O Services

The setup tool checks that virtual I/O services are correctly configured.

If a virtual I/O service is not correctly configured then its configuration is automatically updated.

Virtual I/O Services Configuration
*** ERROR: The virtual disk service (vds) is not configured to be disabled at boot time.
*** ERROR: The virtual switch service (vsw) is not configured to be disabled at boot time.
Configuring the virtual disk service
Configuring the virtual switch service
Virtual I/O Services Configuration OK

2.2.5 Control Domain CPU and Memory Settings

The Oracle VM Agent setup tool configures the control domain with 1 CPU core. If the server has 16 GB of memory or more, the control domain is allocated 8 GB of memory. If the server has less than 16 GB of memory, the control domain is allocated 2 GB of memory and a warning message is displayed. [1] If you encounter performance issues because the control domain does not have enough CPUs or memory, you can increase the number of CPU cores and the amount of memory assigned to the control domain. Note, with the Oracle VM Agent, you cannot assign less than 1 CPU core and 2 GB of memory to the control domain, while 8 GB of memory for the control domain is the recommended minimum.

Use the following procedure to change the number of CPU cores or the amount of memory assigned to the control domain:

To change the number of CPU cores or memory assigned to the control domain

  1. Connect as root to the control domain.

  2. Specify the number of CPU cores to assign to the control domain. For example, to assign 2 cpu cores to the control domain:

    # svccfg -s ovs-config setprop config/core_count=2
  3. Specify the amount of memory (in GB) to assign to the control domain. For example, to assign 16 GB of memory to the control domain:

    # svccfg -s ovs-config setprop config/memory_size=16
  4. Refresh and restart the ovs-config service:

    # svcadm refresh ovs-config
    # svcadm restart ovs-config
  5. The restart of the ovs-config service automatically reconfigures the control domain with the specified number of CPU cores and amount of memory and restarts the other Oracle VM Agentservices (ovs-agent and ovmwatch). Check that all services come back online:

    # svcs ovm/*
    STATE          STIME    FMRI
    online         15:40:59 svc:/ovm/ovs-config:default
    online         15:40:59 svc:/ovm/ovmwatch:default
    online         15:41:18 svc:/ovm/ovs-agent:default

    If a service fails to restart and goes into the maintenance state, check for errors in the log file of the service. The restart of the ovs-config service fails if the control domain cannot be configured with the specified number of CPU cores and amount of memory.

Note that the reconfiguration of the control domain is achieved dynamically without rebooting the control domain, but the new configuration persists if the control domain is rebooted. The reconfiguration can be achieved while virtual machines are running, and the change impacts any running virtual machines. The server can continue to be managed with Oracle VM Manager while the ovs-agent is not fully restarted.

To restore the default configuration, use the same steps to set the core_count and memory_size to 0.

2.2.6 Using the Oracle VM Agent for SPARC Service

To check the status of the Oracle VM Agent for SPARC service:

# svcs ovs-agent

To start the Oracle VM Agent for SPARC service:

# svcadm enable -r ovs-agent

To stop the Oracle VM Agent for SPARC service:

# svcadm disable ovs-agent

If the Oracle VM Agent service fails to come online, look for errors in the /var/svc/log/ovm-ovs-agent:default.log file.

You can also check if the configuration has any error by running the following command:

# ovs-agent-setup check

If the command reports any error, then the Oracle VM Agent service is be unable to start.

For more detailed information about managing Oracle Solaris 11 services, see Managing System Services in Oracle Solaris 11.3:

http://docs.oracle.com/cd/E53394_01/html/E54799/eqbrs.html#scrolltoc

2.2.7 Oracle VM Agent for SPARC Log File

The Oracle VM Agent for SPARC log file is located at:

/var/log/ovs-agent.log

The Oracle VM Agent for SPARC service log file is located at:

/var/svc/log/ovm-ovs-agent:default.log

The Oracle VM Agent for SPARC configuration service log file is located at:

/var/svc/log/ovm-ovs-config:default.log

2.2.8 Uninstalling Oracle VM Agent for SPARC

To uninstall Oracle VM Agent for SPARC:

  1. On the control domain, change directory to the location in which you uncompressed the Oracle VM Agent (see Section 2.2.3, “Installing Oracle VM Agent for SPARC”), and run the following as the root user:

    # cd ovs-ldoms-xx
    # ./uninstall

    The script uninstalls Oracle VM Agent for SPARC and removes the default Oracle VM Storage Connect plug-ins.



[1] This is only likely to occur on older SPARC systems such as the T2, T2+ and the T3, since these systems can have a minimum of 4 GB or 8 GB of memory. Newer servers like the T4 (with a minimum of 16 GB) and the T5 (with a minimum of 128 GB), are unaffected and are automatically configured so that the control domain is allocated a full 8 GB of memory.