1. Overview of the Oracle VM Server for SPARC Software
2. Installing and Enabling Software
4. Setting Up Services and the Control Domain
Export a Virtual Disk Back End Multiple Times
Export a Physical Disk as a Virtual Disk
Export a Physical Disk Slice as a Virtual Disk
File or Volume Exported as a Full Disk
File or Volume Exported as a Single-Slice Disk
Export a ZFS Volume as a Single-Slice Disk
Exporting Volumes and Backward Compatibility
Summary of How Different Types of Back Ends Are Exported
Guidelines for Exporting Files and Disk Slices as Virtual Disks
Using the Loopback File (lofi) Driver
Directly or Indirectly Exporting a Disk Slice
Configuring Virtual Disk Multipathing
Configure Virtual Disk Multipathing
Export a CD or DVD From the Service Domain to the Guest Domain
Export an ISO Image From the primary Domain to Install a Guest Domain
Virtual Disk and the format(1M) Command
Configuring a ZFS Pool in a Service Domain
Examples of Storing Disk Images With ZFS
Create a Disk Image Using a ZFS Volume
Create a Disk Image Using a ZFS File
Assign the ZFS Volume or File to a Guest Domain
Creating a Snapshot of a Disk Image
Create a Snapshot of a Disk Image
Using Clone to Provision a New Domain
Using Volume Managers in a Logical Domains Environment
Using Virtual Disks on Top of Volume Managers
Using Virtual Disks on Top of Solaris Volume Manager
Using Virtual Disks When VxVM Is Installed
Using Volume Managers on Top of Virtual Disks
Using ZFS on Top of Virtual Disks
Using Solaris Volume Manager on Top of Virtual Disks
Using VxVM on Top of Virtual Disks
12. Performing Other Administration Tasks
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
When you use the ldm add-vdisk command to add a virtual disk to a domain, you can specify its device number by setting the id property.
# ldm add-vdisk [id=disk-id] disk-name volume-name@service-name ldom
Each virtual disk of a domain has a unique device number that is assigned when the domain is bound. If a virtual disk is added with an explicit device number (by setting the id property), the specified device number is used. Otherwise, the system automatically assigns the lowest device number available. In that case, the device number assigned depends on how virtual disks were added to the domain. The device number eventually assigned to a virtual disk is visible in the output of the ldm list-bindings command when a domain is bound.
When a domain with virtual disks is running the Oracle Solaris OS, each virtual disk appears in the domain as a c0dn disk device, where n is the device number of the virtual disk.
In the following example, the ldg1 domain has two virtual disks: rootdisk and pdisk. rootdisk has a device number of 0 (disk@0) and appears in the domain as the disk device c0d0. pdisk has a device number of 1 (disk@1) and appears in the domain as the disk device c0d1.
primary# ldm list-bindings ldg1 ... DISK NAME VOLUME TOUT DEVICE SERVER MPGROUP rootdisk dsk_nevada@primary-vds0 disk@0 primary pdisk c3t40d1@primary-vds0 disk@1 primary ...
Caution - If a device number is not explicitly assigned to a virtual disk, its device number can change when the domain is unbound and is later bound again. In that case, the device name assigned by the OS running in the domain can also change and break the existing configuration of the system. This might happen, for example, when a virtual disk is removed from the configuration of the domain. |