| Skip Navigation Links | |
| Exit Print View | |
|
Oracle VM Server for SPARC 2.0 Administration Guide |
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
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
Once a migration starts, if the ldm command is interrupted with a KILL signal, the migration is terminated. The target domain is destroyed, and the source domain is resumed if it was active. If the controlling shell of the ldm command is lost, the migration continues in the background.
A migration operation can also be canceled externally by using the ldm cancel-operation command. This terminates the migration in progress, and the source domain resumes as the active domain. The ldm cancel-operation command should be initiated from the source system. On a given system, any migration-related command impacts the migration operation that was started from that system. A system cannot control a migration operation when it is the target system.
Note - Once a migration has been initiated, suspending the ldm(1M) process does not pause the operation, because it is the Logical Domains Manager daemon (ldmd) on the source and target machines that are effecting the migration. The ldm process waits for a signal from the ldmd that the migration has been completed before returning.
|