- Book Information
- Preface
- Chapter 1 Logical Domains 1.3 Release Notes
- What's New in This Release
- System Requirements
- Related Software
- Upgrading to LDoms 1.3 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
- Containers, Processor Sets, and Pools Are Not Compatible With CPU Power Management
- Fault Management
- Delayed Reconfiguration
- Domain Migration in Elastic Mode Is Not Supported
- Cryptographic Units
- Bugs Affecting LDoms 1.3 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
- 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
- The scadm Command Can Hang Following an SC or SP Reset
- Simultaneous Net-Installation of Multiple Domains Fails When in a Common Console Group
- 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
- Logical Domains Manager Can Take Over 15 Minutes to Shut Down a Logical Domain
- 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
- 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
- VIO DR Operations Ignore the Force (-f) Option
- libpiclsnmp:snmp_init() Blocks Indefinitely in open() on primary Domain
- FMA Status Failures
- ldmconfig Might Cause the Root File System of the Control Domain to Become Full and Halt the System
- Guest Domain Sometimes Fails to Make Proper Domain Services Connection to the Control Domain
- ldm: Autosave Feature Should Identify and Allow the Downloading of Damaged Configurations
- ldmd Dumps Core If a rm-io Operation Is Followed by Multiple set-vcpu Operations
- Virtual Network Devices Are Not Created Properly on the Control Domain
- Cannot Connect to Migrated Domain's Console Unless vntsd Is Restarted
- I/O Domain or Guest Domain Panics When Booting From e1000g
- Guest Domain Might Fail to Successfully Reboot When a System Is in Power Management Elastic Mode
- ldm Commands Are Slow to Respond When Several Domains Are Booting
- Spurious ds_ldc_cb: LDC READ event Message Seen When Rebooting the Control Domain or a Guest Domain
- Migrated Domain With MAUs Contains Only One CPU When Target OS Does Not Support DR of Cryptographic Units
- ldm set-vcc Prevented When System Is Already in Delayed Reconfiguration Mode
- Confusing Migration Failure Message for Real Address Memory Bind Failures
- An Enabled Resource Managment Policy Might Not Decrease CPU Count As Expected
- ldm Does Not Make Use of Cryptographic Units Added to the Control Domain After Startup
- Warm Migration Can Fail With an Unknown migration failure Message
- DRM: Some tod-begin and tod-end Values Cannot Begin With a Leading Zero
- Newly Added NIU/XAUI Adapters Are Not Visible to Host OS If Logical Domains Is Configured
- Dynamically Removing All the Cryptographic Units From a Domain Causes SSH to Terminate
- Unexpected Probe-Based IPMP Failures
- Documentation Errata
- General Issues
- Resolved Issues