C H A P T E R  1

Logical Domains (LDoms) 1.0.1 Release Notes

These release notes contain changes for this release, supported platforms, a matrix of required software and patches, and other pertinent information about this release, including bugs that affect Logical domains 1.0.1 software.

Changes for This Release

The major changes for this release of Logical Domains 1.0.1 software are to provide support for:

Supported Platforms

Logical Domains (LDoms) Manager 1.0.1 software is supported on the following platforms:

TABLE 1-1   Supported Platforms
Name Reference
Sun UltraSPARCtrademark T1-based Servers:
Sun Firetrademark or SPARC Enterprise T1000 Server Sun Fire or SPARC Enterprise T1000 Server Administration Guide
Sun Fire or SPARC Enterprise T2000 Server Sun Fire or SPARC Enterprise T1000 Server Administration Guide
Netra T2000 Server Netra T2000 Server Administration Guide
Netra CP3060 Blade Netra CP3060 Board Product Notes
Sun Blade T6300 Server Module Sun Blade T6300 Server Module Administration Guide
Sun UltraSPARCtrademark T2-based Servers:
Sun SPARC Enterprise T5120 and T5220 Servers Sun SPARC Enterprise T5120 and T5220 Servers Administration Guide
Sun Blade T6320 Server Module Sun Blade T6320 Server Module Product Notes
Netra CP3260 Blade Netra CP3260 Board Product Notes
Netra T5220 Server Sun Netra T5220 Server Product Notes

Need Updated Hardware for Netra CP3060 Blade to Support LDoms 1.0.1 Software Release

The minimum hardware revision level of the Netra CP3060 Blade to support this LDoms 1.0.1 software release:

This hardware upgrade resulted from LDoms 1.0.1 software requirements described in Bug ID 6584875.

Required, Recommended, and Optional Software and Required Patches

This section lists the required, recommended, and optional software for use with Logical Domains software.

Required Software

Following is a matrix of required software for use with Logical Domains software.

TABLE 1-2   Required Software Matrix
Supported Servers Logical Domains Manager System Firmware Solaris OS - Primary Domain Solaris OS - Guest Domain
Sun UltraSPARCtrademark T1-based servers 1.0.1 6.5.x plus patches Solaristrademark 10 11/06 OS plus patches Solaris 10 11/06 OS plus patches
Sun UltraSPARC T2-based servers 1.0.1 7.0.x plus patches Solaris 10 8/07 OS Solaris 10 11/06 OS plus patches

Recommended Software

Solaris Security Toolkit 4.2 software – This software can help you secure the Solaris OS in the control domain and other domains. Refer to the Solaris Security Toolkit 4.2 Administration Guide and Solaris Security Toolkit 4.2 Reference Manual for more information.

Optional Software

Logical Domains (LDoms) Management Information Base (MIB) 1.0.1 software – This software can help you enable third party applications to perform remote monitoring and a few control operations. Refer to the Logical Domains (LDoms) MIB 1.0.1 Administration Guide and Release Notes for more information.

Required Solaris 10 11/06 OS Patches

Following are the required patches for Solaris 10 11/06 OS for use with Logical Domains software:

Required System Firmware Patches

Following are the required system firmware patches at a minimum for use with Logical Domains software on supported servers:

TABLE 1-3   Required System Firmware Patches
Patches Supported Servers
127575-01 Netra CP3060 Blade
127576-01 Sun Fire and SPARC Enterprise T2000 Servers
127577-01 Sun Fire and SPARC Enterprise T1000 Servers
127578-01 Netra T2000 Server
127579-01 Sun Blade T6300 Server Module
127580-01 Sun SPARC Enterprise T56120 and T5220 Servers
127581-01 Sun Blade T6320 Server Module
127582-01 Netra T5220 Server
127583-01 Netra CP3260 Blade

Location of Patches

You can find the required Solaris OS and system firmware patches at the SunSolveservice mark site:


Location of Documentation

The Logical Domains (LDoms) 1.0.1 Administration Guide and Logical Domains (LDoms) 1.0.1 Release Notes can be found at:


The Beginners Guide to LDoms: Understanding and Deploying Logical Domains can be found at the Sun BluePrints site.


Supported Network Adapters

In a logical domains environment, the virtual switch service running in a service domain can directly interact with GLDv3-compliant network adapters. Though non-GLDv3 compliant network adapters can be used in these systems, the virtual switch cannot interface with them directly. Refer to “Configuring Virtual Switch and Service Domain for NAT and Routing” in the Logical Domains (LDoms) 1.0.1 Administration Guide for information about how to use non-GLDv3 compliant network adapters.

The following adapters with their corresponding drivers are supported by the virtual switch on the Sun Fire and SPARC Enterprise T2000 servers:

The following adapters with their corresponding drivers are supported by the virtual switch on the Sun SPARC Enterprise T5120 and T5220 servers:

procedure icon  To Determine If a Network Adapter Is GLDv3-Compliant

  1. Use the Solaris OS dladm(1M) command, where, for example, bge0 is the network device name.

    # dladm show-link bge0
    bge0            type: non-vlan   mtu: 1500      device: bge0

  2. Look at type: in the output:

    • GLDv3-compliant drivers will have a type of non-vlan or vlan.

    • Non-GLDv3-compliant drivers will have a type of legacy.

Cards Not Supported

The following cards are not supported for this LDoms 1.0.1 software release:

caution icon

Caution - If these unsupported configurations are used with LDoms 1.0.1, stop and unbind all logical domains before the control domain is rebooted. Failure to do so can result in a system crash causing the loss of all the logical domains that are active in the system.

The following bug IDs are filed to provide the support for the currently unsupported cards: 6552598, 6563713, 6589192, and 6598882.

Memory Size Requirements

Logical Domains software does not impose a memory size limitation when creating a domain. The memory size requirement is a characteristic of the guest operating system. Some Logical Domains functionality might not work if the amount of memory present is less than the recommended size. For recommended and minimum size memory requirements, refer to the installation guide for the operating system you are using. For the Solaris 10 11/06 OS, 512 megabyte is the recommended size of memory to install or upgrade, and 128 megabyte is the minimum size. The default size for a swap area is 512 megabyte. For the Solaris 10 11/06 OS, refer to "System Requirements and Recommendations" in the Solaris 10 11/06 Installation Guide: Planning for Installation and Upgrade.

The OpenBoottrademark PROM has a minimum size restriction for a domain. Currently, that restriction is 12 megabyte. If you have a domain less than that size, the Logical Domains Manager will automatically boost the size of the domain to 12 megabyte. Refer to the release notes for your system firmware for information about memory size requirements.

Software That Can Be Used With the Logical Domains Manager

This section details the software that is compatible with and can be used with the Logical Domains software in the control domain.

