Hallo, dies ist ein Test.

PWD: /www/data-lst1/unixsoft/unixsoft/kaempfer/.public_html

Running in File Mode
Relative path: ./../../../../../../sbin/../man/man7/solaris.7
Real path: /usr/share/man/man7/solaris.7
Zurück

'\" te .\" Copyright (c) 2009, 2021, Oracle and/or its affiliates. .TH solaris 7 "29 Nov 2021" "Oracle Solaris 11.4" "Standards, Environments, Macros, Character Sets, and miscellany" .SH NAME solaris \- solaris branded zone .SH DESCRIPTION .sp .LP The \fBsolaris\fR brand uses the branded zones framework described in \fBbrands\fR(7) to run zones installed with the same software as is installed in the global zone. The system software must always be in sync with the global zone when using a \fBsolaris\fR brand. The system software packages within the zone are managed using the image packaging system. .SS "Configuration and Administration" .sp .LP The \fBsolaris\fR brand supports the whole root non-global zone model. All of the required system software and any additional packages are installed into the private file systems of the zone. The zone must reside on its own \fBzfs\fR(8) dataset and only ZFS is supported. The ZFS dataset is created automatically when the zone is installed or attached. If a ZFS dataset cannot be created, the zone is not installed or attached. .sp .LP The following \fBzonecfg\fR(8) resources and properties are not supported by the solaris brand: .sp .in +2 .nf autoshutdown=suspend anet:id device:id net:id virtual-cpu anet:mac ib-vhca ib-vhca:port capped-memory:pagesize capped-memory:pagesize-policy .fi .in -2 .sp .sp .LP There are specific defaults for properties supported for \fBsolaris\fR brand as listed below: .sp .in +2 .nf Resource Property Default Value global zonepath /system/zones/%{zonename} autoboot false global-time false ip-type exclusive auto-shutdown shutdown net configure-allowed-address true anet mac-address auto lower-link auto link-protection mac-nospoof .fi .in -2 .sp .sp .LP The following \fBzonecfg\fR(8) resources and properties are supported by the live zone reconfiguration for \fBsolaris\fR brand: .sp .in +2 .nf anet (with exceptions stated below) capped-memory dedicated-cpu device fs net (with exceptions stated below) pool scheduling-class zone.* rctls dataset .fi .in -2 .sp .sp .LP The following \fBzonecfg\fR(8) resources and properties are not supported by the live zone reconfiguration for \fBsolaris\fR brand: .sp .in +2 .nf anet:allowed-address anet:configure-allowed-address anet:defrouter anet:evs anet:vport file-mac-profile fs-allowed hostid limitpriv global-time net:allowed-address net:configure-allowed-address net:defrouter npiv rootzpool tenant zpool .fi .in -2 .sp .sp .LP Any changes made to the listed unsupported resources and properties in the persistent configuration will be ignored by the live zone reconfiguration if they are applied to the running zone. .sp .LP Any attempts to modify the listed unsupported resources and properties in the live configuration will be refused. .sp .LP For the list of \fBsolaris\fR brand-specific subcommand options, see \fBzoneadm\fR(8). .SS "Cold Migration" .sp .LP \fBsolaris\fR branded zones can be cold migrated to compatible hosts by using the \fBzoneadm\ migrate\fR command, as described in the \fBzoneadm\fR(8) man page. .sp .LP For cold migration to work, the same services and packages must be configured as for the \fBsolaris-kz\fR(7) brand cold migration. .sp .LP Only zones on shared storage may be migrated. Supported storage URI types for migration are \fBiscsi\fR and \fBlu\fR. .SS "Auxiliary State" .sp .LP The following auxiliary state (as shown by \fBzoneadm\ list\ -is\fR) is defined for this brand: .sp .ne 2 .mk .na \fB\fBno-config\fR\fR .ad .RS 13n .rt The zone is known to the system but its configuration is missing. State of the zone is always incomplete. .RE .SH EXAMPLES .LP \fBExample 1\fR Conversion of a Global Zone to a \fBsolaris\fR Zone .sp .LP The following example shows how to create an archive of a global zone, then use that archive to configure and install a non-global zone. The installation process transforms the image of a global zone such that it can work as a non-global zone. This process is commonly referred to as \fBP2V\fR (physical to virtual). .sp .LP To ensure that the data in the archive does not become stale, applications running in the source zone should be stopped or the zone itself should be shut down before the archive is created. If neither of these is done, it may become necessary to synchronize application data after the zone is installed. .sp .LP First, create a recovery archive of the source system. This assumes the source system has no non-global zones installed. .sp .in +2 .nf web-1# \fBarchiveadm create --recovery /net/images/web-1.uar\fR .fi .in -2 .sp .sp .LP Next, configure the zone on the target system using the configuration stored in the archive. It may be necessary to further customize it. See examples in \fBzonecfg\fR(8). .sp .in +2 .nf t4-1# \fBzonecfg -z web-1\fR Use 'create' to begin configuring a new zone. zonecfg:web-1> \fBcreate -a /net/images/web-1.uar\fR zonecfg:web-1> \fBset zonepath=/zones/web-1\fR zonecfg:web-1> \fBexit\fR .fi .in -2 .sp .sp .LP If there is a preference for not using the interactive mode, you can use the following command: .sp .in +2 .nf t4-1# \fBzonecfg -z web-1 "create -a /net/images/web-1.uar; \e set zonepath=/zones/web-1" \fR .fi .in -2 .sp .sp .LP Finally, install the zone from the archive. .sp .in +2 .nf t4-1# \fBzoneadm -z web-1 install -a /net/images/web-1.uar\fR .fi .in -2 .sp .sp .LP If both the source system and newly installed zone have the same IP address or have other potential conflicts, be sure that only one of them is running at a time. .LP \fBExample 2\fR Zone Migration Using a Unified Archive .sp .LP To ensure that the data in the archive does not become stale, it is suggested that applications on the source zone are stopped or the zone is shut down before creating the archive. If this is not done, it may be necessary to synchronize application data after the zone is installed. .sp .LP First, create a recovery archive of the zone. This is best performed from the global zone. If it is performed within the zone, the zone will not be able to be configured from the archive. .sp .in +2 .nf t4-1# \fBarchiveadm create -r -z web-1 /net/images/v2v/web-1.uar \fR .fi .in -2 .sp .sp .LP Next, configure the zone on the target system using the archive. .sp .in +2 .nf t4-2# \fBzonecfg -z web-1 create -a /net/images/v2v/web-1.uar \fR .fi .in -2 .sp .sp .LP Finally, install the zone from the archive. .sp .in +2 .nf t4-2# \fBzoneadm -z web-1 install -a /net/images/v2v/web-1.uar \fR .fi .in -2 .sp .sp .LP Be sure to shutdown the zone on the source system before booting it on the target system. .SH ATTRIBUTES .sp .LP See \fBattributes\fR(7) for a description of the following attributes: .sp .TS tab( ) box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) . ATTRIBUTE TYPE ATTRIBUTE VALUE _ Availability system/zones/brand/brand-solaris _ Interface Stability Uncommitted .TE .sp .SH SEE ALSO .sp .LP \fBarchiveadm\fR(8), \fBbrands\fR(7), \fBzfs\fR(8), \fBzoneadm\fR(8), \fBzonecfg\fR(8), \fBzones\fR(7)