Skip Navigation Links | |
Exit Print View | |
Oracle VM Server for SPARC 3.0 Administration Guide Oracle VM Server for SPARC |
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
Introduction to Domain Migration
Overview of a Migration Operation
Security for Migration Operations
Performing Non-Interactive Migrations
Domain Migration Requirements for CPUs
Migration Requirements for Memory
Migration Requirements for Physical I/O Devices
Migration Requirements for Virtual I/O Devices
Migration Requirements for NIU Hybrid I/O
Migration Requirements for Cryptographic Units
Delayed Reconfiguration in an Active Domain
Migrating While an Active Domain Has the Power Management Elastic Policy in Effect
Migrating a Domain From the OpenBoot PROM or a Domain That Is Running in the Kernel Debugger
Migrating Bound or Inactive Domains
Migration Requirements for Virtual I/O Devices
Migration Requirements for PCIe Endpoint Devices
Monitoring a Migration in Progress
Recovering From a Failed Migration
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
14. Oracle VM Server for SPARC Configuration Assistant (Oracle Solaris 10)
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
After a migration starts, the migration operation is terminated if the ldm command is interrupted by a KILL signal. When the migration operation is terminated, the migrated domain is destroyed, and the domain to be migrated 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 command terminates the migration in progress, and the domain being migrated resumes as the active domain. The ldm cancel-operation command must be initiated from the source machine. On a given machine, any migration-related command affects the migration operation that was started from that machine. A target machine cannot control a migration operation.
Note - After a migration has been initiated, suspending the ldm process does not pause the operation. The operation is not paused because the Logical Domains Manager daemon (ldmd) on the source and target machines, and not the ldm process, affects the migration. The ldm process awaits a signal from ldmd that the migration has completed before returning.