VM for SPARC (Ldom) Migration

Ha-Ldom is supported in OSC and latest version is osc 3.3

 

http://download.oracle.com/docs/cd/E19680-01/821-1687/cacjgdbc/index.html
It seems that key lines:
1)vdisk need to be on share storage (pxfs in osc)

2)Configure Logical Domains to Reset for Control Domain Failures

ldm set-domain failure-policy=reset primary
3)there are other requirement on OS and arch between two hosts
To enable all the Oracle VM Server for SPARC 2.0 features, you must be running at least version 7.3.0 of the system firmware on both UltraSPARC T2 servers and UltraSPARC T2 Plus servers. You must be running at least version 8.0.0 of the system firmware on SPARC T3 servers. This firmware is preinstalled on the SPARC T3 servers. For information about the required Oracle Solaris OS,

Required and Recommended Oracle Solaris OS

To use all the features of the Oracle VM Server for SPARC 2.0 software, the operating system on all domains should be at least the Oracle Solaris 10 9/10 OS. This OS can be either an initial installation of or an upgrade to the Oracle Solaris 10 9/10 OS.

Patches for Older OS Versions and Domains Needing a Patch

Patch ID Control Domain Service Domain I/O Domain Guest Domain
141514-02 (vntsd) X X    
142909-17 (Oracle Solaris 10 9/10 feature kernel update) X X X X

Following are the requirements and restrictions on CPUs when you are performing a migration:

  • The source and target machines must have the same processor type running at the same frequency.

  • The target machine must have sufficient free strands to accommodate the number of strands in use by the domain.

  • Full cores must be allocated for the migrated domain. If the number of strands in the source domain is less than a full core, the extra strands are unavailable to any domain until after the migrated domain is rebooted.
  • After a migration, CPU dynamic reconfiguration (DR) is disabled for the target domain until it has been rebooted. After a reboot has occurred, CPU DR becomes available for that domain.
  • The target system must have enough full cores that are entirely free to provide the number of strands required for the migrated domain. After the migration, if a full core is only partially used by the migrated domain, any extra strands are unavailable to any domain until after the migrated domain is rebooted.

Migrating Memory in an Active Domain

There must be sufficient free memory on the target machine to accommodate the migration of the source domain. In addition, following are a few properties that must be maintained across the migration:

  • It must be possible to create the same number of identically-sized memory blocks.

  • The physical addresses of the memory blocks do not need to match, but the same real addresses must be maintained across the migration.

The target machine must have sufficient free memory to accommodate the migration of the source domain. In addition, the layout of the available memory on the target machine must be compatible with the memory layout of the source domain or the migration will fail.

In particular, if the memory on the target machine is fragmented into multiple small address ranges, but the source domain requires a single large address range, the migration will fail. The following example illustrates this scenario. The target domain has two Gbytes of free memory in two memory blocks:

 

Migrating Cryptographic Units in an Active Domain

Starting with Logical Domains 1.3, you can migrate a guest domain that has bound cryptographic units if it runs an operating system that supports cryptographic unit dynamic reconfiguration (DR).

The following Oracle Solaris OS versions support cryptographic unit DR:

  • At least the Solaris 10 10/09 OS

  • At least the Oracle Solaris 10 5/08 OS plus patch ID 142245-01

At the start of the migration, the Logical Domains Manager determines whether the source domain supports cryptographic unit DR. If supported, the Logical Domains Manager attempts to remove any cryptographic units from the domain. After the migration completes, the cryptographic units are re-added to the migrated domain.


Note –

If the constraints for cryptographic units cannot be met on the target machine, a migration operation might still complete successfully. In such a case, the domain might end up with fewer cryptographic units than it had prior to the migration operation.

 

Required and Recommended System Firmware Patches

To take advantage of all features of Oracle VM Server for SPARC 2.0, ensure that your server runs at least these revisions of the following system firmware patches:

System Patch
Sun SPARC Enterprise T5120 and T5220 Servers 145673-01
Sun Blade T6320 Server Module 145674-01
Netra T5220 Server 145675-01
Sun SPARC Enterprise T5140 and T5240 Servers 145676-01
Netra T5440 Server 145677-01
Sun SPARC Enterprise T5440 Server 145678-01
Sun Blade T6340 Server Module 145679-01
Sun Netra T6340 Server Module 145680-01
Sun Netra CP3260 Blade 141788-13
Sun Netra T6340 Server Module 139448-12
SPARC T3-1 Server 145665-01
SPARC T3-1B Server 145666-01
SPARC T3-2 Server 145667-01
SPARC T3-4 Server 145668-01

About laotsao 老曹

HopBit GridComputing LLC Rockscluster Gridengine Solaris Zone, Solaris Cluster, OVM SPARC/Ldom Exadata, SPARC SuperCluster
This entry was posted in CMT, oracle-vm, Solaris, Solaris 10, SPARC. Bookmark the permalink.

3 Responses to VM for SPARC (Ldom) Migration

  1. Nutra Pure says:

    Great work! This is the type of information that are meant to
    be shared around the web. Shame on the search engines for not positioning this submit upper!
    Come on over and consult with my site . Thanks =)

  2. Elumalai M says:

    I am planning to migrate guest ldom from T5140 to T5-2 will this procedure will be same ???

    Thanks for the detail

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s