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
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 a back end is exported as a virtual disk, it can appear in the guest domain either as a full disk or as a single-slice disk. The way it appears depends on the type of the back end and on the options used to export it.
When a back end is exported to a domain as a full disk, it appears in that domain as a regular disk with 8 slices (s0 to s7). Such a disk is visible with the format(1M) command. The disk's partition table can be changed using either the fmthard(1M) or format(1M) command.
A full disk is also visible to the OS installation software and can be selected as a disk onto which the OS can be installed.
Any back end can be exported as a full disk except physical disk slices that can only be exported as single-slice disks.
When a back end is exported to a domain as a single-slice disk, it appears in that domain as a regular disk with 8 slices (s0 to s7). However, only the first slice (s0) is usable. Such a disk is visible with the format(1M) command, but the disk's partition table cannot be changed.
A single-slice disk is also visible from the OS installation software and can be selected as a disk onto which you can install the OS. In that case, if you install the OS using the UNIX File System (UFS), then only the root partition (/) must be defined, and this partition must use all the disk space.
Any back end can be exported as a single-slice disk except physical disks that can only be exported as full disks.
Note - Prior to the Oracle Solaris 10 10/08 OS release, a single-slice disk appeared as a disk with a single partition (s0). Such a disk was not visible with the format(1M) command. The disk also was not visible from the OS installation software and could not be selected as a disk device onto which the OS could be installed.