Restrictions for Managing Physical Resources on Domains

The following restrictions apply to the assignment of physical resources:

• You cannot make physical and non-physical memory bindings, or physical and non-physical core bindings, in the same domain.

• You can have non-physical memory and physical core bindings, or non-physical core and physical memory bindings, in the same domain.

• When you add a physical resource to a domain, the corresponding resource type becomes constrained as a physical binding.

• Attempts to add anonymous CPUs to or remove them from a domain where physical-bindings=core will fail.

• For unbound resources, the allocation and checking of the resources can occur only when you run the ldm bind command.

• When removing physical memory from a domain, you must remove the exact physical memory block that was previously added.

• Physical memory ranges must not overlap.

• You can use only the ldm add-core cid= or ldm set-core cid= command to assign a physical resource to a domain.

• If you use the ldm add-mem mblock= or ldm set-mem mblock= command to assign multiple physical memory blocks, the addresses and sizes are checked immediately for collisions with other bindings.

• A domain that has partial cores assigned to it can use the whole-core semantics if the remaining CPUs of those cores are free and available.