System Controller Software That Interacts With Logical Domains 1.0.1 Software

The following system controller software interacts with the Logical Domains 1.0.1 software:

General Notes and Issues

This section contains general notes and issues concerning the Logical Domains 1.0.1 software.

Limited Number of Logical Domain Configurations Can Be Stored on the SC

Currently, there is a limit of 8 configurations for logical domains that can be saved on the system controller using the ldm add-config command, not including the factory-default configuration.

Some Features Are Not Available Currently on System Firmware 6.4.x and 6.5.x for Netra T2000 Servers

Currently, system firmware 6.4.x and 6.5.x do not support the following features on Netra T2000 Servers:

The following bug IDs are still outstanding to add this support:

Rebooting the Control Domain When Guest Domains are Running

When you reboot the control domain when guest domains are running, you will encounter the following bugs:

Cleanly Shutting Down and Power Cycling a Logical Domains System

If you have made any configuration changes since last saving a configuration to the SC, before you attempt to power off or power cycle a Logical Domains system, make sure you save the latest configuration that you want to keep.

procedure icon  To Power Off a System With Multiple Active Domains

  1. Shut down and unbind all the non-I/O domains.

  2. Shut down and unbind any active I/O domains.

  3. Halt the primary domain.

    Because no other domains are bound, the firmware automatically powers off the system.

procedure icon  To Power Cycle the System

  1. Shut down and unbind all the non-I/O domains.

  2. Shut down and unbind any active I/O domains.

  3. Reboot the primary domain.

    Because no other domains are bound, the firmware automatically power cycles the system before rebooting it. When the system restarts, it boots into the Logical Domains configuration last saved or explicitly set.

Logical Domain Channels (LDCs) and Logical Domains

There is a limit to the number of LDCs available in any logical domain. In Logical Domains 1.0.1 software, that limit is 256. Practically speaking, this only becomes an issue on the control domain, because the control domain has at least part, if not all, of the I/O subsystem allocated to it, and because of the potentially large number of LDCs created for both virtual I/O data communications and the Logical Domains Manager control of the other logical domains.

If you try to add a service, or bind a domain, so that the number of LDC channels exceeds the 256 limit on the control domain, the operation fails with an error message similar to the following:

13 additional LDCs are required on guest primary to meet this request, but only 9 LDCs are available

The following guidelines can help prevent creating a configuration that could overflow the LDC capabilities of the control domain:

  1. The control domain allocates 12 LDCs for various communication purposes with the hypervisor, Fault Management Architecture (FMA), and the system controller (SC), independent of the number of other logical domains configured.

  2. The control domain allocates one LDC to every logical domain, including itself, for control traffic.

  3. Each virtual I/O service on the control domain consumes one LDC for every connected client of that service.

For example, consider a control domain and 8 additional logical domains. Each logical domain needs at a minimum:

Applying the above guidelines yields the following results (numbers in parentheses correspond to the preceding guideline number from which the value was derived):

12(1) + 9(2) + 8 x 3(3) = 45 LDCs in total

The Logical Domains Manager will accept this configuration.

Now consider the case where there are 32 domains instead of 8, and each domain includes 3 virtual disks, 3 virtual networks, and a virtual console. Now the equation becomes:

12 + 33 + 32 x 7 = 269

The Logical Domains Manager will reject this configuration.

Memory Size Requested Might Be Different From Memory Allocated

Under certain circumstances, the Logical Domains (LDoms) Manager rounds up the requested memory allocation to either the next largest 8-kilobyte or 4-megabyte multiple. This can be seen in the following example output of the ldm list-domain -l command, where the constraint value is smaller than the actual allocated size:

          Constraints: 1965 M
          raddr          paddr5          size
          0x1000000      0x291000000     1968M

Dynamic Reconfiguration of Virtual CPUs With Cryptographic Units

Currently, there is an issue related to dynamic reconfiguration (DR) of virtual CPUs if a logical domain contains one or more cryptographic (mau) units:

Split PCI Regresses in FMA Functionality From Non–Logical Domains Systems

Currently, Fault Management Architecture (FMA) diagnosis of I/O devices in a Logical Domains environment might not work correctly. The problems are:

Logical Domain Variable Persistence

LDom variables for a domain can be specified using any of the following methods:

The goal is that, in all cases, variable updates made using any of these methods always persist across reboots of the domain, and always reflect in any subsequent logical domain configurations saved to the SC.

In Logical Domains 1.0.1 software, there are a few cases where variable updates do not persist:

The following bug IDs have been filed to resolve these issues: 6520041, 6540368, and 6540937. See also Some Commands Read Old bootmode Settings (Bug ID 6585340).

Logical Domains Manager Restart During ldm Command Execution

If the Logical Domains Manager stops and then restarts during execution of any Logical Domains Manager ldm command, the program returns the following error message:

Receive failed: logical domain manager not responding

Recovery: This message usually indicates that the command did not successfully complete. Verify that is the case, and then reissue the command if appropriate.

Bugs Affecting Logical Domains 1.0.1 Software

This section summarizes the bugs that you might encounter when using this version of the software. The bug descriptions are in numerical order by bug ID. If a recovery procedure and a workaround are available, they are specified.

Logical Domains Manager Can Erroneously Assign an Offline CPU to a Logical Domain (Bug ID 6431107)

When the Fault Management Architecture (FMA) places a CPU offline, it records that information so that when the machine is rebooted, the CPU remains offline. The offline designation persists in a non–Logical Domains environment.

However, in a Logical Domains environment, this persistence is not always maintained for CPUs in guest domains. The Logical Domains Manager does not currently record data on fault events sent to it. This means that a CPU in a guest domain that has been marked as faulty, or one that was not allocated to a logical domain at the time the fault event is replayed, can subsequently be allocated to another logical domain with the result that it is put back online.

Currently Cannot Install Guest Domains From DVDs (Bug ID 6434615)

The Solaris 10 OS virtual disk drivers (vdc and vds) currently do not support the CDIO(7I) ioctls that are needed to install guest domains from DVDs. Therefore, it is not possible at this time to install a guest domain from a DVD. However, a guest domain can access a CD/DVD to install applications. If the CD/DVD device is added to the guest domain, and the guest is booted from another virtual disk, the CD can be mounted in the guest domain after the boot operation.

Some format(1M) Command Options Do Not Work With Virtual Disks (Bug IDs 6437722 and 6531557)

Refer to “Operating the Solaris OS With Logical Domains” in Chapter 5 of the Logical Domains (LDoms) 1.0.1 Administration Guide for specific information.

Virtual Disk Should Support Multihost Disk Control Operations (Bug ID 6437772)

The Solaris OS virtual disk drivers (vdc and vds) currently do not support multihost disk control operations (MHI(7I) ioctls).

