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

Document Information


Part I Oracle VM Server for SPARC 3.0 Software

1.  Overview of the Oracle VM Server for SPARC Software

2.  Installing and Enabling Software

3.  Oracle VM Server for SPARC Security

4.  Setting Up Services and the Control Domain

5.  Setting Up Guest Domains

6.  Setting Up I/O Domains

7.  Using Virtual Disks

8.  Using Virtual Networks

9.  Migrating Domains

10.  Managing Resources

11.  Managing Domain 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

Oracle VM Server for SPARC P2V Tool Overview

Collection Phase

Preparation Phase

Conversion Phase

Back-End Devices

Installing the Oracle VM Server for SPARC P2V Tool



How to Install the Oracle VM Server for SPARC P2V Tool

Using the ldmp2v Command

14.  Oracle VM Server for SPARC Configuration Assistant (Oracle Solaris 10)

15.  Using Power Management

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

17.  Logical Domains Manager Discovery

18.  Using the XML Interface With the Logical Domains Manager



Back-End Devices

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:

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.

Note - During the conversion process, the virtual disk is temporarily named guest-name-diskN to ensure that the name in the control domain is unique.

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.