|Skip Navigation Links|
|Exit Print View|
|Oracle VM Server for SPARC 2.2 Administration Guide Oracle VM Server for SPARC|
The basic process is to save the resource constraints information for each domain into an XML file, which can then be re-issued to the Logical Domains Manager, for example, after a hardware failure to rebuild a desired configuration.
How to Restore a Domain Configuration From an XML File (ldm add-domain) works for guest domains, but not for the control (primary) domain. You can save the primary domain's constraints to an XML file, but you cannot feed the file back into the ldm add-domain -i command. However, you can use the ldm init-system command and the resource constraints from the XML file to reconfigure your primary domain. You can also use the ldm init-system command to reconfigure other domains that are described in the XML file, but those domains are left inactive when the configuration is complete.
With the exception of the named physical resources, the following method does not preserve actual bindings. However, the method does preserve the constraints used to create those bindings. So after completing the following procedure, the domains have the same virtual resources, but are not necessarily bound to the same physical resources. Named physical resources are bound as specified by the administrator.
This procedure shows how to save a domain configuration for a single domain or for all the domains on a system.
# ldm list-constraints -x ldom >ldom.xml
The following example shows how to create an XML file, ldg1.xml, which contains the ldg1 domain's constraints:
# ldm list-constraints -x ldg1 >ldg1.xml
# ldm list-constraints -x >file.xml
The following example shows how to create an XML file, config.xml, which contains the constraints for all the domains on a system:
# ldm list-constraints -x >config.xml
Instead of this procedure, you can use the ldm init-system command to restore domain configurations from an XML file. See How to Restore a Domain Configuration From an XML File (ldm init-system).
# ldm add-domain -i ldom.xml
# ldm bind-domain [-fq] ldom
The -f option forces the binding of the domain even if invalid back-end devices are detected. The -q option disables the validation of back-end devices so that the command runs more quickly.
# ldm start-domain ldom
Example 11-1 Restoring a Single Domain From an XML File
The following example shows how to restore a single domain. First, you restore the ldg1 domain from the XML file. Then, you bind and restart the ldg1 domain that you restored.
# ldm add-domain -i ldg1.xml # ldm bind ldg1 # ldm start ldg1
This procedure explains how to use the ldm init-system command with an XML file to re-create a previously saved configuration. The XML file describes one or more domain configurations. The XML file can be created by running the ldm ls-constraints -x command. The ldm init-system command is expected to be run in the factory-default configuration, but it can restore any configuration from an XML file. The primary domain is reconfigured as specified in the file, and any non-primary domains that have configurations in the XML file are reconfigured but left inactive.
Instead of this procedure, you can use the ldm add-domain command to restore a single domain configuration from an XML file. See How to Restore a Domain Configuration From an XML File (ldm add-domain).
primary# ldm list-config | grep "factory-default" factory-default [current]
If the system is not in the factory-default configuration, see How to Restore the Factory Default Configuration.
For Oracle Solaris 10, see Configuring RBAC (Task Map) in System Administration Guide: Security Services. For Oracle Solaris 11, see Part III, Roles, Rights Profiles, and Privileges, in Oracle Solaris Administration: Security Services.
# ldm init-system [-frs] -i filename.xml
The primary domain must be rebooted for the configuration to take effect. The -r option reboots the primary domain after the configuration. If you do not specify the -r option, you must perform the reboot manually.
The -s option restores only the virtual services configuration (vds, vcc, and vsw) and might be able to be performed without having to reboot.
The -f option skips the factory-default configuration check and continues irrespective of what was already configured on the system. Use the -f option with caution. The ldm init-system command assumes that the system is in the factory-default configuration and so directly applies the changes that are specified by the XML file. Using -f when the system is in a configuration other than the factory default will likely result in a system that is not configured as specified by the XML file. One or more changes might fail to be applied to the system, depending on the combination of changes in the XML file and the initial configuration.
Example 11-2 Restoring Domains From XML Configuration Files
The following examples show how to use the ldm init-system command to restore the primary domain and all the domains on a system from the factory-default configuration.
Restore the primary domain. The -r option is used to reboot the primary domain after the configuration completes. The primary.xml file contains the XML domain configuration that you saved at an earlier time.
primary# ldm init-system -r -i primary.xml
Restore all the domains on a system. Restore the domains on the system to the configurations in the config.xml XML file. The config.xml file contains the XML domain configurations that you saved at an earlier time. The primary domain is restarted automatically by the ldm init-system command. Any other domains are restored, but not bound and restarted.
# ldm init-system -r -i config.xml
After the system reboots, the following commands bind and restart the ldg1 and ldg2 domains:
# ldm bind ldg1 # ldm start ldg1 # ldm bind ldg2 # ldm start ldg2