Logical Domains Manager Should Validate Disk Paths and Network Devices (Bug IDs 6447740 and 6541323)

If a disk device listed in a guest domain’s configuration is either non-existent, already opened by another process, or otherwise unusable, the disk cannot be used by the virtual disk server (vds) but the Logical Domains Manager does not emit any warning or error when the domain is bound or started.

When the guest tries to boot, messages similar to the following are printed on the guest’s console:

WARNING: /virtual-devices@100/channel-devices@200/disk@0: Timeout
connecting to virtual disk server... retrying

In addition, if a network interface specified using the net-dev= parameter does not exist or is otherwise unusable, the virtual switch is unable to communicate outside the physical machine, but the Logical Domains Manager does not emit any warning or error when the domain is bound or started.


In the case of an errant virtual disk service device or volume, perform the following steps:

  1. Stop the domain owning the virtual disk bound to the errant device or volume.

  2. Issue the ldm rm-vdsdev command to remove the errant virtual disk service device.

  3. Issue the ldm add-vdsdev command to correct the physical path to the volume.

  4. Restart the domain owning the virtual disk.

In the case of an errant net-dev= property specified for a virtual switch, perform the following steps:

  1. Issue the ldm set-vsw command with the corrected net-dev= property.

  2. Reboot the domain hosting the virtual switch in question.

Network Devices

If a disk device listed in a guest domain’s configuration is being used by software other than the Logical Domains Manager (for example, if it is mounted in the service domain), the disk cannot be used by the virtual disk server (vds), but the Logical Domains Manager does not emit a warning that it is in use when the domain is bound or started.

When the guest domain tries to boot, a message similar to the following is printed on the guest’s console:

WARNING: /virtual-devices@100/channel-devices@200/disk@0: Timeout
connecting to virtual disk server... retrying

Recovery: Unbind the guest domain, and unmount the disk device to make it available. Then bind the guest domain, and boot the domain.

One CPU Might Show 100% Utilization Under Heavy Network Loads (Bug ID 6492023)

Under heavy network loads, one CPU might show 100% utilization dealing with the network traffic.

Workaround: Attach several CPUs to the domain containing the virtual switch to ensure that the system remains responsive under a heavy load.

Hang Can Occur With Guest OS in Simultaneous Operations (Bug ID 6497796)

Under rare circumstances, when an ldom variable, such as boot-device, is being updated from within a guest domain by using the eeprom(1M) command at the same time that the Logical Domains Manager is being used to add or remove virtual CPUs from the same domain, the guest OS can hang.

Workaround: Ensure that these two operations are not performed simultaneously.

Recovery: Use the ldm stop-domain and ldm start-domain commands to stop and start the guest OS.

Rebooting Multiple Guest Domains Continuously Can Cause OS to Hang (Bug ID 6501039)

Under rare circumstances, if a guest domain is rebooted at a time when it is experiencing high interrupt activity, the OS might hang.

Workaround: None.

Recovery: Use the ldm stop-domain and ldm start-domain commands to stop and start the guest OS.

Panic Message on the Control Domain When Syncing a Guest Domain (Bug ID 6501168)

If too many guest domains are performing I/O to a control or I/O domain, and if that domain is in the middle of panicking, the interrupt request pool of 64 entries overflows and the system cannot save a crash dump. The panic message is as follows:

intr_req pool empty

Workaround: None.

Behavior of the ldm stop-domain Command Needs to Be Improved in Some Cases (Bug ID 6506494)

There are some cases where the behavior of the ldm stop-domain command is confusing.

If the Solaris OS is halted on the domain; for example, by using the halt(1M) command; and the domain is at the prompt "r)eboot, o)k prompt, h)alt?," the ldom stop-domain command fails with the following error message:

LDom <domain name> stop notification failed

Workaround: Force a stop by using the ldm stop-domain command with the -f option.

# ldm stop-domain -f ldom

If the domain is at the kernel module debugger, kmdb(1M) prompt, then the ldm stop-domain command fails with the following error message:

LDom <domain name> stop notification failed

Recovery: If you restart the domain from the kmdb prompt, the stop notification is handled, and the domain does stop.

Cannot Set Security Keys With Logical Domains Running (Bug ID 6510214)

In a Logical Domains environment, there is no support for setting or deleting wide-area network (WAN) boot keys from within the Solaris OS using the ickey(1M) command. All ickey operations fail with the following error:

ickey: setkey: ioctl: I/O error

In addition, WAN boot keys that are set using OpenBoot firmware in logical domains other than the control domain are not remembered across reboots of the domain. In these domains, the keys set from the OpenBoot firmware are only valid for a single use.

The vntsd(1M) Command Needs to Validate the listen-to IP Address (Bug ID 6512526)

The Solaris 10 OS vntsd(1M) command does not validate the listen_addr property in the vntsd command’s Service Management Facility (SMF) manifest. If the listen_addr property is invalid, vntsd fails to bind the IP address and exits.


  1. Update the SMF listen_addr property with the correct IP address.

  2. Refresh vntsd.

    # svcadm refresh vntsd

  3. Restart vntsd.

    # svcadm restart vntsd

Virtual Disk Server Should Export ZFS Volumes as Full Disks (Bug ID 6514091)

When a ZFS, SVM, or VxVM volume is exported as a virtual disk to another domain, then the other domain sees that virtual disk as a disk with a single slice (s0), and the disk cannot be partitioned. As a consequence, such a disk is not usable by the Solaris installer, and you cannot install Solaris on the disk.

For example, /dev/zvol/dsk/tank/zvol is a ZFS volume that is exported as a virtual disk from the primary domain to domain1 using these commands:

# ldm add-vdsdev /dev/zvol/dsk/tank/zvol disk_zvol@primary-vds0
# ldm add-vdisk vdisk0 disk_zvol@primary_vds0 domain1

The domain1 sees only one device for that disk (for example, c0d0s0), and there is no other slice for that disk; for example, no device c0d0s1, c0d0s2, c0d0s3....

Workaround: You can create a file and export that file as a virtual disk. This example creates a file on a ZFS system:

# mkfile 30g /tank/test/zfile
# ldm add-vdsdev /tank/test/zfile disk_zfile@primary-vds0
# ldm add-vdisk vdisk0 disk_zfile@primary-vds0 domain1

Note - When exporting a ZFS, SVM, or VxVM volume as a virtual disk, be aware that you will have to change your configuration once this bug is fixed, and the instructions for changing the configuration will be provided.

The add-vnet Subcommand Allows a Virtual Network Device With the Same MAC Address as Another Logical Domain (Bug ID 6515615)

