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

Document Information


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

8.  Using Virtual Networks

9.  Migrating Domains

Introduction to Domain Migration

Overview of a Migration Operation

Software Compatibility

Authentication for Migration Operations

Migrating a Domain

Performing a Dry Run

Performing Non-Interactive Migrations

Migrating an Active Domain

Migrating CPUs in an Active Domain

Migrating Memory in an Active Domain

Migrating Physical I/O Devices in an Active Domain

Migrating Virtual I/O Devices in an Active Domain

Migrating NIU Hybrid Input/Output in an Active Domain

Migrating Cryptographic Units in an Active Domain

Delayed Reconfiguration in an Active Domain

Migrating While an Active Domain Is in Elastic Mode

Operations on Other Domains

Migrating Bound or Inactive Domains

Migrating CPUs in a Bound or Inactive Domain

Migrating Virtual Input/Output in a Bound or Inactive Domain

Migrating PCIe Endpoint Devices in a Bound or Inactive Domain

Monitoring a Migration in Progress

Canceling a Migration in Progress

Recovering From a Failed Migration

Migration Examples

10.  Managing Resources

11.  Managing Configurations

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

E.  Logical Domains Manager XML Schemas



Authentication for Migration Operations

Because the migration operation executes on two machines, a user must be authenticated on both the source and target host. In particular, a user other than superuser must have the and solaris.ldoms.write authorizations.

The ldm command-line interface for migration allows the user to specify an optional alternate user name for authentication on the target host. If this is not specified, the user name of the user executing the migration command is used. In both cases, the user is prompted for a password for the target system, unless the -p option is used to initiate a non-interactive migration.