This page includes the list of major features introduced in each of the following releases of the Oracle VM Server for SPARC (formerly Logical Domains) software:
The Oracle VM Server for SPARC 3.6.2.0.54 update was first released with the Oracle Solaris 11.4 SRU 54 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.54 software are as follows.
For information about the Oracle VM Server for SPARC 3.6.2 update, see Oracle VM Server for SPARC 3.6.2 Supplemental Release Notes for the resolved issues and outstanding issues.
The Oracle VM Server for SPARC 3.6.2.0.51 update was first released with the Oracle Solaris 11.4 SRU 51 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.51 software are as follows:
The Oracle VM Server for SPARC 3.6.2.0.48 update was first released with the Oracle Solaris 11.4 SRU 48 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.48 software are as follows.
The Oracle VM Server for SPARC 3.6.2.0.45 update was first released with the Oracle Solaris 11.4 SRU 45 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.45 software are as follows.
The Oracle VM Server for SPARC 3.6.2.0.42 update was first released with the Oracle Solaris 11.4 SRU 42 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.42 software are as follows.
The Oracle VM Server for SPARC 3.6.2.0.39 update was first released with the Oracle Solaris 11.4 SRU 39 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.39 software are as follows.
For information about the supported hardware and minimum and fully qualified firmware, Oracle Solaris OS and hardware, see System Requirements in Oracle VM Server for SPARC 3.6 Installation Guide.
For information about the Oracle VM Server for SPARC 3.6.2 update, see Oracle VM Server for SPARC 3.6.2 Supplemental Release Notes for the resolved issues and outstanding issues.
The Oracle VM Server for SPARC 3.6.2.0.36 update was first released with the Oracle Solaris 11.4 SRU 36 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.36 software are as follows.
For information about the supported hardware and minimum and fully qualified firmware, Oracle Solaris OS and hardware, see System Requirements in Oracle VM Server for SPARC 3.6 Installation Guide.
For information about the Oracle VM Server for SPARC 3.6.2 update, see Oracle VM Server for SPARC 3.6.2 Supplemental Release Notes for the resolved issues and documentation issues.
The Oracle VM Server for SPARC 3.6.2.0.33 update was first released with the Oracle Solaris 11.4 SRU 33 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.33 software are as follows.
For information about the supported hardware and minimum and fully qualified firmware, Oracle Solaris OS and hardware, see System Requirements in Oracle VM Server for SPARC 3.6 Installation Guide.
For information about the Oracle VM Server for SPARC 3.6.2 update, see Oracle VM Server for SPARC 3.6.2 Supplemental Release Notes for the resolved issues and documentation issues.
The Oracle VM Server for SPARC 3.6.2.0.9 update was first released with the Oracle Solaris 11.4 SRU 30 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.9 software are as follows.
For information about the supported hardware and minimum and fully qualified firmware, Oracle Solaris OS and hardware, see System Requirements in Oracle VM Server for SPARC 3.6 Installation Guide.
For information about the Oracle VM Server for SPARC 3.6.2 update, see Oracle VM Server for SPARC 3.6.2 Supplemental Release Notes for the resolved issues and documentation issues.
The Oracle VM Server for SPARC 3.6.2.0.8 update was first released with the Oracle Solaris 11.4 SRU 27 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.8 software are as follows.
For information about the supported hardware and minimum and fully qualified firmware, Oracle Solaris OS and hardware, see System Requirements in Oracle VM Server for SPARC 3.6 Installation Guide.
For information about the Oracle VM Server for SPARC 3.6.2 update, see Oracle VM Server for SPARC 3.6.2 Supplemental Release Notes for the resolved issues and documentation issues.
The Oracle VM Server for SPARC 3.6.2.0.7 update was first released with the Oracle Solaris 11.4 SRU 24 OS.
The major changes for the Oracle VM Server for SPARC 3.6.2.0.7 software are as follows.
In addition, over 30 bugs were addressed since the release of LDoms 3.6.2. For information about the supported hardware and minimum and fully qualified firmware, Oracle Solaris OS and hardware, see System Requirements in Oracle VM Server for SPARC 3.6 Installation Guide.
For information about the Oracle VM Server for SPARC 3.6.2 update, see Oracle VM Server for SPARC 3.6.2 Supplemental Release Notes for the resolved issues and documentation issues.
The major changes for the Oracle VM Server for SPARC 3.6.2 software are as follows.
For information about the supported hardware and minimum and fully qualified firmware, Oracle Solaris OS and hardware, see System Requirements in Oracle VM Server for SPARC 3.6 Installation Guide.
For information about the Oracle VM Server for SPARC 3.6.2 update, see Oracle VM Server for SPARC 3.6.2 Supplemental Release Notes for the resolved issues and documentation issues.
The major changes for the Oracle VM Server for SPARC 3.6.1 software are as follows.
For information about the supported hardware and minimum and fully qualified firmware, Oracle Solaris OS and hardware, see System Requirements in Oracle VM Server for SPARC 3.6 Installation Guide.
For information about the Oracle VM Server for SPARC 3.6.1 update, see Oracle VM Server for SPARC 3.6.1 Supplemental Release Notes for the resolved issues and documentation issues.
The major changes for the Oracle VM Server for SPARC 3.6 software are as follows. Note that each feature is available on all supported platforms unless otherwise stated. For the list of supported platforms, see Supported Platforms in Oracle VM Server for SPARC 3.6 Installation Guide.
Add the ability to assign zero or more physical devices to a virtual SAN. See Managing the Physical Devices in a Virtual Storage Area Network in Oracle VM Server for SPARC 3.6 Administration Guide.
Enhance the ovmtconfig command with an option to clear local properties. See the ovmtconfig(8) man page.
Improvements to the ldm list-netstat command. See the ldm(8) man page.
Remove support for the UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 servers. An Oracle VM Server for SPARC 3.6 control domain must run at least the Oracle Solaris 11.4 OS, which no longer supports these older servers.
Normalize Oracle VM Server for SPARC man page sections to match Oracle Solaris 11.4 man page organization.
This section describes features that have been added solely to the Oracle Solaris 11.4 OS that are of interest to Oracle VM Server for SPARC users.
Support for listing available virtual consoles and connecting to a virtual console. See Connecting to a Guest Domain Console Over the Network in Oracle VM Server for SPARC 3.6 Administration Guide and the ldmconsole(8) man page.
Support for DLMP over virtual network devices. See Configuring DLMP Aggregations Over Virtual Network Devices in Oracle VM Server for SPARC 3.6 Administration Guide.
For information about the Oracle VM Server for SPARC 3.5.0.3 maintenance update, see Oracle VM Server for SPARC 3.5.0.3 Supplemental Release Notes for the resolved issues and documentation issues.
The Oracle VM Server for SPARC 3.5.0.3 software was first released with the Oracle Solaris 11.3 SRU 35.6 OS.For information about the Oracle VM Server for SPARC 3.5.0.2 maintenance update, see Oracle VM Server for SPARC 3.5.0.2 Supplemental Release Notes for the resolved issues and documentation issues.
The Oracle VM Server for SPARC 3.5.0.2 software was first released with the Oracle Solaris 11.3 SRU 31.6 OS.
The major changes for the Oracle VM Server for SPARC 3.5.0.1 software are as follows. Note that each feature is available on all supported platforms except UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 unless otherwise stated. For the list of supported platforms, see Supported Platforms in Oracle VM Server for SPARC 3.5 Installation Guide.
Disable Power Management feature on Oracle SPARC platforms by default.
Add ldmd/fjpm_enabled SMF property to control the Power Management feature on Fujitsu SPARC platforms.
See New ldmd/fjpm_enabled SMF Property in Oracle VM Server for SPARC 3.5.0.1 Supplemental Release Notes.
The Oracle VM Server for SPARC 3. 5.0.1 software was first released with the Oracle Solaris 11.3 SRU 29.5 OS.The major changes for the Oracle VM Server for SPARC 3.5 software are as follows. Note that each feature is available on all supported platforms except UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 unless otherwise stated. For the list of supported platforms, see Supported Platforms in Oracle VM Server for SPARC 3.5 Installation Guide.
The Oracle VM Server for SPARC 3.5 software was first released with the Oracle Solaris 11.3 SRU 26.5 OS.
Improve Oracle VM Server for SPARC logging and add command logging. See “Logging Oracle VM Server for SPARC Events” in Oracle VM Server for SPARC 3.5 Administration Guide.
Add ldm start-domain -f option to start an I/O domain if the root domains are unavailable. See “Starting a Domain” in Oracle VM Server for SPARC 3.5 Administration Guide.
Specify an amount of time to wait for domains to stop after you issue an ldm stop-domain command. See “Stopping a Domain” in Oracle VM Server for SPARC 3.5 Administration Guide.
Add features to the XML and XMPP interfaces to match the CLI. See Oracle VM Server for SPARC 3.5 Developer's Guide.
Show blacklisted and evacuation-pending core and memory resources. See “Using FMA to Blacklist or Unconfigure Faulty Resources” in Oracle VM Server for SPARC 3.5 Administration Guide.
Add ADI support across live migration. See “Migration Restrictions for Silicon Secured Memory Servers” in Oracle VM Server for SPARC 3.5 Administration Guide.
Enable domain migration when SR-IOV or PCIe cards are present. See “Migrating a Domain That Has an SR-IOV Ethernet Virtual Function Assigned” in Oracle VM Server for SPARC 3.5 Administration Guide.
Increase the success rate of domain migrations between machines whose memory layouts were previously incompatible. See “Migration Requirements for Memory” in Oracle VM Server for SPARC 3.5 Administration Guide.
Ensure that migrated domains do not reappear after an SP reset. See “Saving Post-Migration SP Configurations Automatically” in Oracle VM Server for SPARC 3.5 Administration Guide.
Support native CPU-family migration. See “Domain Migration Requirements for CPUs” in Oracle VM Server for SPARC 3.5 Administration Guide.
Standardize the memory allocation size.
Support the migration of named resources. See “Migrating a Domain That Uses Named Resources” in Oracle VM Server for SPARC 3.5 Administration Guide.
Support SCSI devices that have no LUN0. See “Simulating a LUN0” in Oracle VM Server for SPARC 3.5 Administration Guide.
Support the virtual switch relay. See “Using a Virtual Switch Relay” in Oracle VM Server for SPARC 3.5 Administration Guide.
Better handle MAC address collisions. See “Detecting MAC Address Collisions” in Oracle VM Server for SPARC 3.5 Administration Guide.
Support for updating alternate MAC addresses dynamically. See “Dynamically Updating Alternate MAC Addresses” in Oracle VM Server for SPARC 3.5 Administration Guide.
Add support for up to 999 virtual networks. See “Virtual Network Device” in Oracle VM Server for SPARC 3.5 Administration Guide.
Make MIB enhancements. See Oracle VM Server for SPARC 3.5 Management Information Base User’s Guide.
Make XMPP enhancements to the
Update the OVM template utilities to provide automatic disk expansion. See “Oracle VM Server for SPARC Template Features” in Oracle VM Server for SPARC 3.5 Developer's Guide.
Update the OVM template utilities to create an OpenStack image. See “Oracle VM Server for SPARC Template Features” in Oracle VM Server for SPARC 3.5 Developer's Guide.
Add support for cross-CPU live migration on Fujitsu SPARC M12 servers. See Fujitsu SPARC M12 Server Product Notes.
Add support for setting the maximum page size of a logical domain. See Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.
This feature is supported only on Fujitsu SPARC M12 servers and Fujitsu M10 servers.
The major changes for the Oracle VM Server for SPARC 3.4.0.2 software are as follows. Note that each feature is available on all supported platforms except UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 unless otherwise stated. For the list of supported platforms, see Supported Platforms in Oracle VM Server for SPARC 3.4 Installation Guide.
Enhanced the ovmtcreate command with the -m option to select either the openstack disk image or the default ovf template format.
Enhanced the ovmtdeploy command to expand the underlying disk devices to device extents during template deployment. This expansion operation occurs by default and supports only disk devices and not disk image files. You can use the ovmtdeploy -x command to disable the expansion operation at runtime.
The major changes for the Oracle VM Server for SPARC 3.4 software are as follows. Note that each feature is available on all supported platforms except UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 unless otherwise stated. For the list of supported platforms, see Supported Platforms in Oracle VM Server for SPARC 3.4 Installation Guide.
Added support for the SPARC S7 series servers. See Supported Platforms in Oracle VM Server for SPARC 3.4 Installation Guide.
Enhanced the virtual SCSI HBA feature to enable I/O multipathing in the service domain. See Chapter 12, "Using Virtual SCSI Host Bus Adapters" in Oracle VM Server for SPARC 3.4 Administration Guide.
This feature requires the Oracle Solaris 11.3 OS.
This feature is also available on UltraSPARC T2, UltraSPARC T2 Plus and SPARC T3 servers. However, these older servers do not support booting from a virtual SCSI HBA.
Added MIB support for the virtual SCSI HBA-related
Enabled a trusted host to create virtual devices such as VLANs and VNICs by permitting guest-specified MAC addresses and VLAN IDs. See “Using Trusted Virtual Networks” in Oracle VM Server for SPARC 3.4 Administration Guide.
Extended the verified boot feature to include guest domains. This feature enables you to validate the signatures of SPARC boot blocks and Oracle Solaris kernel modules. See “Using Verified Boot” in Oracle VM Server for SPARC 3.4 Administration Guide.
Changed the default inter-vnet-link property value to auto. The default behavior ensures that inter-vnet LDC channels are enabled unless more than eight virtual networks are associated with a single virtual switch. This property enforces the switching off of inter-vnet-links if the number exceeds the configured value, which is eight by default. See “Inter-Vnet LDC Channels” in Oracle VM Server for SPARC 3.4 Administration Guide and the ldm(1M) man page.
This feature is also available on UltraSPARC T2, UltraSPARC T2 Plus and SPARC T3 servers.
Enhanced property modification methods for the ldm add-vnet, ldm set-vnet, ldm add-vsw, and set-vsw commands. See the ldm(1M) man page.
This feature is also available on UltraSPARC T2, UltraSPARC T2 Plus and SPARC T3 servers.
Expanded the number of LDC channels to 4096 on several platforms.
Added support for the dynamic modification of device-specific properties on InfiniBand SR-IOV devices. Use the ldm set-io property=value InfiniBand-VF-or-PF command.
Changed the default linkprop property value to phys-state. See the ldm(1M) man page.
This feature is also available on UltraSPARC T2, UltraSPARC T2 Plus and SPARC T3 servers.
Enhanced the ldm list-bindings command to show details about virtual network and virtual switch devices. See the ldm(1M) man page.
This feature is also available on UltraSPARC T2, UltraSPARC T2 Plus and SPARC T3 servers.
Enhanced the Oracle VM Server for SPARC template utilities and add the ovmtadm command. See the ovmtadm(1M) man page.
This feature is also available on UltraSPARC T2, UltraSPARC T2 Plus and SPARC T3 servers.
Restricted the XML interface to only support at least version 1.2 of the Transport Layer Security (TLS) protocol. Support for deprecated protocols such as SSLv3, TLSv1.0, and TLSv1.1 has ended.
This feature is also available on UltraSPARC T2, UltraSPARC T2 Plus and SPARC T3 servers.
Added support for physical partition dynamic reconfiguration policy options for Fujitsu M10 servers. See Fujitsu M10/SPARC M10 Systems System Operation and Administration Guide.
This feature is supported only on Fujitsu M10 servers.
The major changes for the Oracle VM Server for SPARC 3.3 software are as follows. Note that each feature is available on all supported platforms except UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 unless otherwise stated. For the list of supported platforms, see Supported Platforms in Oracle VM Server for SPARC 3.3 Installation Guide.
Support the virtual SCSI host bus adapter (vHBA) feature, which enables you to virtualize any type of SCSI device (such as disk, tape, CD, or DVD). The virtualized SCSI device is accessible from a guest domain.
The vHBA feature is compatible with other I/O interfaces such as MPxIO multipathing, which enables a virtual LUN to have the same behavior as a physical LUN. vHBA also enables you to easily configure virtual SANs, which can contain an unbounded number of SCSI devices. See Introduction to Virtual SCSI Host Bus Adapters in Oracle VM Server for SPARC 3.3 Administration Guide and the ldm(1M) man page.
This feature is supported on UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems as well. However, the system firmware of the UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 servers does not support booting from a virtual SCSI HBA.
Enable recovery mode by default. See Recovering Domains After Detecting Faulty or Missing Resources in Oracle VM Server for SPARC 3.3 Administration Guide.
This feature is not supported on SPARC T4 systems.
Add Oracle VM Templates commands to create, deploy, and configure Oracle VM templates for SPARC systems. See Chapter 18, Using Oracle VM Server for SPARC Templates, in Oracle VM Server for SPARC 3.3 Administration Guide.
This feature is supported on UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems as well.
Support whole-core dynamic resource management (DRM). See Using Dynamic Resource Management in Oracle VM Server for SPARC 3.3 Administration Guide.
Add support for CPU socket constraints. See Fujitsu M10/SPARC M10 Systems System Operation and Administration Guide.
This feature is supported only on Fujitsu M10 servers.
Enhance the live migration feature to enable memory block splitting. Memory block splitting eliminates the requirement to have sufficient free contiguous memory regions on the target machine for each memory block that is assigned to the guest domain. The migration can split up memory blocks in the guest domain to fit into available free regions on the target machine.
This feature requires that you run the Oracle Solaris 11.3 OS on the guest domain being migrated.
This feature is supported on UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems as well.
Enable autoreplacement of faulty CPUs with bound processes and faulty CPUs in single-core domains. See Fujitsu M10/SPARC M10 Systems System Operation and Administration Guide.
This feature is supported only on Fujitsu M10 servers.
Dynamically update the net-dev property value by using the ldm set-vsw command.
Expand cross-CPU migration to include the SPARC T7 series servers and SPARC M7 series servers. See Domain Migration Requirements for CPUs in Oracle VM Server for SPARC 3.3 Administration Guide and Cross-CPU Restrictions for Migration in Oracle VM Server for SPARC 3.3 Administration Guide.
Provide support for Ethernet over USB to enable the ldmd daemon to communicate with the SP and provide support for an ldmd connection check. See How to Verify the ILOM Interconnect Configuration in Oracle VM Server for SPARC 3.3 Administration Guide.
This feature is supported only on SPARC T7 series servers and SPARC M7 series servers.
The major changes for the Oracle VM Server for SPARC 3.2.0.1 software are as follows. Note that each feature is available on all supported platforms except UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 unless otherwise stated. For the list of supported platforms, see Supported Platforms in Oracle VM Server for SPARC 3.2 Installation Guide.
The Oracle VM Server for SPARC 3.2.0.1 software was first released with the Oracle Solaris 11.2 SRU 11.5 OS.
Audit records are not generated for Logical Domains Manager actions by default. For more information, see Audit Records Are No Longer Generated for Logical Domains Manager Actions by Default in Oracle VM Server for SPARC 3.2.0.1 Supplemental Release Notes.
The major changes for the Oracle VM Server for SPARC 3.2 software are as follows. Note that each feature is available on all supported platforms except UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 unless otherwise stated. For the list of supported platforms, see Supported Platforms in Oracle VM Server for SPARC 3.2 Installation Guide.
Provide performance counter access control to get, set, and unset a domain's access rights to three groups of performance counters. See Oracle VM Server for SPARC 3.2 Administration Guide and the ldm(1M) man page.
This feature is not available on Fujitsu M10 systems.
Provide migration security enhancements. See Oracle VM Server for SPARC 3.2 Administration Guide, Oracle VM Server for SPARC 3.2 Security Guide, and the ldm(1M) man page.
This feature is also supported on the UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems.
Provide live migration performance enhancements, including parallel memory-mapped I/O and optimized firmware copying routines. These enhancements reduce the overall migration time and the time during which the migrated guest domain is suspended. See Chapter 12, Migrating Domains, in Oracle VM Server for SPARC 3.2 Administration Guide and Migration Requirements for Memory in Oracle VM Server for SPARC 3.2 Administration Guide.
Some of these performance enhancements require at least the Oracle Solaris 11.2 SRU 8 OS and are not supported on the Oracle Solaris 10 OS.
Update virtual disk management for mpgroups to show and specify the selected path to the virtual disk backend. You can see the path that is currently used and dynamically request a path switch. This feature requires at least the Oracle Solaris 11.2.1.5.0 OS. See Configuring Virtual Disk Multipathing in Oracle VM Server for SPARC 3.2 Administration Guide and the ldm(1M) man page.
This feature is also supported on the UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems.
Provide a centralized view of the network devices and network statistics in a physical system or physical domain. Also, provide new link properties for virtual network and switch devices. See Chapter 11, Using Virtual Networks, in Oracle VM Server for SPARC 3.2 Administration Guide and the ldm(1M) man page.
This feature is also supported on the UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems.
Provide a large pool of LDC endpoints to assign to domains. See Using Logical Domain Channels in Oracle VM Server for SPARC 3.2 Administration Guide.
Remove virtual CPU cores and virtual memory from a resource group. See Using Resource Groups in Oracle VM Server for SPARC 3.2 Administration Guide.
Provide support for private virtual LANs. See Using Private VLANs in Oracle VM Server for SPARC 3.2 Administration Guide.
This feature is also supported on the UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems.
Provide support to dynamically assign PCIe buses. See Chapter 6, Creating a Root Domain by Assigning PCIe Buses, in Oracle VM Server for SPARC 3.2 Administration Guide.
This feature is supported only on the SPARC M5 and SPARC M6 systems and Fujitsu M10 systems.
Provide support of FIPS 140-2 mode for migration. See FIPS 140-2 Mode for Domain Migration in Oracle VM Server for SPARC 3.2 Administration Guide
This feature is also supported on the UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems.
Provide support for resilient I/O domains that can continue to run even when their root domains are not available. See I/O Domain Resiliency in Oracle VM Server for SPARC 3.2 Administration Guide
Require that each master domain assigned to a slave domain must have the same failure policy. See Configuring Domain Dependencies in Oracle VM Server for SPARC 3.2 Administration Guide.
This feature is also supported on the UltraSPARC T2, UltraSPARC T2 Plus, and SPARC T3 systems.
For information about the Oracle VM Server for SPARC 3.1.1.2 maintenance update, see the “Oracle VM Server for SPARC 3.1.1.2 Maintenance Update” in Oracle VM Server for SPARC 3.1.1.2, 3.1.1.1, 3.1.1, and 3.1 Release Notes.
The Oracle VM Server for SPARC 3.1.1.2 software was first released with the Oracle Solaris 11.2 SRU 5.5 OS.
For information about the hardware and software requirements for the Oracle VM Server for SPARC 3.1.1.1 maintenance update, see the Oracle VM Server for SPARC 3.1.1.1, 3.1.1, and 3.1 Release Notes.
The changes for this maintenance update of the Oracle VM Server for SPARC 3.1.1.1 software are as follows. Note that each feature is available on all supported platforms unless otherwise stated.
Provides support for private virtual LANs. Using Private VLANs, in Oracle VM Server for SPARC 3.1 Administration Guide.
This feature requires at least the Oracle Solaris 11.2.4.0.0 (SRU 4) OS.
Increases the number of LDC endpoints per guest domain on SPARC T4, SPARC T5, SPARC M5, and SPARC M6 systems. See Using Logical Domain Channels, in Oracle VM Server for SPARC 3.1 Administration Guide.
Adds support for dynamically assigning PCIe endpoint devices to Fujitsu M10 systems. See the Fujitsu M10 Systems Product Notes.
For information about the hardware and software requirements for the Oracle VM Server for SPARC 3.1.1 maintenance update, see the Oracle VM Server for SPARC 3.1.1 and 3.1 Release Notes.
The Oracle VM Server for SPARC 3.1.1 software was first released with the Oracle Solaris 11.1 SRU 17.5 OS.
The changes for this maintenance update of the Oracle VM Server for SPARC 3.1.1 software are as follows. Note that each feature is available on all supported platforms unless otherwise stated.
Adds support for Fibre Channel SR-IOV. See Creating an I/O Domain by Assigning PCIe SR-IOV Virtual Functions, in Oracle VM Server for SPARC 3.1 Administration Guide.
This feature is supported only on SPARC T4, SPARC T5, SPARC M5, and SPARC M6 platforms and Fujitsu M10 systems.
Adds network bandwidth controls. See Controlling the Amount of Physical Network Bandwidth That Is Consumed by a Virtual Network Device, in Oracle VM Server for SPARC 3.1 Administration Guide.
Adds ability to create or destroy multiple virtual functions simultaneously. See the ldm(1M) man page.
For information about the hardware and software requirements for the Oracle VM Server for SPARC 3.1 release, see the Oracle VM Server for SPARC 3.1.1 and 3.1 Release Notes.
The major changes for this release of the Oracle VM Server for SPARC 3.1 software are as follows. Note that each feature is available on all supported platforms unless otherwise stated.
Enhances dynamic I/O virtualization for SR-IOV. See Setting Up I/O Domains, in Oracle VM Server for SPARC 3.1 Administration Guide and Fujitsu M10 System Has Different SR-IOV Feature Limitations, in Oracle VM Server for SPARC 3.1.1 and 3.1 Release Notes.
This feature is supported only on SPARC T4, SPARC T5, SPARC M5, and SPARC M6 platforms and Fujitsu M10 systems.
Adds support for non-primary domains to act as root domains. See Setting Up I/O Domains, in Oracle VM Server for SPARC 3.1 Administration Guide.
This feature is supported only on SPARC T4, SPARC T5, SPARC M5. and SPARC M6 platforms and Fujitsu M10 systems.
Enhances the dynamic reconfiguration operation to act on all types of root domains. See Setting Up I/O Domains, in Oracle VM Server for SPARC 3.1 Administration Guide.
This feature is supported only on SPARC T4, SPARC T5, SPARC M5, and SPARC M6 platforms and Fujitsu M10 systems.
Adds the Fault Management Architecture (FMA) blacklisting feature. When FMA detects faulty CPU or memory resources, Oracle VM Server for SPARC places them on a blacklist. A faulty resource that is on the blacklist cannot be reassigned to any domains until FMA marks it as being repaired. See Handling Hardware Errors, in Oracle VM Server for SPARC 3.1 Administration Guide.
This feature is supported only on SPARC T5, SPARC M5, and SPARC M6 platforms.
Adds a recovery mode feature that automatically recovers domain configurations that cannot be booted because of faulty or missing resources. See Handling Hardware Errors, in Oracle VM Server for SPARC 3.1 Administration Guide.
This feature is supported only on SPARC T5, SPARC M5, and SPARC M6 platforms.
Adds cross-CPU migration support for the SPARC T5, SPARC M5, and SPARC M6 platforms. This feature enables you to perform a migration even if the CPU type of the source and target systems is not identical. Use the ldm set-domain command to set the cpu-arch property.
Adds InfiniBand device support to the SR-IOV feature. See Setting Up I/O Domains, in Oracle VM Server for SPARC 3.1 Administration Guide.
This feature is supported only on SPARC T4, SPARC T5, SPARC M5, and SPARC M6 platforms and Fujitsu M10 systems.
Adds the ldmpower command to show per-domain, power-consumption information. See Viewing Power-Consumption Data in Oracle VM Server for SPARC 3.1 Administration Guide and the ldmpower(1M) man page.
This feature is supported only on SPARC T3, SPARC T4, SPARC T5, SPARC M5, and SPARC M6 platforms.
Adds support for VNICs on virtual networks. See the ldm(1M) man page.
Significant networking performance improvements. See Maximizing Virtual Network Performance, in Oracle VM Server for SPARC 3.1 Administration Guide.
For information about the hardware and software requirements for the Oracle VM Server for SPARC 3.0 release, see the Oracle VM Server for SPARC 3.0 Release Notes.
The Oracle VM Server for SPARC 3.0 software was first released with the Oracle Solaris 11.1 SRU 1 OS.
Adds support for Oracle's SPARC M5-32 platform. See Supported Platforms, in Oracle VM Server for SPARC 3.0 Release Notes.
Adds support for Oracle's SPARC T5 platform. See Supported Platforms, in Oracle VM Server for SPARC 3.0 Release Notes.
Adds support for the Fujitsu M10 system. See Supported Platforms, in Oracle VM Server for SPARC 3.0 Release Notes.
Enhances the resource affinity capability to address memory affinity.
This feature is only supported on Oracle's SPARC T3, SPARC T4, SPARC T5, and SPARC M5 platforms, and the Fujitsu M10 system.
Retrieves a service processor (SP) configuration from the SP into the bootset, which is on the control domain. See Chapter 11, Managing Domain Configurations, in Oracle VM Server for SPARC 3.0 Administration Guide.
This feature is supported on the SPARC T3, SPARC T4, SPARC T5, and SPARC M5 platforms. Some limited support is also available on Oracle's UltraSPARC T2 and UltraSPARC T2 Plus platforms, and the Fujitsu M10 system.
Adds cross-CPU migration support for Oracle Solaris 10. This feature enables you to perform a migration even if the CPU type of the source and target systems is not identical. Use the ldm set-domain command to set the cpu-arch property.
This feature is supported on the SPARC T3, SPARC T4 platforms, and Fujitsu M10 systems.
Enhances the domain shutdown process. This feature enables you to specify whether to perform a full shutdown (default), a quick kernel stop, or force a shutdown. See the ldm(1M) man page.
Enhances the domain shutdown process to perform an ordered shutdown of domaiins based on domain priorities. See Fujitsu M10 Appendix and the ldm(1M) man page.
This feature is supported only on the Fujitsu M10 system.
Adds support for capacity on demand. See Fujitsu M10 Systems Domain Configuration Guide.
This feature is supported only on the Fujitsu M10 system.
Adds support to automatically detect and degrade faulty memory and CPU resources. See “Viewing Faulty Resources” and “Autoreplacement of Faulty CPUs” in Fujitsu M10 Appendix and the ldm(1M) man page.
This feature is supported only on the Fujitsu M10 system.
Adds support to collect hypervisor dump data on Fujitsu M10 systems. See “Hypervisor Dump Collection” in Fujitsu M10 Appendix and the ldm(1M) man page.
Adds domain console logging support. See “Logging Domain Consoles” in Fujitsu M10 Appendix.
This feature is available on all supported platforms.
Adds Oracle Solaris 11 support for Oracle VM Server for SPARC Management Information Base (MIB). See Chapter 16, Using the Oracle VM Server for SPARC Management Information Base Software, in Oracle VM Server for SPARC 3.0 Administration Guide.
Enables a migration process to be initiated without specifying a password on the target system. See the ldm(1M) man page.
Enables the live migration feature while the source machine, target machine, or both, have the power management (PM) elastic policy in effect. See Chapter 9, Migrating Domains, in Oracle VM Server for SPARC 3.0 Administration Guide.
Enables the dynamic resource management (DRM) feature while the host machine has the PM elastic policy in effect. See Using Dynamic Resource Management in Oracle VM Server for SPARC 3.0 Administration Guide.
This feature is only supported on the SPARC T3, SPARC T4, SPARC T5, and SPARC M5 platforms, and the Fujitsu M10 system.
Bug fixes
For information about the hardware and software requirements for the Oracle VM Server for SPARC 2.2 release, see the Oracle VM Server for SPARC 2.2 Release Notes.
The Oracle VM Server for SPARC 2.2 software was first released with the Oracle Solaris 11 SRU 7 OS.
Support for PCIe Single Root I/O Virtualization (SR-IOV) physical functions and virtual functions. See Using PCIe SR-IOV Virtual Functions in Oracle VM Server for SPARC 2.2 Administration Guide.
Support for performing named CPU core and memory block assignments. See Assigning Physical Resources to Domains in Oracle VM Server for SPARC 2.2 Administration Guide.
CPU whole-core allocation enhancement. See Configuring the System With Hard Partitions in Oracle VM Server for SPARC 2.2 Administration Guide.
Single-CPU performance enhancements that provide high instructions per cycle (IPC) on Oracle's SPARC T4 platform. See Tuning the SPARC CPU to Optimize Workload Performance on SPARC T4 Systems in Oracle VM Server for SPARC 2.2 Administration Guide.
Cross-CPU migration support. For information about the cpu-arch property, see the ldm(1M) man page.
Virtual I/O support for Rx Dring mode. For information about the extended-mapin-space property, see the ldm(1M) man page.
For information about the hardware and software requirements for the Oracle VM Server for SPARC 2.1 release, see the Oracle VM Server for SPARC 2.1 Release Notes.
Support for Oracle's SPARC T4 servers (only with patch ID 147507-01). See "Supported Platforms" in Oracle VM Server for SPARC 2.1 Release Notes.
Single-CPU performance enhancements that provide high instructions per cycle (IPC) on the SPARC T4 platform (only with patch ID 147507-01). See Tuning the SPARC CPU to Optimize Workload Performance on SPARC T4 Systems at Oracle VM Technical White Papers.
Live migration support for active domains. See “Migrating Domains” in Oracle VM Server for SPARC 2.1 Administration Guide.
Support for a higher-priority domain to take CPUs from a lower-priority domain when required by DRM policy. See the description of the priority property in the ldm(1M) man page.
Support for disabling inter-vnet channels. See “Inter-Vnet LDC Channels” in Oracle VM Server for SPARC 2.1 Administration Guide and the ldm(1M) man page.
Support for virtual device service validation. See the ldm(1M) man page.
Oracle VM Server for SPARC P2V tool enhancements. See “Oracle VM Server for SPARC Physical-to-Virtual Conversion Tool” in Oracle VM Server for SPARC 2.1 Administration Guide.
Oracle VM Server for SPARC MIB enhancements. See “Using the Oracle VM Server for SPARC Management Information Base Software” in Oracle VM Server for SPARC 2.1 Administration Guide.
Extended mapin space support for the Oracle Solaris 11 Express OS. See the ldm(1M) man page.
Support for the integrated dynamic reconfiguration of cryptographic units and virtual CPUs.
For information about the hardware and software requirements for the Oracle VM Server for SPARC 2.0 release, see the Oracle VM Server for SPARC 2.0 Release Notes.
For information about the hardware and software requirements for the Logical Domains 1.3 release, see the Logical Domains 1.3 Release Notes.
For information about the hardware and software requirements for the Logical Domains 1.2 release, see the Logical Domains 1.2 Release Notes.
For information about the hardware and software requirements for the Logical Domains 1.1 release, see the Logical Domains (LDoms) 1.1 Release Notes.
Use the ldm cancel-operations reconf command instead of the deprecated ldm remove-reconf or cancel-reconf commands to cancel a delayed reconfiguration operation. You can still use the remove-reconf or cancel-reconf subcommands as an alias, but the rm-reconf subcommand does not work.
Use the ldm cancel-operations migration command to cancel a domain migration operation.
For information about the hardware and software requirements for the Logical Domains 1.0.3 release, see the Logical Domains (LDoms) 1.0.3 Release Notes.
For information about the hardware and software requirements for the Logical Domains 1.0.2 release, see the Logical Domains (LDoms) 1.0.2 Release Notes.
For information about the hardware and software requirements for the Logical Domains 1.0.1 release, see the Logical Domains (LDoms) 1.0.1 Release Notes.
For information about the hardware and software requirements for the Logical Domains 1.0 release, see the Logical Domains (LDoms) 1.0 Release Notes.