When creating logical domains with virtual switches and virtual network devices, the Logical Domains Manager does not prevent you from creating these devices with the same given MAC address. This can become a problem if the logical domains with virtual switches and virtual networks that have conflicting MAC addresses are in a bound state simultaneously.

Workaround: Ensure that you do not bind logical domains whose vsw and vnet MAC addresses might conflict with another vsw or vnet MAC address.

Certain ldm Subcommands Return Misleading Messages If One or More Arguments Are Missing (Bug IDs 6519049 and 6573220)

Misleading error messages are returned from certain ldm subcommands that take two or more required arguments, if one or more of those required arguments is missing.

For example, if the add-vsw subcommand is missing the vswitch-name or ldom argument, you receive an error message similar to the following:

# ldm add-vsw net-dev=e1000g0 primary
Illegal name for service: net-dev=e1000g0

For another example, if the add-vnet command is missing the vswitch-name of the virtual switch service with which to connect, you receive an error message similar to the following:

# ldm add-vnet mac-addr=08:00:20:ab:32:40 vnet1 ldg1
Illegal name for VNET interface: mac-addr=08:00:20:ab:32:40

As another example, if you fail to add a logical domain name at the end of an ldm add-vcc command, you receive an error message saying that the port-range= property must be specified.

Recovery: Refer to the Logical Domains (LDoms) Manager 1.0.1 Man Page Guide or the ldm man page for the required arguments of the ldm subcommands, and retry the commands with the correct arguments.

Disks Managed by Veritas DMP Cannot Be Exported to Other Domains (Bug ID 6522993)

In a service domain, disks that are managed by Veritas Dynamic Multipathing (DMP) cannot be exported as virtual disks to other domains. If a disk that is managed by Veritas DMP is added to a virtual disk server (vds) and then added as a virtual disk to a guest domain, the domain is unable to access and use that virtual disk. In such a case, the service domain reports the following errors in the /var/adm/messages file after binding the guest domain:

vd_setup_vd():  ldi_open_by_name(/dev/dsk/c4t12d0s2) = errno 16
vds_add_vd():  Failed to add vdisk ID 0

Recovery: If Veritas Volume Manager (VxVM) is installed on your system, disable Veritas DMP for the disks you want to use as virtual disks.

CPU DR Is Disabled For All Logical Domains That Have MAU Cryptographic Units Bound (Bug ID 6525647)

Due to problems with the Solaris Crypto Framework and its handling of CPU dynamic reconfiguration (DR) events that affect MAU cryptographic units, CPU DR is disabled for all logical domains that have any crypto units bound to it.

Workaround: To be able to use CPU DR on the control domain, all the crypto units must be removed from it while the system is running in the factory-default configuration, before saving a new configuration to the SC. To perform CPU DR on all other domains, stop the domain first so it is in the bound state.

Attempt to Store Boot Command Variable During a Reboot Can Time Out (Bug ID 6527622)

When the Solaris OS reboot(1M) command is issued to reboot a guest OS, the following messages can appear on the guest console:

WARNING: promif_ldom_setprop: ds response timeout
WARNING: unable to store boot command for use on reboot

The reboot proceeds as usual, but all arguments passed to the OpenBoot PROM boot command; that is, arguments that appear after the -- delimiter of the Solaris OS reboot(1M) command, are ignored by the boot code. The same warnings can occur even if no arguments are passed to the reboot command, because the system always attempts to store a default boot command.

Recovery: Once this occurs, there is no recovery.

Workaround: To prevent it from happening on future boots, you can do one of the following:

Disk Recovery Fails in a Service Domain When the Disk Device Is Actively Used as a Virtual Disk (Bug ID 6528156)

The virtual disk server opens the physical disk exported as a virtual disk device at the time of the bind operation. In certain cases, a recovery operation on the physical disk following a disk failure may not be possible if the guest domain is bound.

For instance, when a RAID or a mirror Solaristrademark Volume Manager (SVM) volume is used as a virtual disk by another domain, and if there is a failure on one of the components of the SVM volume, then the recovery of the SVM volume using the metareplace command or using a hot spare does not start. The metastat command shows the volume as resynchronizing, but there is no progress in the synchronization.

Similarly, when a Fibre Channel Arbitrated Loop (FC_AL) device is used as a virtual disk, you must use the Solaris OS luxadm(1M) command with a loop initialization primitive sequence (forcelip subcommand) to reinitialize the physical disk after unbinding the guest.

Note - Recovery mechanisms may fail in a similar manner for other devices, if the mechanism requires that the device being recovered is not actively in use.

Recovery: To complete the recovery or SVM resynchronization, stop and unbind the domain using the SVM volume as a virtual disk. Then resynchronize the SVM volume using the metasync command.

When Running Cluster Software, Selecting the ok Prompt Upon a Logical Domain Shutdown Can Cause Panic (Bug ID 6528556)

If Solaris™ Cluster software is in use with Logical Domains software, and the cluster is shut down, the console of each logical domain in the cluster displays the following prompt:

r)eboot, o)k prompt, h)alt?

If the ok prompt (o option) is selected, the system can panic.


procedure icon  To Force the Primary Domain to Stop at the ok Prompt

Use this procedure only for the primary domain.

  1. Issue the following ALOM command to reset the domain:

    sc> poweron

    The OpenBoot banner is displayed on the console:

    Sun Fire T200, No Keyboard
    Copyright 2007 Sun Microsystems, Inc.  All rights reserved.
    OpenBoot 4.26.0, 4096 MB memory available, Serial #68100096.
    Ethernet address 0:14:4f:f:20:0, Host ID: 840f2000.

  2. Issue the following ALOM command to send a break to the domain immediately after the OpenBoot banner displays:

    sc> break -y

    The logical domain immediately drops to the ok prompt.

procedure icon  To Force All Other Domains to Stop at the ok Prompt

Use this procedure for all logical domains except the primary domain.

  1. Issue the following command from the control domain to disable the auto-boot? variable for the logical domain:

    # ldm set-var auto-boot?=false domain-name

  2. Issue the following command from the control domain to reset the logical domain:

    # ldm start-domain domain-name

    The logical domain stops at the ok prompt.

  3. Issue the following OpenBoot command to restore the value of the auto-boot? variable:

    ok setenv auto-boot? true

ZFS Volumes Need to Have the Same Version of Solaris Software Running on the Service Domain and the Guest Domain (Bug ID 6528974)

If a guest domain is running the Solaris 10 OS and using a virtual disk built from a ZFS volume provided by a service domain running the Solaristrademark Express or OpenSolaris™ programs, then the guest domain might not be able to access that virtual disk.

The same problem can occur with a guest domain running the Solaris Express or OpenSolaris programs using a virtual disk built from a ZFS volume provided by a service domain running Solaris 10 OS.

