What's New in Logical Domains Software

This page includes the list of major features introduced in each of the following releases of the Logical Domains software:

  • Logical Domains 1.2
  • Logical Domains 1.1
  • Logical Domains 1.0.3
  • Logical Domains 1.0.2
  • Logical Domains 1.0.1
  • Logical Domains 1.0

Logical Domains 1.2

For information about the hardware and software requirements for the Logical Domains 1.2 release, see the Logical Domains 1.2 Release Notes.

Logical Domains 1.1

For information about the hardware and software requirements for the Logical Domains 1.1 release, see the Logical Domains (LDoms) 1.1 Release Notes.

  • Extensible Markup Language (XML) version 3 (v3) public interface for monitoring and controlling logical domains. This feature is described in Chapter 10 of the Logical Domains (LDoms) 1.1 Administration Guide and provides the following:
    • Access using the Extensible Messaging and Presence Protocol (XMPP)
    • Local raw access with no authentication
    • Logical Domains Manager interface and Logical Domains Manager events
  • Guest Domain Migration provides the capability to migrate a guest logical domain from one server to another compatible server. If active, the domain on the source server is suspended, and its configuration and run-time state are transferred to another server, where the domain is recreated and resumed. Inactive and bound domains can also be migrated, and this happens almost instantaneously as only the domain's configuration needs to be transferred and recreated. See Chapter 8, "Migrating Logical Domains" in the Logical Domains (LDoms) 1.1 Administration Guide.
  • Virtual Input/Output (I/O) Dynamic Reconfiguration (DR) provides the ability to add and remove virtual I/O services and devices without rebooting.
  • Network
    • Network Interface Unit (NIU) Hybrid I/O provides support for a virtualized I/O path, a hybrid I/O path, and better performance and scalability. See "Using NIU Hybrid I/O" in the Logical Domains (LDoms) 1.1 Administration Guide.
    • VLAN Support provides the capability to configure and use virtual local area networks (VLANs) in logical domains. See "Using VLAN Tagging With Logical Domains Software" in the Logical Domains (LDoms) 1.1 Administration Guide. Note that Logical Domains 1.1 software and Solaris(tm) 10 10/08 OS must use this feature. Tagged VLANs are not supported in any of the previous releases for LDoms networking components.
  • Storage
    • Virtual Disk Failover adds support for disk multipathing, which enables the virtual disk device in a guest domain to be serviced by multiple virtual disk servers. See "Configuring Virtual Disk Multipathing" in the Logical Domains (LDoms) 1.1 Administration Guide.
    • Single-Slice Disk Enhancement allows installing the Solaris OS on a single-slice disk. Single-slice disks are now visible with the format(1M) command.
  • New and Changed CLI ldm Subcommands. See the ldm(1M) man page in the Logical Domains (LDoms) Manager 1.1 Man Page Guide.
    • Use the new list subcommand output (-o format) options to limit the output format to one or more of the following subsets: console, cpu, crypto, disk, domain, memory, network, physio, serial, and status.
    • Use new arguments to the add-vnet and set-vnet subcommands to specify details for hybrid I/O (mode=hybrid).
    • Use new arguments to the add-vsw, set-vsw, add-vnet, and set-vnet subcommands to specify VLAN tagging (port VLAN ID and VLAN ID).
    • Use the new mpgroup= argument to the add-vdsdev and set-vdsdev subcommands to define a multipath group name for several virtual disk server devices (vdsdev). In case a virtual disk cannot communicate with a virtual disk server device, a failover is initiated to one of the other virtual disk server devices in the multipath group.
      o 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.
    • Use the ldm migrate-domain command to migrate a logical domain from one machine to another.
    • Output of ldm ls-config has changed so that the annotations more accurately reflect when a configuration saved to the service processor (SP) matches the currently running configuration. See "Output of the ldm ls-config Command Changed" in the Logical Domains 1.1 Release Notes.
  • CPU Power Management (PM) implements power saving by disabling each Sun UltraSPARC® T2-- and T2 Plus--based Server core that has all of its CPU strands idle. See "Using CPU Power Management With LDoms 1.1 Software" in the Logical Domains (LDoms) 1.1 Administration Guide. To use CPU power management, your system must have the firmware that supports power management.

Logical Domains 1.0.3

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.

  • Added DVD boot support. See Chapter 5 in the Logical Domains (LDoms) 1.0.3 Administration Guide.
  • Added support for the format(1M) command and unformatted disks. See Chapter 5 in the Logical Domains (LDoms) 1.0.3 Administration Guide.
  • Added support for multihost disks.
  • Added device ID (DevID) for disk images.
  • Added support to use physical trunk devices for external connectivity.
  • Enabled statistics reporting using the interrupt statistics command, intrstat(1M).
  • Improved Volume Manager support – You can now export a volume as a full disk and install on it.
  • Added timeout= argument for virtual disks to ldm add-vdisk command. Added set-vdisk subcommand to set timeout= or volume= arguments for a virtual disk. See the ldm(1M) man page or Chapter 5 of the Logical Domains (LDoms) 1.0.3 Administration Guide.
  • Added options= argument to ldm add-vdsdev command to specify slice (slice), exclusive (excl), or read-only (ro) options. Added set-vdsdev subcommand to set options for a virtual disk server. See the ldm(1M) man page or Chapter 5 of the Logical Domains (LDoms) 1.0.3 Administration Guide.
  • Added support for Solaris Cluster software on a guest domain. See "Software That Can Be Used With the Logical Domains Manager" in the Logical Domains 1.0.3 Release Notes.
  • Conformed the XML format produced by the ldm ls-constraints -x command to the new version 3 (v3) specification. The LDoms Manager continues to accept the version (v2) format XML files produced by previous versions of the ls-constraints -x subcommand, but it produces the new version only on output.

Logical Domains 1.0.2

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.

  • Sun SPARC® Enterprise T5140 and T5240 Servers
  • Up to 64 domains on Sun UltraSPARC® T2 processors
  • Up to 128 domains on Sun UltraSPARC T2 Plus processors

Logical Domains 1.0.1

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.

  • Sun Blade(tm) T6320 Server Module
  • Netra(tm) CP3260 Blade
  • Netra T5220 Server
  • Sun SPARC® Enterprise T5120 and T5220 Servers plus the Network Interface Unit (NIU)
  • Sun Multithreaded 10GbE card (nxge driver)
  • Forced stop on an I/O service domain
  • I/O domain reset
  • Logical Domains (LDoms) Management Information Base (MIB) 1.0.1 software – See the Logical Domains (LDoms) MIB 1.0.1 Administration Guide.
  • Logical domains minimization – See "Minimizing Logical Domains" in the Logical Domains (LDoms) 1.0.1 Administration Guide.
  • XML input and output enhancements for certain ldm commands and for the LDoms MIB.

Logical Domains 1.0

For information about the hardware and software requirements for the Logical Domains 1.0 release, see the Logical Domains (LDoms) 1.0 Release Notes.

  • Sun Fire(tm) or SPARC® Enterprise T1000 Server - See the Sun Fire or SPARC Enterprise T1000 Server Administration Guide.
  • Sun Fire or SPARC Enterprise T2000 Server - See the Sun Fire or SPARC Enterprise T1000 Server Administration Guide.
  • Netra T2000 Server - See the Netra T2000 Server Administration Guide.
  • Netra CP3060 Blade - See the Netra CP3060 Board Product Notes.
  • Sun Blade T6300 Server Module - See the Sun Blade T6300 Server Module Administration Guide.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Sun Microsystems community and they might not be employed or in any way formally affiliated with Sun Microsystems. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Sun nor any other party necessarily agrees with them.

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact