Skip Navigation Links | |
Exit Print View | |
Oracle VM Server for SPARC 2.1 Release Notes Oracle VM Server for SPARC |
1. Oracle VM Server for SPARC 2.1 Release Notes
Required and Recommended Oracle Solaris OS
Required Software to Enable Oracle VM Server for SPARC 2.1 Features
Required and Recommended System Firmware Patches
Minimum Version of Software Required
Direct I/O Hardware and Software Requirements
Live Domain Migration Requirements
Location of Oracle VM Server for SPARC 2.1 Software
Software That Can Be Used With the Logical Domains Manager
System Controller Software That Interacts With Logical Domains Software
Upgrading to Oracle VM Server for SPARC 2.1 Software
I/O MMU Bypass Mode Is No Longer Needed
Service Processor and System Controller Are Interchangeable Terms
Logical Domain Channels and Logical Domains
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 Domains Variable Persistence
Oracle's Sun SNMP Management Agent Does Not Support Multiple Domains
Containers, Processor Sets, and Pools Are Not Compatible With CPU Power Management
ldmp2v convert Command: VxVM Warning Messages During Boot
Extended Mapin Space Is Only Available in the Oracle Solaris 10 8/11 OS and Oracle Solaris 11 OS
Graphical Configuration Assistant Tool Has Been Removed
Upgrade Option Not Presented When Using ldmp2v prepare -R
Block of Dynamically Added Memory Can Be Dynamically Removed Only as a Whole
ldmp2v Command: ufsdump Archiving Method Is No Longer Used
Version Restrictions for Migration
CPU Restrictions for Migration
Oracle VM Server for SPARC MIB Issues
Incorrect ldomCryptoRpReserved Property Value
The snmptable Command Does Not Work With the Version 2 or Version 3 Option
Bugs Affecting the Oracle VM Server for SPARC 2.1 Software
init-system Does Not Restore Named Core Constraints for Guest Domains From Saved XML Files
Named Cores Can Power Off All CPUs When in Bind Mode
Partial Core primary Fails to Permit Whole-Core DR Transitions
ldmconfig Is Only Supported on Oracle Solaris 10 Systems
Oracle VM Server for SPARC MIB Is Only Supported on Oracle Solaris 10 Systems
Removing a Large Number of CPUs From a Guest Domain
CPU Threading Mode Is Not Restored After a Domain Migration Is Canceled
A Large-Memory Domain in Elastic Mode Might Take a Long Time to Stop
Cannot Use Solaris Hot Plug Operations to Hot Remove a PCIe Endpoint Device
install-ldm Hangs When Run By Using an Absolute Path From Another Directory
ldm add-dev Can Create a Device Alias That is Longer Than Supported by OpenBoot
Virtual Disk Validation Fails for a Physical Disk With No Slice 2
When incoming_migration_enabled=false, Outgoing Migrations Fail
Do Not Use the Sun Management Console Software to Monitor an Oracle VM Server for SPARC System
Incorrect SP Configuration Is Used as the Default
All ldm Commands Hang When Migrations Have Missing Shared NFS Resources
ldmd Fails to Remove Cores From a Domain That Has Partial Cores
Incorrect Return Status for a Failed CPU DR Operation on a Domain Booted in Single User Mode
Logical Domains Agent Service Does Not Come Online if the System Log Service Does Not Come Online
Kernel Deadlock Causes Machine Hang During a Migration
Virtual CPU Timeout Failures During DR
Domain Bind Fails When XML File Has an Invalid Network or Disk Back End
Migration Failure Reason Not Reported When the System MAC Address Clashes With Another MAC Address
Simultaneous Migration Operations in "Opposite Direction" Might Cause ldm to Hang
Removing a Large Number of CPUs From the Control Domain
SPARC T3: Oracle VM Server for SPARC Hangs When Performing Memory Operations
System That Has the Elastic Policy Set and Is Running the Oracle Solaris 10 8/11 OS Might Hang
pkgadd Fails to Set ACL Entries on /var/svc/manifest/platform/sun4v/ldmd.xml
SPARC T3-1: Detect And Handle Disks That Are Accessible Through Multiple Direct I/O Paths
ldmd Falsely Reports 100% CPU Utilization on a Domain
Guest Domains Cannot Boot From an Exported DVD Device
Cryptographic Units Cannot Be Removed From the primary Domain
An In-Use MAC Address Can be Reassigned
ldmconfig Cannot Create a Domain Configuration on the SP
Uncooperative Oracle Solaris Domain Migration Can Be Blocked If cpu0 Is Offline
Memory DR Is Disabled Following a Canceled Migration
Dynamic Reconfiguration of MTU Values of Virtual Network Devices Sometimes Fails
Memory DR Is Not Supported With Some Physical Memory Configurations
Confusing Migration Failure Message for Real Address Memory Bind Failures
Dynamically Removing All the Cryptographic Units From a Domain Causes SSH to Terminate
Atlas PCI Express Dual 10-Gigabit Ethernet Fiber Card Shows Four Subdevices in ldm list-io -l Output
ldm Commands Are Slow to Respond When Several Domains Are Booting
Guest Domain Might Fail to Successfully Reboot When a System Is in Power Management Elastic Mode
Spurious ds_ldc_cb: LDC READ event Message Seen When Rebooting the Control Domain or a Guest Domain
Guest Domain Sometimes Fails to Make Proper Domain Services Connection to the Control Domain
Virtual Network Devices Are Not Created Properly on the Control Domain
Newly Added NIU/XAUI Adapters Are Not Visible to Host OS If Logical Domains Is Configured
I/O Domain or Guest Domain Panics When Booting From e1000g
Explicit Console Group and Port Bindings Are Not Migrated
Constraint Database Is Not Synchronized to Saved Configuration
Migration Does Not Fail If a vdsdev on the Target Has a Different Back End
Migration Can Fail to Bind Memory Even If the Target Has Enough Available
Logical Domains Manager Does Not Start If the Machine Is Not Networked and an NIS Client Is Running
Logical Domains Manager Displays Migrated Domains in Transition States When They Are Already Booted
Cannot Connect to Migrated Domain's Console Unless vntsd Is Restarted
Logical Domains Manager Can Take Over 15 Minutes to Shut Down a Domain
Simultaneous Net-Installation of Multiple Domains Fails When in a Common Console Group
The scadm Command Can Hang Following an SC or SP Reset
ldc_close: (0xb) unregister failed, 11 Warning Messages
Guest Domain With Too Many Virtual Networks on the Same Network Using DHCP Can Become Unresponsive
Logical Domains Manager Does Not Retire Resources On Guest Domain After a Panic and Reboot
Cannot Set Security Keys With Logical Domains Running
Behavior of the ldm stop-domain Command Can Be Confusing
Hang Can Occur With Guest OS in Simultaneous Operations
Sometimes DR Requests Fail to Remove All Requested CPUs
Incorrect Cross Reference to Required Software Information
ldm stop Command Description Is Misleading
Logical Domains Manager Package Name Incorrect in Upgrade Procedure
ILOM load Command Synopsis Uses Incorrect Character
Oracle VM Server for SPARC 2.1 RFEs and Bugs Fixed in Oracle Solaris 10 8/11 OS
RFEs and Bugs Fixed for Oracle VM Server for SPARC 2.1 Software
RFEs and Bugs Fixed for Oracle VM Server for SPARC 2.1 Software Patch
The domain manager automatically selects the physical resources to be assigned to a domain. You can also explicitly choose the physical resources to assign to a domain. Other than for the control domain, this capability is available when the domain runs the Oracle Solaris 10 or Oracle Solaris 11 OS on any platform that supports the Oracle VM Server for SPARC 2.1 software. For the control domain, this capability is only available when it runs the Oracle Solaris 11 OS.
Note - This capability is only available with the Oracle Solaris 11 SRU 4.
Resources that you explicitly assign are called named resources. Resources that are automatically assigned are called anonymous resources.
Caution - The capability to assign named resources is intended to be used only by expert administrators as it requires careful planning to use. |
You can explicitly assign physical resources to the control domain and to guest domains. Because the control domain remains active, it might optionally be in delayed reconfiguration mode before you make physical resource assignments. Or, delayed reconfiguration mode is automatically triggered when you make physical assignments. See Managing Physical Resources on the Control Domain. For information about physical resource restrictions, see Restrictions for Managing Physical Resources on Domains.
You can explicitly assign the following physical resources to the control domain and to guest domains:
Physical CPUs. Assign the physical core IDs to the domain by setting the cid property. You can set this property by running the following commands:
# ldm add-core cid=core-ID[,core-ID[,...]] ldom # ldm set-core cid=core-ID[,core-ID[,...]] ldom # ldm rm-core [-f] cid=core-ID[,core-ID[,...]] ldom
If you specify a core ID as the value of the cid property, core-ID is explicitly assigned to or removed from the domain.
Physical memory. Assign a set of contiguous physical memory regions to a domain by setting the mblock property. Each physical memory region is specified as a physical memory starting address and as a size. You can set this property by running the following commands:
# ldm add-mem mblock=PA-start:size[,PA-start:size[,...]] ldom # ldm set-mem mblock=PA-start:size[,PA-start:size[,...]] ldom # ldm rm-mem mblock=PA-start:size[,PA-start:size[,...]] ldom
To assign a memory block to or remove it from a domain, set the mblock property. A valid value includes a physical memory starting address (PA-start) and a memory block size (size) separated by a colon character (:).
Note - You cannot use dynamic reconfiguration (DR) to move memory or core resources between running domains when you set the mblock or cid property, respectively. To move resources between domains, ensure that the domains are in a bound or unbound state. For information about managing physical resources on the control domain, see Managing Physical Resources on the Control Domain.
You can use the ldm list-constraints command to view the resource constraints for domains. The physical-bindings constraint specifies which resource types have been physically assigned to a domain. When a domain is created, the physical-bindings constraint is unset until a physical resource is assigned to that domain. By setting the mblock property, the physical-bindings constraint is set to memory. Likewise, by setting the cid property, the physical-bindings constraint is set to core. If both the cid and mblock properties are set, the physical-bindings constraint is set to core,memory.
To change the physical-bindings constraint for a resource type on the control domain, you must first remove all resources of that type by setting the number of resources to zero. Use one of the following methods:
Set the number of resources to 0 by using the ldm set-core 0 or ldm set-mem 0 command.
Remove all of the specified physical-bindings constraints for a particular resource type.
To remove all named cores and memory blocks, run the ldm set-core cid= and ldm set-mem mblock= commands, respectively. To remove all anonymous cores and memory blocks, run the ldm set-core 0 and ldm set-mem 0 commands, respectively.
Because the control domain must have CPUs and memory allocated, specifying cid= or mblock= on the control domain returns an error.
Delete each resource from the domain individually.
If you use the ldm add-mem or ldm set-mem command to assign multiple physical memory blocks, the addresses and sizes are checked immediately. Also, a domain that has partial cores assigned to it can use the whole-core semantics only if the remaining CPUs of those cores are free and available.
Because the control domain is always active, it might optionally be in delayed reconfiguration mode before you make physical resource assignments. When you explicitly assign physical resources, the control domain is automatically placed in delayed reconfiguration mode and the physical-bindings constraint is set.
If physical-bindings=core, running the ldm set-core cid=core-ID primary command or the ldm set-vcpu CPU-count primary command causes the physical-bindings constraint to be cleared on the next reboot. If the physical-bindings constraint is not set to core, run the ldm set-core cid=core-ID primary command to set physical-bindings=core on the next reboot.
If physical-bindings=memory, running the ldm set-mem size primary command causes the physical-bindings constraint to be cleared on the next reboot. If the physical-bindings constraint is not set to memory, run the ldm set-mem mblock=PA-start:size primary command to set the physical-bindings constraint on the next reboot.
Note - When the control domain is in delayed reconfiguration mode, you can perform unlimited memory assignments by using the ldm add-mem and ldm rm-mem commands on the control domain. However, you can perform only one core assignment to the control domain by using the ldm set-core command.
The following restrictions apply to the assignment of physical resources on domains:
You cannot make physical and non-physical memory bindings or physical and non-physical core bindings in the same domain. However, you can have non-physical memory and physical core bindings or non-physical core and physical memory bindings in the same domain.
When you add a physical resource to a domain, the corresponding resource type becomes constrained as a physical binding.
Attempts to add individual CPUs to or remove them from a domain where physical-bindings=core will fail.
For unbound resources, the allocation and checking of the resources can only occur when you run the ldm bind command.
When removing physical memory from a domain, you must remove the exact physical memory block that was previously added.
Physical memory ranges must not overlap.
You cannot use the ldm add-vcpu -c or ldm set-vcpu -c command to assign a physical resource to a domain.