How to perform a warm/live migration on an OVM SPARC (LDom) guest within a virtual pool (vpool) using Ops Center
(Doc ID 1390801.1)
Last updated on JUNE 08, 2018
Applies to:Enterprise Manager Ops Center - Version 11g and later
Sun SPARC Sun OS
Oracle Solaris on SPARC (64-bit)
***Checked for relevance on 08-Oct-2013***
After you have successfully created a vpool and installed one or more guests as described in 1390793.1 you might want to use warm/live migration features to gain more uptime.
- warm migration - the domain is running on the source system. The LDoms manager on the source system contacts the target system to start the migration and ensure the target system matches chip type and has resources to host the domain. It then suspends the guest's operation, compresses and encrypts its state information (mostly RAM) using the T-series crypto acceleration, and transmits it to the target. The LDoms manager on the target decompresses and decrypts the contents and resumes domain operation. The domain can be unresponsive for minutes (depending on memory size and network speed). but picks up from where it was.
- live migration - is similar to warm migration, except that the guest is not suspended during transmission. Instead, the LDoms manager keeps track of memory changed while state is being transmitted, and then makes followup passes to retransmit data changed state information. A brief pause is used at the end to transmit residual changed state. This method is typical for virtual machine systems that provide live guest migration.
same command: ldm migrate
Before LDOM 2.1, only warm migration was supported.
Since LDOM 2.1, only live migration is performed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document