Go to main content

Oracle® Solaris 11.4 Release Notes

Exit Print View

Updated: May 2021

Issues When Installing Oracle Solaris 11.4

The following issues might occur during or after the installation of Oracle Solaris 11.4.

Spectre Mitigation Warning During VirtualBox Guest Installation (28441940)

When installing Oracle Solaris 11.4 as a VirtualBox guest, or updating an existing VirtualBox guest to Oracle Solaris 11.4, a message similar to the following might appear on the console in the menu selection screen:

PLATFORM: VirtualBox, CSN: 0, HOSTNAME: host
SOURCE: software-diagnosis, REV: 0.2
AUTO-RESPONSE: No automated response available
IMPACT: Oracle Solaris is not running with Spectre Vulnerability Mitigation Enabled
REC-ACTION: Update the CPU with the Spectre capable microcode. Please refer to the 
associated reference document at http://support.oracle.com/msg/SUNOS-8000-LG for the 
latest service procedures and policies regarding this diagnosis.

Workaround: Shut down and restart the VM after enabling Spectre vulnerability mitigation.

  1. Shut down the VM.

  2. Enable Spectre vulnerability mitigation.

    $ /opt/VirtualBox/VBoxManage list vms
    "11.4" {2de193ee-50cd-45d8-9527-72e648438bf5}
    $ /opt/VirtualBox/VBoxManage modifyvm 11.4 --spec-ctrl on
  3. Restart the VM.

For more information, see the documentation for the –-spec-ctrl option in VBoxManage modifyvm on virtualbox.org.

Text Installer Displays in English When Another Language Is Chosen (15744356)

When using the text installer on an equivalent of a physical console such as a web-based remote keyboard, video monitor, mouse, or VirtualBox console, the installer displays text in English even if you have chosen another language during the boot from the install media. The installer displays text in English to avoid a garbled display of non-ASCII characters.

The text installer displays localized text only on an equivalent of a serial console, for example, a service console based on SSH or telnet.

Workaround: None.

Unified Archives Do Not Support Zones on Shared Storage (19627821)

Unified Archives do not support archives that contain zones on shared storage (ZOSS). Although you can use the archiveadm create command to create a recovery or clone archive containing a zone on shared storage, the resulting archive might fail to install.

Workaround: Choose one of the following workarounds:

  • To avoid installation issues with Unified Archives, you must exclude zones on shared storage in an archive.

  • When generating clone archives, you can use the –Z excluded_zone option to exclude specified zones on shared storage.

  • For recovery archives on systems containing zones on shared storage, all non-shared storage zones should be archived individually.

  • When generating a clone or recovery archive for the global zone, use the –D excluded-dataset option must be used to exclude any zones on shared storage zpools that are visible in the global zone.

SPARC: Power Off or On Messages of One or More Hosts Is Displayed in Other Hosts (21511552)

Within an M5 chassis, ILOM messages from one or more Oracle Solaris HOSTs is displayed in the /var/adm/messages file of a different HOST. The following message is displayed:

Jul 23 15:03:41 HOST2-pd2.com SC Alert: [ID 552608
daemon.error] Power | major: Power to /HOST1 has been turned off by: Shell session, Username:root
Jul 23 15:03:41 HOST2-pd2.com SC Alert: [ID 936275
daemon.notice] SDM | minor: Power to /Servers/PDomains/PDomain_1/System
(Hardware Domain 1) has been turned off by Shell session, Username:root.
Jul 23 15:03:41 HOST2-pd2.com SC Alert: [ID 555134
daemon.notice] Audit | minor: root : Set : object =
"/Servers/PDomains/PDomain_1/HOST/power_state" : value = "off" : success

Workaround: You can safely ignore this message.

SPARC: Configuration Changes for Fiber Channel Storage

The updates described in this section simplify configuration of Fiber Channel (FC) disk storage on SPARC platforms and make configuration of FC disk storage on SPARC platforms the same as configuration of FC disk storage on x86 platforms.

  • Oracle Solaris I/O Multipathing is enabled by default. The default setting in /kernel/drv/fp.conf changes to mpxio-disable="no".

    Note -  Use stmsboot(8) to disable or enable Oracle Solaris I/O Multipathing. Do not edit the /kernel/drv/fp.conf file, which is read-only.
  • FC driver binding is changed from ssd(4D) to sd(4D). Move configuration that you have in ssd.conf to sd.conf.

    Note -  Create and edit sd.conf in /etc/driver/drv, not in /kernel/drv. See the driver.conf(5) man page for more information.
  • To configure parameters in sd.conf and ssd.conf, use the JSON-text name:value pair format, instead of the bit-masking format. Bit mask values usually represent different tunable parameters in SPARC sd.conf, SPARC ssd.conf, and x86 sd.conf, which can result in misconfiguration.

  • Associated with the driver binding change, the node name in the private /devices path is changed from ssd@ to the generic disk@.

    For example, with Oracle Solaris I/O Multipathing enabled, the path changes from:




    With Oracle Solaris I/O Multipathing disabled, the path changes from:



  • Use the /dev public namespace, which remains unchanged.

    With Oracle Solaris I/O Multipathing enabled, the Logical Unit identity is encoded in the public /dev name as, for example:


    With Oracle Solaris I/O Multipathing disabled, the target-port identity is encoded in the public /dev name as, for example:


    In both cases, the use of identity in the /dev public namespace insulates applications from changes to the /devices symlink.

Although the changes described in this section above are incompatible with previous Oracle Solaris versions, the Image Packaging System (IPS) provides a compatible way to upgrade from Oracle Solaris 11.3 or earlier to Oracle Solaris 11.4. See Updating Your Operating System to Oracle Solaris 11.4.