Login to Solaris Here is the available zpool on my system. As per previous command output,kernel zone is going to create virtual disk under rpool. In rpool, we do not have 16GB free space. You need IPS repository to install the kernel zone.
If you do not have a local repository, just set to oracle IPS repo. You need to configure package repository for kernel zone like global for any additional package installation and non-global zone installation.
Exit Print View. Documentation Home » Oracle Solaris Language: English. How to Create and Deploy a Non-Global Zone Unless specified otherwise, all the procedures in this guide assume that you are not working directly on the server system that hosts the zones. Before You Begin If you plan to install other packages in addition to the default solaris-small-server package, make sure that you have properly prepared the manifest.
Become a zone administrator. Create the zone. Choose from one of the following options. These fields are:. The uuid value is assigned by libuuid 3LIB when the zone is installed, and is useful for identifying the same zone when present or renamed on alternate boot environments.
The —v and —p options are mutually exclusive. If neither —v nor —p is used, just the zone name is listed. Display verbose information, including zone name, id, current state, root directory, brand type, ip-type, and options. The apply subcommand reconfigures a running zone to match persistent configuration of a zone maintained through zonecfg 1M and prints out performed actions.
Applied configuration takes effect immediately and does not require reboot of the zone. The apply command is available only for running zones. See respective brand man page for details on resources supported by the live zone reconfiguration. Runs the reconfiguration in a dry run mode that does not change the configuration of a running zone. The dry run mode acts the same way as the real reconfiguration, but leaves the running zone intact. Use the dry run mode to review actions that would be performed by the real reconfiguration.
Quiet mode. Suppresses all messages and returns a status code only. In case of the global zone, no options are allowed. The apply subcommand reconfigures resource controls, pools, and sets the file-mac-profile. If the global zone is configured as an immutable global zone, it immediately makes the zone immutable. Change the state of an installed zone to incomplete. This command can be useful in cases where administrative changes on the system have rendered a zone permanently unusable or inconsistent.
This change cannot be undone, except by uninstalling the zone. Change the state of an installed zone to unavailable.
This command can be useful in cases where administrative changes or failures on the system have rendered a zone temporarily unusable. This change can be undone with the attach subcommand. Live-migrate the zone to the given destination host. The zone will continue running on the source host until the final stage of migration. After a migration, any zlogin sessions will be terminated.
However, network connections to the zone are maintained. The zone configuration must be compatible with the destination host's environment, as if you were detaching then attaching the zone. For example, any storage references should use a storage URI see zonecfg 1M that is accessible by both hosts.
The zone can be configured on the destination host prior to migration; in this case, that configuration is used to start the zone on the destination host. If the configuration is incompatible with the current zone configuration for example, a virtual disk is missing , an error will be returned. If the zone is not configured on the destination, live migration will configure it based on the current zone configuration. After migration, the zone will be detached from the source zone, but left in a configured state.
The scheme defaults to 'rads', 'user' defaults to the current user, and 'port' defaults to the standard RAD port. To receive migrating zones, the RAD service mentioned must be running. In addition, the ' kz-migr ' service under inetd must be enabled. With the default configuration, therefore, ports and must be accessible. Do a dry-run: checks if the zone could be live migrated to the destination host, but leave it running.
Use the specified cipher to encrypt memory transfer. The value "none" disables encryption. The value "list" may be used to list supported ciphers. If not specified, a cipher will be automatically chosen based on the source and destination capabilities.
The zone must be halted before this subcommand can be used. Note, for zones configured with a rootzpool resource only the zonepath will be renamed but the zone itself will not move out of its containing zpool. Prepares a zone for running applications but does not start any user processes in the zone. Restart the zone. This is equivalent to a halt boot sequence shutdown scripts are not run. Rename the zone. This subcommand may be used for configured and installed zones. The installed zone must be halted before this subcommand can be used.
Use the following command to rename a zone:. The rename subcommand is not supported for the solaris-kz brand. The shutdown subcommand waits until the zone is successfully shut down; a zoneadm halt can be used to forcibly halt the zone, if the shutdown process takes a long time.
If —r is specified, reboot the zone. See the boot subcommand for supported boot options. Save a core dump of a running solaris-kz brand to the global zone by default, kzcore. X in the current directory. This core dump file can be debugged through mdb 1. If —k is specified then the core dump is placed in the location configured by coreadm 1M for kernel zone core dumps.
Suspend a running solaris-kz brand zone to disk. The zone is suspended to an image file contained within the zone path.
The zone can be resumed through zoneadm boot. Uninstall the specified zone from the system. Use this subcommand with caution.
0コメント