Workaround: Ensure that the guest domain and the service domain are running the same version of Solaris software (Solaris 10 OS, Solaris Express, or OpenSolaris).

The Virtual Switch, When Plumbed and in Program Mode, Should Write Its MAC Address Into Hardware (Bug ID 6530331)

When plumbing the virtual switch device, you must explicitly set the virtual switch’s MAC address to that of the underlying physical device, rather than allowing the Logical Domains Manager to automatically generate the MAC address, so that your networking will function correctly.

The MAC address of the physical device can be found using the following command; for example:

# ifconfig e1000g0
e1000g0: flags=201104843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,ROUTER,IPv4,CoS> mtu 1500 index 2
     inet netmask fffffe00 broadcast
     ether 0:3:ba:d8:d4:6e

Then you can set the virtual switch to use that MAC address by specifying the ether value from the output as the mac-addr=<num> when executing the ldm add-vsw command.

Page Retirement Does Not Persist in the Logical Domains Environment (Bug IDs 6531030 and 6531058)

When a memory page of a guest domain is diagnosed as faulty, the Logical Domains Manager retires the page in the logical domain. If the logical domain is stopped and restarted again, the page is no longer in a retired state.

The fmadm faulty -a command shows whether the page from either the control or guest domain is faulty, but the page is not actually retired. This means the faulty page can continue to generate memory errors.

Workaround: Use the following command in the control domain to restart the Fault Manager daemon, fmd(1M) :

primary# svcadm restart fmd

Aggregated Network Devices Are Not Supported by the Virtual Switch (Bug ID 6531266)

Currently, the virtual switch (vsw) does not support the use of aggregated network interfaces. If a virtual switch instance is told to use an aggregated device (aggr15 in this example), then a warning message similar to the following appears on the console during boot:

WARNING: mac_open aggr15 failed

Recovery: Configure the virtual switch to use a supported GLDv3-compliant network interface, and then reboot the domain.

Fault Manager Daemon (fmd) Does Not Correctly Recover From a Logical Domain Channel Reset (Bug ID 6533308)

If you reset the system controller while the host is powered on, subsequent error reports and faults are not delivered to the host.

Recovery: Use one of the following methods to recover.

Using the server-secure.driver With an NIS-enabled System, LDoms or No LDoms (Bug ID 6533696)

On a system configured to use the Network Information Services (NIS) or NIS+ name service, if the Solaristrademark Security Toolkit software is applied with the server-secure.driver, NIS or NIS+ fails to contact external servers. A symptom of this problem is that the ypwhich(1) command, which returns the name of the NIS or NIS+ server or map master, fails with a message similar to the following:

Domain atlas some.atlas.name.com not bound on nis-server-1.

This is true whether the Solaris Security Toolkit software is applied indirectly through the ldm-install script menu options or applied directly using this command:

# /opt/SUNWjass/bin/jass-execute -d server-secure.driver

The recommended Solaris Security Toolkit driver to use with the Logical Domains Manager is ldm_control-secure.driver, and NIS and NIS+ work with this recommended driver.

If you are using NIS as your name server, you cannot use the Solaris Security Toolkit profile server-secure.driver, because you may encounter Solaris OS Bug ID 6557663, IP Filter causes panic when using ipnat.conf. However, the default Solaris Security Toolkit driver, ldm_control-secure.driver, is compatible with NIS.

procedure icon  To Reset Your System

  1. Log in to the system console from the system controller, and if necessary, switch to the ALOM mode by typing:

    # #.

  2. Power off the system by typing the following command in ALOM mode:

    sc> poweroff

  3. Power on the system.

    sc> poweron

  4. Switch to the console mode at the ok prompt:

    sc> console

  5. Boot the system to single user mode:

    ok boot -s

  6. Edit the file /etc/shadow, and change the first line of the shadow file that has the root entry to:


  7. You can now log in to the system and do one of the following:

    • Add file /etc/ipf/ipnat.conf.

    • Undo the Solaris Security Toolkit, and apply another driver:

      # /opt/SUNWjass/bin/jass-execute -u
      # /opt/SUNWjass/bin/jass-execute -a ldm_control-secure.driver

Network Performance Is Substantially Worse in a Logical Domain Guest Than in a Non-LDoms Configuration (Bug ID 6534438)

The virtual networking infrastructure adds additional overhead to communications from a logical domain. All packets are sent through a virtual network device, which, in turn, passes the packets to the virtual switch. The virtual switch then sends the packets out through the physical device. The lower performance is seen due to the inherent overheads of the stack.

Workarounds: Do one of the following depending on your server:

Logical Domain Time-of-Day Changes Do Not Persist Across a Power Cycle of the Host (Bug ID 6536572)

If the time or date on a logical domain is modified, for example using the ntpdate command, the change persists across reboots of the domain but not across a power cycle of the host.

Workaround: For time changes to persist, save the configuration with the time change to the SC and boot from that configuration.

Errors to Buses in a Split-PCI Configuration Might Not Get Logged (Bug ID 6542295)

During operations in a split-PCI configuration, if a bus is unassigned to a domain or is assigned to a domain but not running the Solaris OS, any error in that bus or any other bus may not get logged. Consider the following example:

In a split-PCI configuration, the primary domain contains Bus B, and Bus A is not assigned to any domain. In this case, any error that occurs on Bus B might not be logged. (The situation occurs only during a short time period.) The problem resolves when the unassigned Bus A is assigned to a domain and is running the Solaris OS, but by then some error messages might be lost.

Workaround: When using a split-PCI configuration, quickly verify that all buses are assigned to domains and are running the Solaris OS.

The intrstat(1M) Command Is Not Supported for Virtual Devices on a Logical Domain (Bug ID 6543601)

The intrastat(1M) command does not show the statistics corresponding to the interrupts of the virtual devices.

Workaround: None.

During Boot or Installation Over a WAN, Miniroot Download Time Can Increase Significantly (Bug ID 6543749)

During boot or installation over a wide-area network (WAN), the time it takes to download the miniroot can increase significantly when using a virtual network (vnet) device. Early tests showed miniroot download to be 5 to 6 times slower than similar boots or installations over physical network devices.

This performance degradation appears only when trying to boot or install over a WAN using a virtual network device. Similar boots or installations using a physical network device works as expected, as does a traditional local area network (LAN) boot or installation from a virtual network device.

Emulex-based Fibre Channel Host Adapters Not Supported in Split-PCI Configuration on Sun Fire T1000 Servers (Bug ID 6544004)

The following message appears at the ok prompt if an attempt is made to boot a guest domain that contains Emulex-based Fibre Channel host adapters (Sun Part Number 375-3397):

ok> FATAL:system is not bootable, boot command is disabled

These adapters are not supported in a split-PCI configuration on Sun Fire T1000 servers.

