Part I Oracle VM Server for SPARC 3.1 Software
Part II Optional Oracle VM Server for SPARC Software
Chapter 14 Oracle VM Server for SPARC Physical-to-Virtual Conversion Tool
Oracle VM Server for SPARC P2V Tool Overview
Installing the Oracle VM Server for SPARC P2V Tool
Prerequisites for using the SPARC P2V Tool
Limitations of Using the SPARC P2V Tool
How to Install the Oracle VM Server for SPARC P2V Tool
Chapter 15 Oracle VM Server for SPARC Configuration Assistant (Oracle Solaris 10)
Using the Configuration Assistant (ldmconfig)
Installing the Configuration Assistant
Prerequisites for Running the Configuration Assistant
Limitations and Known Issues of the Configuration Assistant
Chapter 16 Using Power Management
Viewing Power-Consumption Data
Chapter 17 Using the Oracle VM Server for SPARC Management Information Base Software
Oracle VM Server for SPARC Management Information Base Overview
Logical Domains Manager and the Oracle VM Server for SPARC MIB
Parsing the XML-Based Control Interface
Providing Fault and Recovery Information
Oracle VM Server for SPARC MIB Object Tree
Installing and Configuring the Oracle VM Server for SPARC MIB Software
Installing and Configuring the Oracle VM Server for SPARC MIB Software
How to Install the Oracle VM Server for SPARC MIB Software Package
How to Load the Oracle VM Server for SPARC MIB Module Into the Oracle Solaris SNMP Agent
How to Remove the Oracle VM Server for SPARC MIB Software Package
How to Create the Initial snmpv3 User
Querying the Oracle VM Server for SPARC MIB
Retrieving Oracle VM Server for SPARC MIB Information
Environment Variables Table (ldomEnvVarsTable)
Domain Policy Table (ldomPolicyTable)
Service Processor Configuration Table (ldomSPConfigTable)
Domain Resource Pool and Scalar Variables
Virtual CPU Table (ldomVcpuTable)
Virtual Memory Table (ldomVmemTable)
Virtual Memory Physical Binding Table (ldomVmemPhysBindTable)
Virtual Disk Service Table (ldomVdsTable)
Virtual Disk Service Device Table (ldomVdsdevTable)
Virtual Disk Table (ldomVdiskTable)
Virtual Switch Service Table (ldomVswTable)
Virtual Network Device Table (ldomVnetTable)
Virtual Console Concentrator Table (ldomVccTable)
Virtual Console Group Table (ldomVconsTable)
Virtual Console Relationship Table (ldomVconsVccRelTable)
Cryptographic Units Table (ldomCryptoTable)
I/O Bus Table (ldomIOBusTable)
Scalar Variables for Domain Version Information
Using Oracle VM Server for SPARC MIB Module Traps
Oracle VM Server for SPARC MIB Trap Descriptions
Domain State Change (ldomStateChange)
Virtual CPU Change (ldomVCpuChange)
Virtual Memory Change (ldomVMemChange)
Virtual Disk Service Change (ldomVdsChange)
Virtual Disk Change (ldomVdiskChange)
Virtual Switch Change (ldomVswChange)
Virtual Network Change (ldomVnetChange)
Virtual Console Concentrator Change (ldomVccChange)
Virtual Console Group Change (ldomVconsChange)
Chapter 18 Logical Domains Manager Discovery
Discovering Systems Running the Logical Domains Manager
How to Discover Logical Domains Managers Running on Your Subnet
Chapter 19 Using the XML Interface With the Logical Domains Manager
Registration and Unregistration
Logical Domains Manager Actions
Logical Domains Manager Resources and Properties
Domain Information (ldom_info) Resource
Virtual Disk Server (vds) Resource
Virtual Disk Server Volume (vds_volume) Resource
Virtual Console Concentrator (vcc) Resource
Physical I/O Device (physio_device) Resource
SP Configuration (spconfig) Resource
DRM Policy Configuration (policy) Resource
Virtual Data Plane Channel Service (vdpcs) Resource
You can subscribe to the following event types:
Domain events
Hardware events
Progress events
Resource events
All the events correspond to ldm subcommands.
Domain events describe which actions can be performed directly to a domain. The following domain events can be specified in the <action> tag in the <LDM_event> message:
add-domain
bind-domain
domain-reset
migrate-domain
panic-domain
remove-domain
start-domain
stop-domain
unbind-domain
These events always contain only a <Content> tag in the OVF <data> section that describes the domain to which the event happened. To register for the domain events, send an <LDM_interface> message with the <action> tag set to reg-domain-events. To unregister for these events, send an <LDM_interface> message with the <action> tag set to unreg-domain-events.
Hardware events pertain to changing the physical system hardware. In the case of Oracle VM Server for SPARC software, the only hardware changes are those to the service processor (SP) when you add, remove, or set an SP configuration. Currently, the only three events of this type are:
add-spconfig
set-spconfig
remove-spconfig
The hardware events always contain only a <Section> tag in the OVF <data> section which describes which SP configuration to which the event is happening. To register for these events, send an <LDM_interface> message with the <action> tag set to reg-hardware-events. To unregister for these events, send an <LDM_interface> message with the <action> tag set to unreg-hardware-events.
Progress events are issued for long-running commands, such as a domain migration. These events report the amount of progress that has been made during the life of the command. At this time, only the migration-process event is reported.
Progress events always contain only a <Section> tag in the OVF <data> section that describes the SP configuration affected by the event. To register for these events, send an <LDM_interface> message with the <action> tag set to reg-hardware-events. To unregister for these events, send an <LDM_interface> message with the <action> tag set to unreg-hardware-events.
The <data> section of a progress event consists of a <content> section that describes the affected domain. This <content> section uses an ldom_info <Section> tag to update progress. The following generic properties are shown in the ldom_info section:
--progress – Percentage of the progress made by the command
--status – Command status, which can be one of ongoing, failed, or done
--source – Machine that is reporting the progress
Resource events occur when resources are added, removed, or changed in any domain. The <data> section for some of these events contains the <Content> tag with a <Section> tag providing a service name in the OVF <data> section.
The following events can be specified in the <action> tag in the <LDM_event> message:
add-vdiskserverdevice
remove-vdiskserverdevice
set-vdiskserverdevice
remove-vdiskserver
set-vconscon
remove-vconscon
set-vswitch
remove-vswitch
remove-vdpcs
The following resource events always contain only the <Content> tag in the OVF <data> section that describes the domain to which the event happened:
add-vcpu
add-crypto
add-memory
add-io
add-variable
add-vconscon
add-vdisk
add-vdiskserver
add-vnet
add-vswitch
add-vdpcs
add-vdpcc
set-vcpu
set-crypto
set-memory
set-variable
set-vnet
set-vconsole
set-vdisk
remove-vcpu
remove-crypto
remove-memory
remove-io
remove-variable
remove-vdisk
remove-vnet
remove-vdpcc
To register for the resource events, send an <LDM_interface> message with the <action> tag set to reg-resource-events. Unregistering for these events requires an <LDM_interface> message with the <action> tag set to unreg-resource-events.
You can also register to listen for all three type of events without having to register for each one individually. To register for all three types of events simultaneously, send an <LDM_interface> message with the <action> tag set to reg-all-events. Unregistering for these events require an <LDM_interface> message with the <action> tag set to unreg-all-events.