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 create virtual disks for a guest domain on a number of back-end types: files (file), ZFS volumes (zvol), physical disks or LUNs (disk), or volume manager volumes (disk). The ldmp2v command automatically creates files or ZFS volumes of the appropriate size if you specify file or zvol as the back-end type in one of the following ways:
By using the –b option
By specifying the value of the BACKEND_TYPE parameter in the /etc/ldmp2v.conf file
The disk back-end type enables you to use a physical disk, LUN, or volume manager volume (Oracle Solaris Volume Manager and Veritas Volume Manager (VxVM)) as a back-end device for virtual disks. You must create the disk or volume with an appropriate size prior to beginning the prepare phase. For a physical disk or LUN, specify the back-end device as slice 2 of the block or character device of the disk, such as /dev/dsk/c0t3d0s2. For a volume manager volume, specify the block or character device for the volume, such as /dev/md/dsk/d100 for Oracle Solaris Volume Manager or /dev/vx/dsk/ldomdg/vol1 for VxVM.
Unless you specify the volume and virtual disk names with the –B backend:volume:vdisk option, the volumes and virtual disks that you create for the guest are given default names.
backend specifies the name of the back end to use. You must specify backend for the disk back-end type. backend is optional for the file and zvol back-end types, and can be used to set a non-default name for the file or ZFS volume that ldmp2v creates. The default name is $BACKEND_PREFIX/guest-name/diskN.
volume is optional for all back-end types and specifies the name of the virtual disk server volume to create for the guest domain. If not specified, volume is guest-name-volN.
vdisk is optional for all back-end types and specifies the name of the volume in the guest domain. If not specified, vdisk is diskN.
To specify a blank value for backend, volume, or vdisk, include only the colon separator. For example, specifying –B ::vdisk001 sets the name of the virtual disk to vdisk001 and uses the default names for the back end and volume. If you do not specify vdisk, you can omit the trailing colon separator. For example, –B /ldoms/ldom1/vol001:vol001 specifies the name of the back-end file as /ldoms/ldom1/vol001 and the volume name as vol001. The default virtual disk name is disk0.