| Skip Navigation Links | |
| Exit Print View | |
|
Oracle VM Server for SPARC 3.0 Administration Guide Oracle VM Server for SPARC |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle VM Server for SPARC 3.0 Administration Guide Oracle VM Server for SPARC |
Part I Oracle VM Server for SPARC 3.0 Software
1. Overview of the Oracle VM Server for SPARC Software
2. Installing and Enabling Software
3. Oracle VM Server for SPARC Security
4. Setting Up Services and the Control Domain
11. Managing Domain Configurations
12. Performing Other Administration Tasks
File Names (file) and Variable Names (var-name)
Virtual Disk Server backend and Virtual Switch Device Names
Configuration Name (config-name)
Connecting to a Guest Console Over a Network
How to Combine Multiple Consoles Into One Group
Operating the Oracle Solaris OS With Oracle VM Server for SPARC
OpenBoot Firmware Not Available After Oracle Solaris OS Has Started
Performing a Power Cycle of a Server
How to Save Your Current Domain Configurations to the SP
Do Not Use the psradm(1M) Command on Active CPUs in a Power-Managed Domain
Result of Oracle Solaris OS Breaks
Results From Halting or Rebooting the Control Domain
Using Logical Domains With the Service Processor
How to Reset the Domain Configuration to the Default or Another Configuration
Configuring Domain Dependencies
Determining Where Errors Occur by Mapping CPU and Memory Addresses
How to Determine the CPU Number
How to Determine the Real Memory Address
Examples of CPU and Memory Mapping
Using Universally Unique Identifiers
Virtual Domain Information Command and API
Part II Optional Oracle VM Server for SPARC Software
13. Oracle VM Server for SPARC Physical-to-Virtual Conversion Tool
14. Oracle VM Server for SPARC Configuration Assistant (Oracle Solaris 10)
16. Using the Oracle VM Server for SPARC Management Information Base Software
17. Logical Domains Manager Discovery
18. Using the XML Interface With the Logical Domains Manager
An ldm stop-domain command can time out before the domain completes shutting down. When this happens, an error similar to the following is returned by the Logical Domains Manager.
LDom ldg8 stop notification failed
However, the domain could still be processing the shutdown request. Use the ldm list-domain command to verify the status of the domain. For example:
# ldm list-domain ldg8 NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME ldg8 active s---- 5000 22 3328M 0.3% 1d 14h 31m
The preceding list shows the domain as active, but the s flag indicates that the domain is in the process of stopping. This should be a transitory state.
The following example shows the domain has now stopped.
# ldm list-domain ldg8 NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME ldg8 bound ----- 5000 22 3328M
Note - Starting with the Oracle VM Server for SPARC 3.0 release, the ldm stop command uses the shutdown command to stop a domain. The execution of the shutdown sequence usually takes much longer than a quick stop, which can be performed by running the ldm stop -q command. See the ldm(1M) man page.
A long shutdown sequence might generate the following timeout message:
domain-name stop timed out. The domain might still be in the process of shutting down. Either let it continue, or specify -f to force it to stop.
While this shutdown sequence runs, the s flag is also shown for the domain.
|