Adding Non-Existent Disk Device to Single-CPU Domain Causes Hang (Bug ID 6544946)

When a guest domain is configured to a virtual disk that is backed by a nonexistent storage device, the domain can hang either during reconfiguration boot or running the devfsadm(1M) command. The error is encountered because the virtual disk driver fails to detach properly following a attach failure.

Workaround: Add more than one CPU to the domain.

Recovery: Unconfigure or replace the nonexistent disk device with a valid disk device and reboot the domain.

Watchdog Timeout Can Be Triggered by Heavy Network Loads (Bug ID 6545470)

A system in which the virtual switch has been configured to use the bge network interface can trigger the watchdog timeout under heavy network load conditions. This often happens when the CPU count in guest domains running network intensive workloads is significantly larger than the number of CPUs in the service domain.

Even though watchdog timeouts do not cause a system to reset, the system does become progressively more nonresponsive. A message similar to the following might also appear on the console:

APR 19 17:05:47 ERROR: Watchdog timeout ignored because user is 
running on a Logical Domains Configuration

If the watchdog message is displayed, or if you want to run network intensive loads in the guest domain, apply the following workaround. However, note that doing so might result in a slight degradation of network performance under certain loads.

Workaround: Set the following in the /etc/system file, and reboot the service domain.

set vsw_chain_len=20

Recovery: Apply the workaround, and power cycle the system.

Do Not Use Control-C From the prtdiag(1M) Command (Bug ID 6552999)

Normally, when the verbose (-v) option is specified to the prtdiag(1M) command in the control domain, additional environmental status information is displayed. If the output of this information is interrupted by issuing a Control-C, the PICL daemon, picld(1M), can enter a state which prevents it from supplying the environmental status information to the prtdiag command from that point on, and the additional environmental data is no longer displayed.

Workaround: Restart the picld(1M) SMF service in the control domain using the following command:

# svcadm restart picl

Some luxadm(1M) Commands Can Fail to Work on Devices That Have Been Assigned to Guest Domain (Bug ID 6553809)

When a Fibre Channel Arbitrated Loop (FC_AL) disk is exported as a virtual disk to another domain, then some luxadm(1M) commands, such as luxadm display, can fail.

An example of the failure of the luxadm display command is:

# luxadm display /dev/rdsk/c1t44d0s2
Error: SCSI failure. - /dev/rdsk/c1t44d0s2.

Workaround: To successfully issue a luxadm(1M) command on a disk exported as a virtual disk to another domain, you must first stop and unbind this other domain.

Do Not Specify a Virtual Switch Interface as a Network Device (Bug ID 6554177)

Do not specify a virtual switch (vsw) interface as the network device for a virtual switch configuration. That is, do not specify a virtual switch interface as the net-dev property for the ldm add-vswitch or ldm set-vswitch commands.

Occasionally, a Network Installation Hangs on a Guest Domain (Bug ID 6555461)

Occasionally, while doing a network installation on a guest domain, the installation begins normally and then hangs after printing the following message on the console:

NFS server <servername> not responding still trying

The guest domain then stops sending and receiving network traffic.

Workaround: Stop the guest domain, restart the guest domain, and restart the network installation.

Occasionally During Solaris OS Reboot, You Can Receive an Unsuccessful Read or Write Message (Bug ID 6560890)

Occasionally during Solaris OS boot, a console message from the Domain Services (ds) module reports that reading or writing from a logical domain channel was unsuccessful. The reason code (131) indicates that the channel has been reset. Below are examples of the console message:

NOTICE: ds@1: ldc_read returned 131
WARNING: ds@0: send_msg: ldc_write failed (131)

Recovery: None. These console messages do not affect the normal operation of the system and can be ignored.

The prtdiag and prtpicl Utilities Do Not Work in Guest Domains (Bug ID 6563508)

The prtpicl(1M) and prtdiag(1M) utilities do not work in a guest domain. Each utility produces the following error message, and neither utility displays any other information:

picl_initialize failed: Daemon not responding

In these situations, the PICL daemon, picld(1M), is in a hung state.

Workarounds: Use one of the following workarounds:

procedure icon  To Disable the PRI Pseudo Driver

  1. Stop the PICL service:

    # svcadm disable picl

  2. Disable the PRI pseudo device driver:

    # rem_drv ds_pri

  3. Re-start the PICL service:

    # svcadm enable picl

Virtual Disk Client Needs an I/O Timeout (Bug ID 6566086)

In a guest domain, if a virtual disk is unreachable because the service domain is down, then any I/O operations to that disk are blocked until the service domain is up and running. As a consequence, any application performing an I/O operation to an unreachable disk is blocked while the service domain is down and no I/O error is ever reported to the application.

Rarely, a Hard Hang Can Occur After Resetting or Rebooting the Control Domain (Bug ID 6567907)

Rarely, when rebooting the control domain of an LDoms system, the operation can hang, requiring a power cycle.


  1. To clear the hang condition, use the powercycle command of the system controller or service processor.

  2. Restart all guest domains that were running at the time of the hang.

  3. Restart all applications that were running in the guest domains.

  4. Recover databases if I/O operations that were in progress in the guest domains did not complete.

  5. Perform any other necessary application-specific recovery operations.

Workaround: None.

Under Certain Circumstances, Reverting to a Configuration Previously Saved on the SC Can Cause the Logical Domains Manager to Crash (Bug ID 6571091)

After reverting to a logical domain configuration previously saved using the ldm add-config command, the Logical Domains Manager might crash with the following error message:

"0L != clientp->published_name".

Workaround: When creating virtual I/O clients and services do not use the canonical names which the Logical Domains Manager applies when there is no match in the constraints database. These names are:

Device Canonical Name Format
vdisk vdiskNN
vnet vnetNN
vsw ldom-name-vswNN
vcc ldom-name-vccNN
vds dom-name-vdsNN
vdsdev ldom-name-vdsNN-volVV

NN and VV refer to monotonically increasing instance numbers.

Virtual Disk Service Should Support Unformatted Disks (Bug ID 6575050)

A physical disk that is unformatted or that does not have a valid disk label, either a Volume Table of Contents (VTOC) or an Extensible Firmware Interface (EFI) label, cannot be exported as a virtual disk to another domain.

Trying to export such a disk as a virtual disk fails when you attempt to bind the domain to which the disk is exported. A message similar to this one is issued and stored in the messages file of the service domain exporting the disk:

vd_setup_vd(): vd_read_vtoc returned errno 22 for /dev/dsk/c1t44d0s2
vds_add_vd(): Failed to add vdisk ID 1

To export a physical disk that is unformatted or that does not have a valid disk label, use the format(1M) command first in the service domain to write a valid disk label (VTOC or EFI) onto the disk to be exported.

