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



Migrating a Domain

You can use the ldm migrate-domain command to initiate a migration of a domain from one system to another system.

For information about the migration options and operands, see the ldm(1M) man page.

Performing a Dry Run

When you provide the -n option to the migrate-domain subcommand, migration checks are performed, but the source domain is not migrated. Any requirement that is not satisfied is reported as an error. This allows you to correct any configuration errors before attempting a real migration.

Note - Because of the dynamic nature of logical domains, it is possible for a dry run to succeed and a migration to fail and vice-versa.

Performing Non-Interactive Migrations

Until the release of the Logical Domains 1.3 software, migrations were interactive operations. When you initiated the migration, you were prompted for the password to use for the target machine. Starting with Logical Domains 1.3, you can use the ldm migrate-domain -p filename command to initiate a non-interactive migration operation.

The file name you specify as an argument to the -p option must have the following properties:

A newline character on the end of the password and all lines that follow the first line are ignored.

The file in which you store the target machine's password must be properly secured. If you plan to store passwords in this manner, ensure that the file permissions are set so that only the root owner, or a privileged user, can read or write the file (400 or 600).