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
Virtual Disk Identifier and Device Name
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
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
The format(1M) command recognizes all virtual disks that are present in a domain. However, for virtual disks that are exported as single-slice disks, the format command cannot change the partition table of the virtual disk. Commands such as label will fail unless you try to write a disk label similar to the one that is already associated with the virtual disk.
Virtual disks whose back ends are SCSI disks support all format(1M) subcommands. Virtual disks whose back ends are not SCSI disks do not support some format(1M) subcommands, such as repair and defect. In that case, the behavior of format(1M) is similar to the behavior of Integrated Drive Electronics (IDE) disks.