Print this page
@@ -4,17 +4,17 @@
NAME
zonecfg - set up zone configuration
SYNOPSIS
- zonecfg {-z zonename | -u uuid}
+ zonecfg -z zonename
- zonecfg {-z zonename | -u uuid} subcommand
+ zonecfg -z zonename subcommand
- zonecfg {-z zonename | -u uuid} -f command_file
+ zonecfg -z zonename -f command_file
zonecfg help
@@ -27,12 +27,11 @@
The default scope is global.
The following synopsis of the zonecfg command is for interactive usage:
- {-z zonename | -u uuid}
- zonecfg {-z zonename | -u uuid} subcommand
+ zonecfg -z zonename subcommand
Parameters changed through zonecfg do not affect a running zone. The
@@ -192,24 +191,18 @@
(global)
fs-allowed
- (global)
-
- zfs-io-priority
-
-
fs
dir, special, raw, type, options
net
- address, allowed-address, defrouter, global-nic, mac-addr,
- physical, property, vlan-id
+ address, physical, defrouter
device
match
@@ -372,18 +365,12 @@
Values needed to determine how, where, and so forth to mount file
systems. See mount(1M), mount(2), fsck(1M), and vfstab(4).
- inherit-pkg-dir: dir
+ net: address, physical, defrouter
- The directory path.
-
-
- net: address, allowed-address, defrouter, global-nic, mac-addr,
- physical, property, vlan-id
-
The network address and physical interface name of the network
interface. The network address is one of:
o a valid IPv4 address, optionally followed by "/" and a
prefix length;
@@ -408,20 +395,10 @@
zone prior to booting the non-global zone. However, if the
interface is not used by the global zone, it should be configured
down in the global zone, and the default router for the interface
should be specified here.
- The global-nic is used for exclusive stack zones which will use a
- VNIC on-demand. When the zone boots, a VNIC named using the
- physical property will be created on the global NIC. If provided,
- the mac-addr and vlan-id will be set on this VNIC.
-
- The property setting is a resource which can be used to set
- arbitrary name/value pairs on the network. These name/value pairs
- are made available to the zone's brand, which can use them as
- needed to set up the network interface.
-
For an exclusive-IP zone, the physical property must be set and the
address and default router properties cannot be set.
device: match
@@ -575,20 +552,11 @@
WARNING: allowing filesystem mounts other than the default may
allow the zone administrator to compromise the system with a
malicious filesystem image, and is not supported.
- global: zfs-io-priority
- Specifies a priority for this zone's ZFS I/O. The priority is used
- by the ZFS I/O scheduler as in input to determine how to schedule
- I/O across zones. By default all zones have a priority of 1. The
- value can be increased for zones whose I/O is more critical. This
- property is the preferred way to set the zone.zfs-io-priority rctl.
-
-
-
The following table summarizes resources, property-names, and types:
resource property-name type
(global) zonename simple
(global) zonepath simple
@@ -604,26 +572,17 @@
(global) max-msg-ids simple
(global) max-sem-ids simple
(global) max-shm-ids simple
(global) max-shm-memory simple
(global) scheduling-class simple
- (global) zfs-io-priority simple
fs dir simple
special simple
raw simple
type simple
options list of simple
net address simple
- allowed-address simple
- defrouter simple
- global-nic simple
- mac-addr simple
physical simple
- property list of complex
- name simple
- value simple
- vlan-id simple
device match simple
rctl name simple
value list of complex
attr name simple
type simple
@@ -755,15 +714,10 @@
alphanumeric characters, the underscore (_) the hyphen (-), and the
dot (.). The name global and all names beginning with SUNW are
reserved and cannot be used.
- -u uuid
-
- Specify the uuid of a zone instead of the Zone name.
-
-
SUBCOMMANDS
You can use the add and select subcommands to select a specific
resource, at which point the scope changes to that resource. The end
and cancel subcommands are used to complete the resource specification,
at which time the scope is reverted back to global. Certain
@@ -823,11 +777,11 @@
automatically upon completion of a zonecfg session. Since a
configuration must be correct to be committed, this operation
automatically does a verify.
- create [-F] [ -a path |-b | -t template] [-X]
+ create [-F] [ -a path |-b | -t template]
Create an in-memory configuration for the specified zone. Use
create to begin to configure a new zone. See commit for saving this
to stable storage.
@@ -845,15 +799,11 @@
configuration.
Use the -b option to create a blank configuration. Without
arguments, create applies the Sun default settings.
- Use the -X option to facilitate creating a zone whose XML
- definition already exists on the host. The zone will be atomically
- added to the zone index file.
-
delete [-F]
Delete the specified configuration from memory and stable storage.
This action is instantaneous, no commit is necessary. A deleted
configuration cannot be reverted.
@@ -893,24 +843,20 @@
criteria. In the resource scope, any arguments are ignored, and
info displays information about the resource which is currently
being added or modified.
- remove [-F] resource-type [property-name=property-value]* (global
- scope)
- remove property-name property-value (resource scope)
+ remove resource-type{property-name=property -value}(global scope)
In the global scope, removes the specified resource. The [] syntax
- means 0 or more property name-value pairs. If you want to only
- remove a single instance of the resource, you must specify enough
- property name-value pairs for the resource to be uniquely
- identified. If no property name-value pairs are specified, all
- instances will be removed. If there is more than one pair
+ means 0 or more of whatever is inside the square braces. If you
+ want only to remove a single instance of the resource, you must
+ specify enough property name-value pairs for the resource to be
+ uniquely identified. If no property name-value pairs are specified,
+ all instances will be removed. If there is more than one pair is
specified, a confirmation is required, unless you use the -F
- option. Likewise, the -F option can be used to remove a resource
- that does not exist (that is, no error will occur). In the resource
- scope, remove the specified name-value pair.
+ option.
select resource-type {property-name=property-value}
Select the resource of the given type which matches the given