Configuring and Installing Root Domains
12c Release 2 (220.127.116.11.0)
This guide provides an end-to-end example for how to use Oracle Enterprise Manager Ops Center.
Using Oracle Enterprise Manager Ops Center, you can configure and install root domains on Oracle VM Server for SPARC systems.
A logical domain is a virtual machine with resources, such as CPU threads, memory, I/O devices, and its own operating system. A root domain is a logical domain that has PCIe root complexes assigned to it. The PCIe bus and all the devices on it are owned by the root domain. From the root domain, you can allocate PCIe Endpoint devices to other logical domains.
When you provision Oracle VM Server for SPARC using Oracle Enterprise Manager Ops Center, ensure to select the option to detach the unused buses. The unused buses are detached from the primary domain and are available for creating root domains. Refer to Oracle Enterprise Manager Ops Center Configuring and Deploying Oracle VM Server for SPARC for more information about deploying Oracle VM Server for SPARC.
The number of root domains that you can create depends on the number of PCIe buses that are available on the server hardware.
In this guide, a root domain is created on Oracle SPARC T4-2 server provisioned with Oracle VM Server for SPARC 3.1 version. The SPARC server has two PCIe buses. One PCIe bus, pci_0, is allocated to the primary domain and the other PCIe bus, pci_1, is detached and available for root domain creation.
You need the following resources to configure and deploy a root domain:
Oracle VM Server for SPARC system
Oracle SPARC T4-2 server installed and configured with Oracle VM Server for SPARC 3.1 version using Oracle Enterprise Manager Ops Center. Refer to the guide Oracle Enterprise Manager Ops Center Configuring and Deploying Oracle VM Server for SPARC for more information.
Obtain the details of the Ethernet devices connected to the PCIe bus that will be assigned to the root domain. You must acquire the network interfaces in the PCIe Endpoint device that are physically connected to the required network.
The network to which the network interface is physically connected must be discovered and managed in Oracle Enterprise Manager Ops Center.
An IP address to be assigned to the root domain OS.
The local filesystem library is used for virtual disks of the root domain. The root domain is not migratable and hence the root domain metadata is stored in the local filesystem library automatically. In this example, 20 GB of virtual disk is created for the root domain.
You must install and configure Oracle Enterprise Manager Ops Center in Oracle Solaris 11 OS and populate the Oracle Solaris 11 Library with SRUs. You can select an Oracle Solaris 11 OS of particular SRU version.
Refer to Oracle Enterprise Manager Ops Center Feature Reference Guide for more information about uploading or importing OS images.
Roles and Permissions
A user with the following roles:
Virtualization admin role to create root domains and server provisioning.
Plan/Profile admin role to create profiles and plan for root domain creation and provisioning.
In this example, the root domain is installed on Oracle VM Server for SPARC 3.1 version. The control domain is configured and deployed in stand-alone mode and it is not placed in a server pool.
The Oracle VM Server for SPARC 3.1 version Summary tab is displayed in the UI as follows:
The I/O Resources tab of the control domain shows the PCIe buses and its allocation status. The I/O Resources tab of the control domain is displayed in the UI as follows:
The necessary profiles and plans that must be created and applied to create root domains are illustrated in the following illustration:
The steps to configure and install root domain is as follows:
Create a root domain with the following resource requirements:
Four CPU Threads.
4 GB of memory. You must provide at least 4 GB of memory for each I/O device.
Native CPU architecture.
Local file system for the virtual disks.
Do not provide any virtual network connection for the root domain. Instead, an Ethernet connection from one of the PCIe Endpoint device of the PCIe bus assigned to the root domain will be used for providing the physical network connection for OS provisioning.
Select Plan Management section in the Navigation pane.
Expand Profiles and Policies and select Logical Domain.
Click Create Profile in the Actions pane.
The Create Logical Domain Profile wizard is displayed.
Enter a name and description to identify the profile.
Retain the option to create a deployment plan for this profile. Select Root Domain in the Subtype.
Enter the name of the root domain as root_dom and the starting number as 1. The root domain will be created with the name as root_dom1.
Provide description and add new tags for the root domain. All the logical domains created using this profile uses the same description and tags.
Click Next to configure the CPU Threads and memory.
The threads in the physical CPU of the Oracle VM Server are dedicated to the logical domains. Select Virtual CPU as the CPU model and enter the values for CPU Threads and memory to be allocated for the root domain:
4 CPU Threads.
4 GB of memory.
Do not specify a value for Crypto Units. Depending on the number of CPU threads, the Crypto units are assigned automatically.
Click Next to specify the PCIe bus for the root domain.
Specify the number of PCIe buses that must be allocated to the root domain. The number of bus allocated in this example is one.
Click Next to specify the storage for the logical domains.
Click the Add icon to select the local filesystem library for the virtual disks. Enter the disk size as 20 GB. You can retain or edit the name of the virtual disk.
Skip the step to specify the networks that must be used for OS provisioning. In this example, virtual network connection is not used. Instead, a physical network connection from one of the PCIe Endpoint device is provided.
Click Next to view the summary of the logical domain details.
Review the information and click Finish to save the profile.
The profile to create to the root domain and the corresponding deployment plan are created. Apply the deployment plan to create the root domain.
Deploy the automatically created root domain plan to create a root domain. The root domain is created without any OS provisioned on it.
Select the Plan Management section in the Navigation pane.
Expand Deployment Plans, then expand Create Logical Domains.
Select the plan from the list of plans and click Apply Deployment Plan in the Actions pane.
In the Select Targets window, select the Oracle VM Server for SPARC system on which you want to create the root domain.
Click Add to Target List to move the selected target Oracle VM Server to the Target List. Select to apply the deployment plan in minimum interaction mode.
The Specify Domain Identity step is displayed. Confirm the given name in the profile and click Next.
Specify the PCIe bus alias for the root domain.
In the Storage Resource Assignments step, retain the storage library selected for the virtual disks from the profile.
There is only one path to access the backend storage and the multipathing group name is not provided. Therefore, multipathing group is not created for this virtual disk.
The virtual disk server is named as root_dom1-vds0 by default. If required, you can modify the name of the virtual disk server.
In the profile to create root domain, the network connections details were not provided. Therefore, the network connection settings step and network resource step are empty.
Schedule the job to run now.
Review the properties and click Apply to apply the deployment plan to create logical domain.
The root domain is created and displayed under the corresponding Oracle VM Server for SPARC server:
The root domain is in installing state as the OS is not yet provisioned on it. You can view the I/O Resources tab of the root domain in the center pane of Oracle Enterprise Manager Ops Center UI. The PCIe bus is assigned to the root domain. The PCIe slot status will be updated once the OS is provisioned on it.
You can also see in the I/O resources details that there are Ethernet devices available in the
/SYS/MB/PCIE7 slots. You must select these slots while provisioning the OS on the root domain.
If the PCIe Endpoint Ethernet device supports SR-IOV configuration, then the virtual functions are created for the physical function. The virtual functions are created only during OS provisioning. The SR-IOV Services are empty for the root domain created:
Create a new OS provisioning profile for the Oracle Solaris 11 OS that must be provisioned on the root domain. You can also edit the default profiles that are created for the Oracle Solaris 11 OS. The procedure in this section describes about creating a new OS provisioning profile.
Select the Plan Management section in the Navigation pane.
Expand Profiles and Policies and select OS Provisioning profile.
Click Create Profile in the Actions pane.
The Create Profile - OS Provisioning wizard is displayed.
Provide the following details for the profile identification:
Enter the name of the profile as ldom_guest_osp.
Enter a suitable description for the profile.
Select Logical Domain as the Subtype.
Click Next to specify the provisioning parameters.
Select the following OSP parameters:
Oracle Solaris 11 OS and SRU 13.4.0 from the list.
solaris-small-server as the Software Group.
Click Next to specify the OS Setup.
Specify the OS setup parameters:
Enter the time zone, language, terminal type, console serial port, and console baud rate.
Enter the root password.
The NFS4 domain is set to dynamic in this example. If a naming service is configured in your environment, enter the NFS4 domain value.
Create a user account to SSH to the OS after provisioning. Provide a user name and password for the account.
Click Next to specify whether you want to use iSCSI disks for OS provisioning.
Do not select the option to use iSCSI disk as this scenario does not involve the use of iSCSI disk for OS provisioning.
The root (/) and a swap file system are defined by default. You can change the swap size. Click the Add icon to add more ZFS file systems.
UFS File System Type is available when you are provisioning Oracle Solaris 10 1/13 OS.
Click Next to specify the name service.
If you have a naming service in place, select the appropriate one and provide the setup details. In this procedure, select None for the naming service.
If you have any naming service in your setup, refer to the help in the wizard or the Oracle Enterprise Manager Ops Center Feature Reference Guide for information about specifying the naming services.
Click Next to view the summary of the parameters selected for the profile.
Review the parameters selected for the profile and click Finish to create the OS provisioning profile.
Click Finish to create the OS provisioning profile.
Select the Plan Management section and expand Profiles and Policies.
Select OS Configuration and click Create Profile in the Actions pane.
Enter the following details to identify the profile:
Name and description of the profile.
Select Logical Domain as the Subtype and Virtual Machine as the Target Type.
Click Next to set the OS Management properties
Select to manage the OS automatically and deploy the Agent Controller to manage the asset.
Select the option Enable Multiplexed I/O so that you can associate block storage libraries such as FC and iSCSI for storage with the OS.
Select the option Enable Single Root I/O Virtualization (SR-IOV) in the root domain. Starting with the 18.104.22.168.0 release, you can choose to disable SR-IOV to root domains by deselecting this option. Disabling SR-IOV prevents Oracle Enterprise Ops Center to automatically create virtual functions on the root domain.
Click Next to specify the networking details.
Select None as the networking option for the OS.
Click Next to specify the networking details for the OS such as network interface.
Enter the number of network interfaces that must be used on the OS. The details of the interfaces are collected while deploying the plan.
Click Next to view the summary of the parameters selected for OS configuration.
Review the parameters and click Finish to create the OS configuration profile.
Create a Provision OS plan that includes the OS Provisioning and OS Configuration profile created in the previous procedures. The provision plan will then be applied on the created root domain.
Select Plan Management section in the Navigation pane.
Expand Deployment Plans and select Provision OS.
Click Create Plan from Tempalte in the Actions pane.
In the Create a Deployment Plan window, enter the following details:
Name of the plan as my_guest_os.
Description for the plan.
Select Stop at failure for Failure Policy.
Select the OS Provisioning Profile and the OS Configuration Profile created for provisioning OS on the root domain.
Click Save to save the deployment plan.
For provisioning OS on the root domain, two important parameters are required:
Boot interface details: The details can be either the PCIe slot and the network port number, or the MAC address of the interface.
OS Provisioning IP Address: The IP address that must be used on the OS. If you have more than one interfaces defined to be used on the OS, the network slot and the IP address for each network connection.
In this scenario, the root domain is created first and then the OS provisioning plan is deployed on the root domain. The available PCIe Endpoint devices are filtered and displayed in the boot interface list.
Select the root domain in the Assets tree of the Navigation pane.
Click Install Server in the Actions pane.
The Install Server window is displayed.
Select the OS provisioning plan created for deploying the OS and apply the plan in minimal interaction mode.
Click Apply Plan.
The OS deployment wizard is displayed. Select not to review the steps that are not included in the deployment plan.
Click Next in the Introduction step.
The plan consists of the OS provisioning profile and OS configuration profile. The application of the plan starts with the Provision OS step.
Click Next to define the boot interface resources.
In the Boot Interface Resource Assignment step, enter the following details:
Select a network in the Network column. The networks that are discovered and managed in Oracle Enterprise Manager Ops Center are listed.
Select the PCIe Endpoint device that provides the network interface for the network connection.
In this example, select
PCIE7(pci_1) in the Controller column. The controller displays only those devices that are available for network connection. It does not display all the endpoint devices available in the bus.
Select the interface from the list of interfaces available for that PCIe slot.
Provide the IP address for the boot interface.
(Optional) Provide the host name for the target.
Review the summary of information for OS provisioning and click Next.
The application of the OS configuration profile starts in the wizard.
The boot interface network details are populated in this step. In this example, there was only one network interface selected to be configured on the OS. Therefore, the network resource is populated with the boot interface network details.
If you have selected more than one interface to be configured on the OS, the first interface is always overwritten by the boot interface network details. Always define the first interface as the boot interface. You can select the interface that you want to be the primary interface. Specify the network resources for the selected interfaces:
Select the network in the Network column.
Select the PCIe Endpoint device in the Controller column. The PCIe Endpoint device provides the network interface for communication.
Select the network interface.
Enter the IP address for OS provisioning.
Select the primary interface.
In this example, the OS is not placed in a server pool for zones.
Review the summary of OS configuration parameters and click Next.
Schedule the job to run now and click Apply.
Execute the provisioning job on the root domain. The OS is provisioned and it is displayed in the UI:
You can now view the I/O Resources tab of the root domain that displays the complete details of the PCIe slot status.
For the SR-IOV enabled network interfaces, the virtual functions are created. In this scenario, the
/SYS/MB/NET2 is SR-IOV enabled network interface. Therefore, the virtual functions were created for the two physical functions:
For any reason, if you want to delete the root domain, starting with the 22.214.171.124.0 release you can use the Delete action to delete root domains if other domains are not using a virtual function from the root domain. For previous releases, if you want to delete the root domain that have virtual functions, then you must delete all the virtual functions created on the SR-IOV enabled PCIe devices before proceeding to delete the domain, all virtual functions must be deleted manually from the command line prompt of the control domain.
You can release the PCIe Endpoint Devices of the root domain, so that you can create I/O domains. Or, you can provide virtual I/O resources services to the other guest domains in the server.
The Oracle Enterprise Manager Ops Center 12c documentation is located at
Refer to the following resources for more information:
http://www.oracle.com/technetwork/documentation/vm-sparc-194287.html for Oracle VM Server for SPARC documentation.
See the Operate How To available at
See the Deploy How To available at
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Enterprise Manager Ops Center Configuring and Installing Root Domains, 12c Release 2 (126.96.36.199.0)
Copyright © 2007, 2014, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.