Overview of a live migration
The Logical Domains Manager on the source system accepts the request to migrate a domain and establishes a secure network connection with the Logical Domains Manager that runs on the target system. The migration occurs after this connection has been established.
The migration operation occurs in the following phases:
| Phase 1 | After the source system connects with the Logical Domains Manager that runs in the |
|---|---|
| target system, the Logical Domains Manager transfers information about the source system and the domain to be migrated to the target system. The Logical Domains Manager uses this information to perform a series of checks to | |
| determine whether a migration is possible. The Logical Domains Manager performs state-sensitive checks on the domain that you plan to migrate. The checks it performs is different for an active domain than for bound or inactive ones. | |
| Phase 2 | When all checks in Phase 1 have passed, the source and target systems prepare for the |
| migration. On the target system, the Logical Domains Manager creates a domain to receive the domain. If | |
| the domain that you plant to migrate is inactive or bound, the migration operation proceeds to Phase 5. | |
| Phase 3 | If the domain that you want to migrate is active, its run-time state information is transferred to |
| the target system. The domain continues to run, and the Logical Domains Manager simultaneously tracks the modifications that the operating system makes to this domain. The Logical Domains Manager on the source retrieves this information on the source from the source hypervisor and sends the information to the Logical Domains Manager on the target. The Logical Domains Manager on the target installs this information in the hypervisor for the target. | |
| Phase 4 | The Logical Domains Manager suspends the domain that you want to migrate. At this time, all of the remaining modified |
| state information is re-copied to the target system. In this way, there should be little or no | |
| perceivable interruption to the domain. The amount of interruption depends on the workload. | |
| Phase 5 | A handoff occurs from the Logical Domains Manager on the source system to the |
| Logical Domains Manager on the target system. The handoff occurs when the migrated | |
| domain resumes execution (if the domain to be migrated was active), and the domain on the | |
| source system is destroyed. From this point forward, the migrated domain is the sole version | |
| of the domain running. |
With Oracle VM Server for SPARC 2.1, the default domain migration attempted is Live Migration. If the installed version of Oracle VM Server for SPARC is 2.0, the domain migration defaults to warm migration. For more details on supported configurations, see Migrating Domains in the Oracle® VM Server for SPARC Administration Guide.
Cluster Server (VCS) provides the following support for migration of Oracle VM Server for SPARC guest domains:
For migration of guest domains, ensure each virtual disk back end that is used in the guest domain to be migrated is defined on the target machine. The virtual disk back end that is defined must have the same volume and service names as on the source machine. Similarly each virtual network device in the domain to be migrated must have a corresponding virtual network switch on the target machine. Each virtual network switch must have the same name as the virtual network switch to which the device is attached on the source machine. For complete list of migration requirements for a guest domain, refer to Administration Guide for appropriate Oracle VM for SPARC version that you are using.
Note: If CVM is configured inside the logical domain which is planned for migration, perform this step: Set the value of the LLT peerinact parameter to sufficiently high value on all nodes in the cluster. You set the value to very high value so that while the logical domain is in migration, the system is not thrown out of the cluster by the other members in the cluster. If the CVM stack is unconfigured, the applications can stop. See theCluster Server Administrator's Guidefor LLT tunable parameter configuration instructions. Note: If the control domain exports the FSS volumes to a guest domain, live migration can be performed even if the storage is not physically connected to the hosts of the source system and the target system for migration.