Observe the following configuration guidelines that apply only to HA for Oracle VM Server.
For restrictions that apply to all data services, see the Oracle Solaris Cluster 4.4 Release Notes.
HA for Oracle VM Server configuration –Oracle VM Server for SPARC can be configured only as a failover data service and not as a scalable data service. It can be configured only in the global zone.
HA for Oracle VM Server virtual disks – The Oracle VM Server for SPARC virtual disk back end can be of any storage or file system that is supported by Oracle Solaris Cluster software. This includes cluster file systems (Global UFS or Global ZFS), raw disk, NFS, iSCSI, and SAN LUNs. The back end is exported through the virtual disk server of the control domain to a domain as a full disk and is visible to the Oracle Solaris installation software inside the logical domain. Virtual disks from non-control domains are not supported.
Multiple domain migration Oracle VM Server for SPARC 3.5 has the following restriction:
While a migration is in progress on a machine, any operation that might result in the modification of the state or configuration of the domain being migrated is blocked. All operations on the domain itself, as well as operations such as bind and stop on other domains on the machine, are blocked.
The implication is that it is not possible to switch a resource group that has multiple resources of type SUNW.ldom, or multiple resource groups where each resource group has a resource of type SUNW.ldom, at the same time as the domain migration will be blocked. Instead, plan to manually serialise domain migration between Oracle Solaris Cluster nodes.
If a resource group has multiple resources of type SUNW.ldom then specify a resource dependency between those resources. If there are multiple resource groups where each resource group has a resource of type SUNW.ldom then plan to switch one resource group at a time.
Live migration and warm migration – HA for Oracle VM Server software supports Oracle VM Server for SPARC live migration and warm migration. For more information, see your Oracle VM Server for SPARC documentation.
In some cases where the cluster cannot determine the target node to which the HA for Oracle VM Server resource group is migrating, it uses an ordinary resource group switchover instead of using live migration. In such cases, the logical domain shuts down on its current node and then boots on its new node. To achieve live migration, relocate the HA for Oracle VM Server resource group by using the clresourcegroup switch command explicitly on the resource group, rather than depending on node evacuation or strong resource group affinities to move the resource group.
You can specify the Abort_migration extension property to specify the behavior of the clrg switchover -n ldom-rg command for a resource group that contains a SUNW.ldom resource. For more information, see the SUNW.ldom (7) manpage.
Live migration is supported only for cluster file systems (Global UFS or Global ZFS), raw disk,NFS, iSCSI, or SAN LUNs, as live migration requires that storage is accessible to all potential primary nodes simultaneously.
Oracle VM Server for SPARC data service creates symlinks for the libschost.so.1 shared object and uses this during live migration of guest domain.
# ln -s /usr/cluster/lib/libschost.so.1 /usr/lib/secure/libschost.so.1 # ln -s /usr/cluster/lib/64/libschost.so.1 /usr/lib/secure/64/libschost.so.1