Guests Can Lose Access to Virtual Disk Services if I/O Domain Is Rebooted (Bug ID 6575216)

When a service domain is rebooted, guest domains might lose access to virtual disks exported from that service domain. When this happens, the guest domain displays a message similar to the following:

NOTICE: [0] disk access failed

Recovery: To recover from this failure, stop the guest domain (ldm stop-domain) and restart it (ldm start-domain).

Workaround: On the I/O service domain, add the following lines to the /etc/system file:

set vds:vds_dev_delay = 60000000
set vds:vds_dev_retries = 10

After updating the /etc/system file, reboot the I/O service domain for the new settings to be effective.

Some Virtual Disks Do Not Have a Device ID (Bug ID 6578918)

In a guest domain, virtual disks created from a file do not have a device ID (or devid). If such disks are used to stored Solaris Volume Manager metadevice state database (metadb) information, then Solaris Volume Manager issue a message similar to the following during the system boot:

NOTICE: mddb: unable to get devid for ’vdc’, 0xf

Workaround: This message is harmless and can be ignored.

Guest Domain Can Lose Connection to the Virtual Switch When the Service Domain is Rebooted (Bug ID 6581720)

Under certain conditions, after a service domain is rebooted while a guest domain is running, the virtual network (vnet) device on the guest fails to establish a connection with the virtual switch on the service domain. As a result, the guest domain cannot send and receive network packets.

Workarounds: Use one of the following workarounds on the domain with the virtual network:

Some Commands Read Old bootmode Settings (Bug ID 6585340)

Users can change ldom variables in the control domain in one of three ways:

Changes made with the setenv and eeprom commands take effect immediately; changes made with the bootmode command are supposed to take effect on the next reset, no matter what kind of reset it is.

Changes made in any of these three ways are supposed to stay in effect until the next change, also made in any of these three ways. That is, it does not matter how the value of an ldom variable is changed; once changed, the value is supposed to stay in effect until it is changed again.

However, because some commands, such as uadmin 2 0 and reboot, read old bootmode settings, changes made using the bootmode command become effective only after a power-on reset and override any intervening change made using the setenv or eeprom commands on every reset (other than a power-on reset) that follows. That is, the changes made by the bootmode command require a power-on reset to be effective and changes made using the setenv or eeprom commands only persist until the next reset, at which point the variable reverts to the value set by the last bootmode command. This stickiness of the bootmode setting persists until the machine is power cycled. Upon power cycling, the prior bootmode setting does not take effect and any subsequent change using the setenv or eeprom command now persists over resets, at least until the next bootmode command followed by a power cycle.

See also Logical Domain Variable Persistence.

Workarounds: Use one of the following:

Shutting Down the System in Certain Ways Can Result in Two Warnings (Bug ID 6586271)

There are two similar prompts that can appear on the console as part of shutting down the system in certain ways:

  1. You access the telnet prompt, type send brk, and receive the following monitor prompt:

    c)ontinue, s)ync, r)eboot, h)alt?

  2. You enter the halt command at the shell running on the console and receive the following monitor prompt:

    r)eboot, o)k prompt, h)alt?

If you select s for sync or select o for the ok prompt, you can see the following error messages on the console:

WARNING: promif_ldom_setprop: ds response timeout
WARNING: unable to store boot command for use on reboot

Additionally, because of the failure underlying these error messages, unexpected behavior can occur on the next boot, depending on what you selected:

  1. If you selected s for sync:

    If the auto-boot? logical domain variable has the value false, correct behavior for the s selection is to override auto-boot? for the next boot only, and boot immediately into the OS. Instead, the system stops at the ok prompt after the system is reset.

  2. If ou selected o for the ok prompt:

    If the auto-boot? logical domain variable has the value false, correct behavior for the o selection is to override auto-boot? for the next boot only, and stop at the ok prompt. Instead, the system immediately boots the OS.

Workaround: You cannot suppress the error messages when using the above monitor prompts. To achieve reset behavior which differs from the current auto-boot? setting, change the setting to the desired new behavior, reboot, then reset auto-boot? to the previous value.

No Error Message If System Controller Cannot Save Logical Domain Configurations Because of Lack of Space (Bug ID 6587522)

Logical domain configurations might not be saved if the system controller runs out of storage space. There is no error message when this happens.

Workaround: Do the following:

  1. Verify that a configuration is saved by using the ldm list-config command after every ldm add-config command.

  2. If the configuration is not saved, free space by removing a configuration using the ldm remove-config command. Then retry the ldm add-config command.

Do Not Use Non-Numeric Values for Port Numbers in ldm Commands (Bug ID 6590848)

The current behavior for the port number argument to the ldm set-vcons command, as well as the port range arguments to the ldm {add,set}-vcc commands, is to ignore anything starting with a non-numeric value. For example, if the value 0.051 is passed in as the port number for a virtual console, rather than returning an error, the value is interpreted as 0, which tells the Logical Domains Manager to use automatic port allocation.

Workaround: Do not use non-numeric values in port numbers for any ldm commands.

Virtual Disk Server Prints File Lookup Error During Service Domain Boot (Bug ID 6591399)

When a service domain is rebooted while some guest domains are bound, you can see messages similar to these from the virtual disk server:

vd_setup_file(): Cannot lookup file (/export/disk_image_s10u4_b12.1) errno=2
vd_setup_vd(): Cannot use device/file (/export/disk_image_S10u4_b12.1) errno=2

These message indicate that the specified file or device is to be exported to a guest domain, but that this file or device is not ready to be exported yet.

Workaround: These messages are usually harmless and should stop once the service domain has completed its boot sequence. If similar message are printed after the service domain is fully booted, you may want to check whether the specified file or device is accessible from the service domain.

Logical Domains Manager Needs to Retire Resources on a Guest Domain After a Panic and Reboot (Bug ID 6591844)

If a CPU or memory fault occurs, it is possible that the affected domain will panic and reboot. If the Fault Management Architecture (FMA) attempts to retire the faulted component while the domain is rebooting, the Logical Domains Manager is not able to communicate with the domain, and the retire operation fails. In this situation, the fmadm faulty command lists the resource as degraded.

Recovery: Once the domain has completed rebooting, force FMA to replay the fault event by restarting fmd(1M) on the control domain using this command:

primary# svcadm restart fmd

Logical Domains Manager Accepts Multiple Entries of I/O Constraints (Bug ID 6591905)

It is possible to erroneously add duplicate I/O constraints when configuring a logical domain.


  1. Show the duplicate entries by using this command:

    # ldm list -l

  2. Remove the duplicate I/O entries using this command:

    # rm-io bus ldom

The Options: true false Menu Interrupts an OpenBoot PROM Reset (Bug ID 6594395)

