- Book Information
- Preface
- Chapter 1 Logical Domains 1.2 Release Notes
- What's New in This Release
- System Requirements
- Related Software
- Known Issues
- General Issues
- Service Processor and System Controller Are Interchangeable Terms
- Cards Not Supported
- In Certain Conditions, a Guest Domain's SVM Configuration or Metadevices Can Be Lost
- Logical Domain Channels (LDCs) and Logical Domains
- Memory Size Requirements
- Booting a Large Number of Domains
- Cleanly Shutting Down and Power Cycling a Logical Domains System
- Memory Size Requested Might Be Different From Memory Allocated
- Logical Domain Variable Persistence
- Sun SNMP Management Agent Does Not Support Multiple Domains
- The sysfwdownload Utility Takes Significantly Longer to Run While LDoms Is Enabled on Certain Systems
- Containers, Processor Sets, and Pools Are Not Compatible With CPU Power Management
- CPU Power Management Does Not Occur When Any Domain Is in a Transition State
- Fault Management
- Delayed Reconfiguration
- Domain Migration in Elastic Mode Is Not Supported
- Cryptographic Units
- Bugs Affecting LDoms 1.2 Software
- Logical Domains Manager Does Not Validate Disk Paths and Network Devices
- Hang Can Occur With Guest OS in Simultaneous Operations
- Behavior of the ldm stop-domain Command Can Be Confusing
- Cannot Set Security Keys With Logical Domains Running
- Logical Domains Manager Forgets Variable Changes After a Power Cycle
- Using the server-secure.driver With an NIS Enabled System, Whether or Not LDoms Is Enabled
- Network Performance Is Worse in a Logical Domain Guest Than in a Non-LDoms Configuration
- Logical Domain Time-of-Day Changes Do Not Persist Across a Power Cycle of the Host
- OpenBoot PROM Variables Cannot be Modified by the eeprom(1M) Command When the Logical Domains Manager is Running
- Emulex-based Fibre Channel Host Adapter Not Supported in Split-PCI Configuration on Sun Fire T1000 Servers
- Starting and Stopping SunVTS Multiple Times Can Cause Host Console to Become Unusable
- Virtual Disk Timeouts Do Not Work If Guest or Control Domain Is Halted
- Logical Domains Manager Does Not Retire Resources On Guest Domain After a Panic and Reboot
- Guest Domain With Too Many Virtual Networks on the Same Network Using DHCP Can Become Unresponsive
- Fault Manager Daemon Dumps Core On a Hardened, Single Strand Control Domain
- The scadm Command Can Hang Following an SC or SP Reset
- Simultaneous Net-Installation of Multiple Domains Fails When in a Common Console Group
- Sometimes, the prtdiag(1M) Command Does Not List All CPUs
- SVM Volumes Built on Slice 2 Fail JumpStart When Used as the Boot Device in a Guest Domain
- If the Solaris 10 5/08 OS Is Installed on a Service Domain, Attempting a Net Boot of the Solaris 10 8/07 OS on Any Guest Domain Serviced by It Can Hang the Installation
- Cryptographic DR Changes Incompatible With Pre-LDoms Firmware
- Logical Domains Manager Can Take Over 15 Minutes to Shut Down a Logical Domain
- With Elara Copper Card, the Service Domain Hangs on Reboot
- Sometimes, Executing the uadmin 1 0 Command From an LDoms System Does Not Return the System to the OK Prompt
- Logical Domains Manager Displays Migrated Domains in Transition States When They Are Already Booted
- Logical Domains Manager Does Not Start If the Machine Is Not Networked and an NIS Client Is Running
- Newly Configured Virtual Network Fails to Establish a Connection With the Virtual Switch
- Do Not Migrate a Guest Domain That Is at the kmdb Prompt
- Cannot Export a ZFS Volume as a Single-Slice Virtual Disk From Service Domain Running Up to the Solaris 10 5/08 OS to Guest Domain Running Solaris 10 10/08 OS
- Migration Can Fail to Bind Memory Even If the Target Has Enough Available
- Migration Does Not Fail If a vdsdev on the Target Has a Different Backend
- Constraint Database Is Not Synchronized to Saved Configuration
- Explicit Console Group and Port Bindings Are Not Migrated
- Pseudonyms for PCI Buses on Sun SPARC Enterprise T5440 Systems Are Not Correct
- Cancelling Domain Migration With Virtual Networks Using Multiple Virtual Switches Might Cause Domain Reboot
- VIO DR Operations Ignore the Force (-f) Option
- libpiclsnmp:snmp_init() Blocks Indefinitely in open() on primary Domain
- Deadlock Occurs Rarely With CPU DR Operations
- FMA Status Failures
- ldmconfig Might Cause the Root File System of the Control Domain to Become Full and Halt the System
- Guest Domain Sometimes Makes Improper Domain Services Connection to the Control Domain
- Spurious Domain Services Invalid Handle Warning Messages Are Logged to the Console
- ldm: Autosave Feature Should Identify and Allow the Downloading of Damaged Configurations
- Canceling a Pending Delayed Reconfiguration Operation Does Not Discard Changes Made to the Configuration
- Configuration Autorecovery: ldm add-config -r oldcfg newcfg Should Leave oldcfg in Previous State
- Unable to bind memory; limit of 31 segments reached
- ldmd Dumps Core If a rm-io Operation Is Followed by Multiple set-vcpu Operations
- Domain Can Lose CPUs During a Migration If Another Domain Is Rebooting
- Migration Does Not Clean Up a Target If the Virtual Network MAC Address Clashes With an Existing Domain
- Migration Dry-Run Check Should Detect Inadequate Memory
- Virtual Network Devices Are Not Created Properly on the Control Domain
- Configuration Autorecovery: Improve Warning Messages for Broken Autosave Configurations
- Logical Domains Domain Services Module Needs to Support More Than 64 Ports
- Cannot Connect to Migrated Domain's Console Unless vntsd Is Restarted
- I/O Domain or Guest Domain Panics When Booting From e1000g
- ldm stop Reports Timeout Too Soon For Large Domains
- set-vdisk and set-vnet Operations Place Guest Domains in Delayed Reconfiguration Mode
- Guest Domain Might Fail to Successfully Reboot When a System Is in Power Management Elastic Mode
- CPU failed to start Panics Seen on Reboots in Elastic Mode
- ldmd Shows Domain State as transition When the Domain Is Running After a CPU DR Operation
- Possible Issues After a Failed add-vdisk Command
- Reboot Stops at OpenBoot Prompt When Services Cannot Be Initialized
- ldm Commands Are Slow to Respond When Several Domains Are Booting
- Spurious dl_ldc_cb: LDC READ event Message Seen When Rebooting the Control Domain or a Guest Domain
- ldm list -l Causes ldmd to Dump Core After Upgrading From Logical Domains 1.1 to Logical Domains 1.2
- UltraSPARC T2 and UltraSPARC T2 Plus Based Systems: Domain Might Panic When Adding New CPUs
- Documentation Errata
- General Issues
- Resolved Issues