Skip Navigation Links | |
Exit Print View | |
Oracle VM Server for SPARC 2.1 Administration Guide Oracle VM Server for SPARC |
Part I Oracle VM Server for SPARC 2.1 Software
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
Security for Migration Operations
Performing Non-Interactive Migrations
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 Cryptographic Units
Delayed Reconfiguration in an Active Domain
Migrating While an Active Domain Is in Elastic Mode
Migrating a Domain That is Running in OpenBoot or in the Kernel Debugger
Migrating Bound or Inactive Domains
Migration Requirements for CPUs
Monitoring a Migration in Progress
Canceling a Migration in Progress
Recovering From a Failed Migration
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
15. Using the Oracle VM Server for SPARC Management Information Base Software
16. Logical Domains Manager Discovery
17. Using the XML Interface With the Logical Domains Manager
Only a few domain migration restrictions apply to a bound or inactive domain because such domains are not executing at the time of the migration.
The migration of a bound domain requires that the target machine is able to satisfy the CPU, memory, and I/O constraints of the domain to be migrated. If these constraints cannot be met, the migration will fail.
The migration of an inactive domain does not have such requirements. However, the target machine must satisfy the migrated domain's constraints when a bind is later attempted, or the domain binding will fail.
You can migrate a bound or inactive domain between machines that run different processor types and machines that run at different frequencies.
The Oracle Solaris OS image in the domain to be migrated must support the processor type on the target machine.
For an inactive domain, no checks are performed of the virtual I/O (VIO) constraints. So, the VIO servers do not need to exist for the migration to succeed. As with any inactive domain, the VIO servers must 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.