JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle VM Server for SPARC 2.1 Administration Guide     Oracle VM Server for SPARC
search filter icon
search icon

Document Information

Preface

Part I Oracle VM Server for SPARC 2.1 Software

1.  Overview of the Oracle VM Server for SPARC Software

2.  Installing and Enabling Software

3.  Security

4.  Setting Up Services and the Control Domain

5.  Setting Up Guest Domains

6.  Setting Up I/O Domains

7.  Using Virtual Disks

Introduction to Virtual Disks

Managing Virtual Disks

Add a Virtual Disk

Export a Virtual Disk Back End Multiple Times

Change Virtual Disk Options

Change the Timeout Option

Remove a Virtual Disk

Virtual Disk Identifier and Device Name

Virtual Disk Appearance

Full Disk

Single-Slice Disk

Virtual Disk Back End Options

Read-only (ro) Option

Exclusive (excl) Option

Slice (slice) Option

Virtual Disk Back End

Physical Disk or Disk LUN

Export a Physical Disk as a Virtual Disk

Physical Disk Slice

Export a Physical Disk Slice as a Virtual Disk

Export Slice 2

File and Volume

File or Volume Exported as a Full Disk

Export a File 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

Configuring Virtual Disk Multipathing

Configure Virtual Disk Multipathing

CD, DVD and ISO Images

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 Timeout

Virtual Disk and SCSI

Virtual Disk and the format Command

Using ZFS With Virtual Disks

Configuring a ZFS Pool in a Service Domain

Storing Disk Images With ZFS

Examples of Storing Disk Images With ZFS

Create a Disk Image Using a ZFS Volume

Create a Disk Image Using a ZFS File

Export the ZFS Volume

Export the 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

Cloning a Boot Disk Image

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

8.  Using Virtual Networks

9.  Migrating Domains

10.  Managing Resources

11.  Managing Configurations

12.  Performing Other Administration Tasks

Part II Optional Oracle VM Server for SPARC Software

13.  Oracle VM Server for SPARC Physical-to-Virtual Conversion Tool

14.  Oracle VM Server for SPARC Configuration Assistant

15.  Using the Oracle VM Server for SPARC Management Information Base Software

16.  Logical Domains Manager Discovery

17.  Using the XML Interface With the Logical Domains Manager

Glossary

Index

Virtual Disk Identifier and Device Name

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

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.