The following system resource features and enhancements have been added to the Solaris 10 5/08 release.
You can perform a trial run of a zone migration before the zone is moved to the new machine by using the “no execute” option, -n.
The zoneadm detach subcommand is used with the -n option to generate a manifest on a running zone without actually detaching the zone. The state of the zone on the originating system is not changed. The zoneadm attach subcommand is used with the -n option to read this manifest and verify that the target machine has the correct configuration to host the zone without actually doing an attach.
For more information, see the following:
Chapter 23, Moving and Migrating Non-Global Zones (Tasks), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones
CPU caps provide absolute fine-grained limits on the amount of CPU resources that can be consumed by a project or a zone. CPU caps are provided as a zonecfg resource, and as project and zone-wide resource controls.
The zonecfg capped-cpu resource provides an absolute limit on the amount of CPU that can be consumed by a project or a zone.
The following resource controls are available:
Absolute limit on the amount of CPU resources that can be consumed by a non-global zone.
Absolute limit on the amount of CPU resources that can be consumed by a project.
For more information, see the following:
zonecfg(1M) man page
zones(5) man page
System Administration Guide: Solaris Containers-Resource Management and Solaris Zones
Use the projmod command with the -A option to apply the resource control values defined in the project database to the active project. Existing values that do not match the values defined in the project file, such as values set manually by prctl(1), are removed.