The ldm set-variable command allows you to set an LDom variable to any arbitrary string. However, many LDom variables have only a small set of valid values. For example, boolean variables like auto-boot? and diag-switch? only accept the values true or false. If an LDom variable is set to a value that is not valid, the OpenBoot firmware issues a warning message during boot with a list of correct values, but without giving the name of the variable in question. For example:

More [<space>,<cr>,q,n,p,c] ?

The preceding warning is sent by OpenBoot firmware if the auto-boot? variable is set to a NULL string. The boot stops at this point waiting for input. If you enters a space or a carriage return, the complete error message is displayed and the boot process continues:


As a common example, you can receive this error if you omit the = sign when using the ldm set-variable command:

# ldm set-variable auto-boot? true guest_domain

The preceding command actually results in two NULL LDoms variables:


As discussed previously, auto-boot? is a boolean variable and setting it to NULL results in an OpenBoot warning during boot. The proper format for the above command is:

# ldm set-variable auto-boot?=true guest_domain

After a resetsc Command, Changing OpenBoot PROM nvram Parameters Does Not Take Effect (Bug ID 6596594)

If the service processor is reset while the control domain is at the ok prompt, then OpenBoot firmware permanently loses its ability to store non-volatile LDom variables or security keys until the host has been reset. Guest domains are not affected by this problem. Attempts to update LDom variables or security keys result in the following warning messages:

{0} ok setenv auto-boot? false
WARNING: Unable to update LDOM Variable

{0} ok set-security-key wanboot-key 545465
 WARNING: Unable to store Security key

Recovery: Reset the control domain using the reset-all OpenBoot command.

{0} ok reset-all

Console Ports Dynamically Assigned When a Logical Domain Is Bound Become Hard Constraints If the Logical Domains Manager Subsequently Restarts (Bug ID 6596652)

When a logical domain with automatic port selection for the console is bound, the Logical Domains Manager assigns a port for the console. If the Logical Domains Manager is restarted with the logical domain in the bound state, the Logical Domains Manager attempts to re-assign the same port for the logical domain’s console, and the bind can fail if another console is already using the port.

Recovery: You can manually revert to automatic port selection for the console by running the following command before attempting a re-bind:

# ldm set-vcons port= ldom

Removing I/O Buses Followed by Adding CPUs Can Cause the Hypervisor to Stop or the Logical Domains Manager to Dump Core (Bug ID 6597761)

During a single delayed reconfiguration operation, do not attempt to add CPUs to a domain if any were previously removed during the same delayed reconfiguration. Either cancel the existing delayed reconfiguration first, if possible, or commit it by rebooting the target domain, and then add the CPU.

Failure to heed this restriction can, under certain circumstances, lead to the hypervisor returning a parse error to the Logical Domains Manager, resulting in the Logical Domains Manager stopping. Additionally, if any virtual I/O devices had been removed during the same delayed reconfiguration operation, when the Logical Domain Manager restarts, it incorrectly detects the need to perform a recovery operation; thus, creating a corrupt configuration, and leading to the hypervisor stopping and the server powering down.

Environmental Status Output From the prtdiag -v Command Can Be Missing After an SP Warm Reset (Bug ID 6601790)

When the verbose (-v) option is specified to the prtdiag(1M) command in the control domain, additional environmental status information is displayed. If the service processor (SP) is reset while the control domain is running, in some cases, the prtdiag command no longer displays the additional environmental data.

Workaround: Environmental status information can be obtained by using the service processor showenvironment command. Refer to the Integrated Lights Out Management 2.0 (ILOM 2.0) Supplement for Sun SPARC Enterprise T5120 and T5220 Servers for details.

Logical Domains Manager Can Crash If Asked to Report the State of a Logical Domain Immediately After Starting It (Bug ID 6602322)

Sometimes, issuing the following two commands within a few seconds of each other results in the Logical Domains Manager stopping and dumping core:

# ldm start-domain ldom
# ldm ls -l -p ldom
Receive failed: logical domain manager not responding

Recovery: When this occurs, the Logical Domains Manager restarts and recovers automatically. However, the system can be in the state that triggers a stop and core dump for several seconds. Wait a short while, and then attempt the ldm ls -l -p command again.

Guest Domain With More Than Four Virtual Networks on the Same Network Using DHCP Can Become Unresponsive (Bug ID 6603974)

If you configure more than four virtual networks (vnets) in a guest domain on the same network using the Dynamic Host Protocol (DHCP), the guest domain can eventually become unresponsive while running network traffic.

Recovery: Issue an ldm stop-domain ldom command followed by an ldm start-domain ldom command on the guest domain (ldom) in question.

Workaround: Avoid such configurations.

Logical Domains Manager Is Not Accepting Empty Variable Values From the eeprom(1M) Command (Bug ID 6604094)

The eeprom(1M) command cannot be used to reset EEPROM values to null in Logical Domains systems. The following example shows what happens if you attempt this:

primary# eeprom boot-file=
eeprom: OPROMSETOPT: Invalid argument
boot-file: invalid property.

The same command works correctly on non–Logical Domains systems as shown in this example:

# eeprom boot-file=
# eeprom boot-file
boot-file: data not available.

LDoms Issues That Apply Only to Solaris 10 11/06 OS

The following LDoms issues apply only if you have Solaris 10 11/06 OS running on your system.

Removing or Updating a Virtual Switch Can Cause Networking to Fail

Once the virtual switch driver (vswitch) has attached, either as part of the normal Solaris OS boot sequence, or as a result of an explicit Solaris OS add_drv(1M) command, removing or updating the driver can cause networking to fail.

Workaround: Once vswitch has attached, do not remove the driver using the Solaris OS rem_drv(1M) command or update the driver using the Solaris OS update_drv(1M) command.

Recovery: If you do remove the driver using the rem_drv command and then attempt to reattach it using the add_drv command, you must reboot after the add_drv command completes to ensure the networking restarts correctly. Similarly, you must also reboot after an update_drv command completes to ensure the networking does not fail.

Fault Manager Daemon (fmd) Dumps Core When Control Domain Has Only a Single Strand (Bug ID 6604253)

If you are running the Solaris 10 11/06 OS, and you harden drivers on the control (primary) domain that is configured with only one strand, rebooting the primary domain or restarting the Fault Manager daemon, fmd(1M), can result in the fmd dumping core. The fmd dumps cores while it cleans up it resources, and this does not affect the Fault Management Architecture (FMA) diagnosis.

Workaround: Add a few more strands into the primary domain. For example:

# ldm add-vcpu 3 primary

LDoms Bugs Fixed for Solaris 10 8/07 OS

The following LDoms bugs were fixed for the Solaris 10 8/07 OS: