Migrating a Domain That Uses Named Resources

Caution:

Do not assign named resources unless you are an expert administrator.

You can migrate a domain that is configured to use named resources by specifying the cores and memory ranges on the target machine to be used by the migrating domain. To migrate such a domain, ensure that the domain is in the native migration class and that it has the whole-core constraint applied.

The ldm migrate-domain command uses the cidmap and mblockmap properties to specify physical resource mappings between the source machine and the target machine.

ldm migrate-domain -c domain-name cidmap=core-ID:core-ID[,core-ID:core-ID,...] \
mblockmap=phys-addr:phys-addr[,phys-addr:phys-addr,...] target-machine

In the following example, the ldm migrate-domain command migrates the ldg1 domain from the system1 machine to the system2 machine. The ldg1 domain has named cores 8 and 9 and a named memory block at physical address 0x400000000. The domain is migrated to the system2 machine and will use cores 16 and 17 and a memory block at physical address 0xc00000000:

system1:primary# ldm migrate-domain -c ldg1 cidmap=8:16,9:17 \
mblockmap=0x400000000:c00000000 system2

Ensure that the cidmap property specifies free, non-duplicate cores on the target machine and that the mblockmap property specifies free, non-overlapping physical address ranges on the target machine. The physical address ranges must meet the migration requirements for target machine memory. See Migration Requirements for Memory.

If you omit the cidmap and mblockmap properties from the ldm migrate-domain command, each core ID on the source machine is mapped to the same core ID on the target machine and each physical address range on the source machine is mapped to the same physical address range on the target machine. Thus, the following command migrates the ldg1 domain to the system2 machine and the migrated domain uses cores 8 and 9 and a memory block at physical address 0x400000000:

system1:primary# ldm migrate-domain -c ldg1 system2