1. Overview of the Oracle VM Server for SPARC Software
2. Installing and Enabling Software
4. Setting Up Services and the Control Domain
Introduction to Domain Migration
Overview of a Migration Operation
Authentication for Migration Operations
Performing Non-Interactive Migrations
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
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
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
Because a bound or inactive domain is not executing at the time of the migration, there are fewer restrictions than when you migrate an active domain.
The migration of a bound domain requires that the target is able to satisfy the CPU, memory, and I/O constraints of the source domain. Otherwise, the migration will fail. The migration of an inactive domain does not have such requirements. However, the target must satisfy the domain's constraints when a bind is later attempted. Otherwise, the domain binding will fail.
You can migrate a bound or inactive domain between machines running different processor types and machines that are running at different frequencies.
The Oracle Solaris OS image in the guest must support the processor type on the target machine.
For an inactive domain, there are no checks performed against the virtual input/output (VIO) constraints. So, the VIO servers do not need to exist for the migration to succeed. As with any inactive domain, the VIO servers need to exist and be available at the time the domain is bound.
You cannot perform a domain migration on an I/O domain that is configured with PCIe endpoint devices.
For information about the direct I/O (DIO) feature, see Assigning PCIe Endpoint Devices.