solaris(7) 맨 페이지 - 윈디하나의 솔라나라

개요

섹션
맨 페이지 이름
검색(S)

solaris(7)

so...s(7)Standards, Environments, Macros, Character Sets, and miscellansyo...s(7)

NAME
       solaris - solaris branded zone

DESCRIPTION
       The  solaris  brand  uses  the  branded  zones  framework  described in
       brands(7) to run zones installed with the same software that is in  the
       global  zone. The solaris branded zone is the default brand and is also
       known as the native zone. The system software must always  be  in  sync
       with  the  global zone when using this brand. The system software pack‐
       ages within the zone are managed using the image packaging system.

   Configuration and Administration
       Zone configurations for solaris branded zones are created and  modified
       with  the zonecfg(8) utility. The zoneadm(8) utility is used to install
       Oracle Solaris from the global zone's pkg(7)  publisher,  and  also  to
       clone and further manipulate such zones.


       The solaris 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  zfs(8)  dataset and only ZFS is supported. The ZFS dataset is cre‐
       ated automatically when the zone is installed or  attached.  If  a  ZFS
       dataset cannot be created, the zone is not installed or attached.


       The  following zonecfg(8) resources and properties are not supported by
       the solaris brand:


         autoshutdown=suspend
         anet:id
         device:id
         net:id
         virtual-cpu
         anet:mac
         ib-vhca
         ib-vhca:port
         capped-memory:pagesize
         capped-memory:pagesize-policy



       There are specific defaults for properties supported for solaris  brand
       as listed below:


         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




       The  following zonecfg(8) resources and properties are supported by the
       live zone reconfiguration for solaris brand:


         anet (with exceptions stated below)
         capped-memory
         dedicated-cpu
         device
         fs
         net (with exceptions stated below)
         pool
         scheduling-class
         zone.* rctls
         dataset




       The following zonecfg(8) resources and properties are not supported  by
       the live zone reconfiguration for solaris brand:


         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




       Any  changes made to the listed unsupported resources and properties in
       the persistent configuration will be ignored by the live zone reconfig‐
       uration if they are applied to the running zone.


       Any attempts to modify the listed unsupported resources and  properties
       in the live configuration will be refused.


       For  the  list  of  this  brand's  specific subcommand options, see its
       Brand-Specific section in zoneadm(8).

   Cold Migration
       solaris branded zones can be cold migrated to compatible hosts by using
       the zoneadm migrate command, as described in the zoneadm(8) man page.


       For cold migration to work, the same services and packages must be con‐
       figured as for the solaris-kz(7) brand cold migration.


       Only zones on shared storage may be  migrated.  Supported  storage  URI
       types for migration are iscsi and lu.

   Auxiliary State
       The following auxiliary state (as shown by zoneadm list -is) is defined
       for this brand:

       no-config    The  zone  is known to the system but its configuration is
                    missing. State of the zone is always incomplete.


EXAMPLES
       Example 1 Conversion of a Global Zone to a solaris Zone



       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
       P2V (physical to virtual).



       To  ensure that the data in the archive does not become stale, applica‐
       tions 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.



       First, create a recovery archive of the source system. This assumes the
       source system has no non-global zones installed.



         web-1# archiveadm create --recovery /net/images/web-1.uar





       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 zonecfg(8).



         t4-1# zonecfg -z web-1
         Use 'create' to begin configuring a new zone.
         zonecfg:web-1> create -a /net/images/web-1.uar
         zonecfg:web-1> set zonepath=/zones/web-1
         zonecfg:web-1> exit





       If there is a preference for not using the interactive  mode,  you  can
       use the following command:



         t4-1# zonecfg -z web-1 "create -a /net/images/web-1.uar; \
             set zonepath=/zones/web-1"





       Finally, install the zone from the archive.



         t4-1# zoneadm -z web-1 install -a /net/images/web-1.uar





       If both the source system and newly installed zone have the same IP ad‐
       dress  or have other potential conflicts, be sure that only one of them
       is running at a time.

       Example 2 Zone Migration Using a Unified Archive



       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 in‐
       stalled.



       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.



         t4-1# archiveadm create -r -z web-1 /net/images/v2v/web-1.uar





       Next, configure the zone on the target system using the archive.



         t4-2# zonecfg -z web-1 create -a /net/images/v2v/web-1.uar





       Finally, install the zone from the archive.



         t4-2# zoneadm -z web-1 install -a /net/images/v2v/web-1.uar





       Be  sure to shutdown the zone on the source system before booting it on
       the target system.

ATTRIBUTES
       See attributes(7) for a description of the following attributes:

       tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE  TYPEAT‐
       TRIBUTE  VALUE  _ Availabilitysystem/zones/brand/brand-solaris _ Inter‐
       face StabilityUncommitted


SEE ALSO
       brands(7),  solaris-kz(7),   solaris10(7),   zones(7),   archiveadm(8),
       zfs(8), zoneadm(8), zonecfg(8)

Oracle Solaris 11.4               29 Aug 2025                        so...s(7)
맨 페이지 내용의 저작권은 맨 페이지 작성자에게 있습니다.
RSS ATOM XHTML 5 CSS3