JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle VM Server for SPARC 2.0 Administration Guide
search filter icon
search icon

Document Information


1.  Overview of the Oracle VM Server for SPARC Software

2.  Installing and Enabling Software

3.  Security

4.  Setting Up Services and the Control Domain

5.  Setting Up Guest Domains

6.  Setting Up I/O Domains

7.  Using Virtual Disks

8.  Using Virtual Networks

9.  Migrating Domains

10.  Managing Resources

11.  Managing Configurations

12.  Performing Other Administration Tasks

Entering Names in the CLI

File Names (file) and Variable Names (var-name)

Virtual Disk Server backend and Virtual Switch Device Names

Configuration Name (config-name)

All Other Names

Connecting to a Guest Console Over a Network

Using Console Groups

Combine Multiple Consoles Into One Group

Stopping a Heavily Loaded Domain Can Time Out

Operating the Oracle Solaris OS With Oracle VM Server for SPARC

OpenBoot Firmware Not Available After Oracle Solaris OS Has Started

Powercycling a Server

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

Reset the Domain Configuration to the Default or Another Configuration

Configuring Domain Dependencies

Domain Dependency Examples

Dependency Cycles

Determining Where Errors Occur by Mapping CPU and Memory Addresses

CPU Mapping

Determine the CPU Number

Memory Mapping

Determine the Real Memory Address

Examples of CPU and Memory Mapping

Using Universally Unique Identifiers

Virtual Domain Information Command and API

A.  Oracle VM Server for SPARC Physical-to-Virtual Conversion Tool

B.  Oracle VM Server for SPARC Configuration Assistant

C.  Logical Domains Manager Discovery

D.  Using the XML Interface With the Logical Domains Manager

E.  Logical Domains Manager XML Schemas



Stopping a Heavily Loaded Domain Can Time Out

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
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
ldg8         bound   -----  5000   22   3328M