OpenSolaris
Collectives
Discussions
Documentation
Download
Source Browser
Free CD
Log-in
|
en
Project zonemgr
:
Documentation
>
Version 1.8 Help
Top Menu
Show
:
Comments
Attachments
History
Information
Print
:
Print
Print preview
Export as PDF
Export as RTF
Export as HTML
Export as XAR
Wiki code for
Version 1.8 Help
Hide Line numbers
1: == Zone Manager Version 1.8 Help 2: 3: {{{ 4: 5: System Administration Commands zonemgr(1M) 6: 7: NAME 8: zonemgr - set up and manage zones 9: 10: SYNOPSIS 11: Normal usage: 12: zonemgr -a <action> [options] 13: 14: See proper usage: 15: zonemgr -h 16: 17: Display the version: 18: zonemgr -v 19: 20: Display the license: 21: zonemgr -l 22: 23: DESCRIPTION 24: The purpose of zonemgr is to simplify Solaris 10 zones 25: management. There are many pre-defined actions that can be 26: applied to one or more zones depending on the action. 27: 28: OPTIONS 29: The following options are supported: 30: 31: -a <action> Specify the action to be performed 32: 33: -n <zonename> Specify the name of the zone 34: 35: -h See this usage information 36: 37: -l See the GPL v2 license 38: 39: -v See the version number of this script 40: 41: ACTIONS 42: Actions which can result in destructive actions or loss 43: of work have a -F flag to force the action. 44: 45: The following actions are supported: 46: 47: info -n <zonename> 48: The "info" action displays configuration information 49: about a zone. 50: 51: add -n <zonename> -z <dir> [add_options] 52: The "add" action adds a new zone. 53: 54: The following add_options are required: 55: 56: -z "<dir>" Base directory for this zone. 57: 58: -P "<file or password>" 59: Unencrypted password of the root user 60: of this new non-global zone. The 61: password can either be specified in 62: a file or as a quoted string. 63: 64: The following add_options can be used as substitutes for 65: the required options: 66: 67: -Z "<dir>" Root zone directory for this zone. 68: This is an alternate way from 69: -z <dir> of specifying the zones root 70: directory. 71: 72: -E "<file or password>" 73: This is an alternate way from 74: -P <password> of specifying the non- 75: global root user’s password via an 76: encrypted format. The encrypted 77: password can either be specified in 78: a file or as a quoted string. You 79: can copy and paste the user’s 80: password from /etc/shadow). 81: 82: The following optional add_options are supported: 83: 84: -t <w or s> Type of zone where w=Whole Root and 85: s=Sparse Root. A sparse root zone 86: inherits the following directories 87: from the global zone: /lib, /usr, 88: /sbin, and /platform. A whole root 89: zone does not inherit any directories 90: from the global zone. The default 91: value is sparse root (s). 92: 93: -A Disable autoboot (prevent zone from 94: booting when the server reboots). 95: 96: -I "<IP Address>|<Interface>|<Netmask>|<Host name>" 97: IP Address of the non-global zone 98: plus the network interface for that 99: IP address, the netmask in CIDR 100: format, and the host name for that IP 101: address. 102: 103: If not specified the default network 104: interface is the first non-loopback 105: interface listed by ifconfig. The 106: default netmask is the netmask that 107: corresponds to the IP address that 108: you specify. There is no default host 109: name. 110: 111: Note that a zone can be created 112: without a network address. 113: 114: -D "<domain>" DNS Domain Name. If a domain is 115: specified, then dns name servers must 116: also be specified. Note also that 117: the fully qualified host name of the 118: non-global zone must be resolvable by 119: the naming service. 120: 121: -d "<ns1>,<ns2>,.." 122: Ordered list of DNS Name Servers. If 123: domain name servers are specified the 124: domain name must also be specified. 125: Note also that the fully qualified host 126: name of the non-global zone must be 127: resolvable by the naming service. 128: 129: -r "<gdir>|<ldir>" Loopback mount global zone directory 130: (gdir) on a non-global zone directory 131: (ldir) in read only mode. 132: 133: -w "<gdir>|<ldir>" Loopback mount global zone directory 134: (gdir) on a non-global zone directory 135: (ldir) in read write mode. 136: 137: -N "<server>|<export_dir>|<mount_dir>|<options>" 138: Mount an NFS directory where <server> 139: is the NFS server host name or IP 140: address, <export_dir> is the NFS 141: exported directory, <mount_dir> is 142: the mount point within the non-global 143: zone to mount the NFS filesystem, and 144: <options> are the NFS mount options. 145: 146: Note that zones only supports 147: mounting an NFS filesystem from a 148: host on a separate physical server. 149: e.g. You cannot at the present time 150: mount an NFS filesystem from another 151: zone on this physical server. 152: 153: -B "<name>|<subset>|<img>" 154: Make the zone into a Linux branded 155: zone where <name> is the brand name, 156: <subset>, is the brand subset, and 157: <img> is the path and file name of 158: the brand archive. If a media drive 159: is being used, <img> is the path to 160: the mounted media. e.g. 161: /cdrom/cdrom0 162: 163: -R "<dir>|<shell>" 164: Custom home directory (<dir>) and 165: a shell (<shell>) for the root user 166: of the non-global zone. 167: 168: -C "<pre or post boot>|<source>|<destination>" 169: or 170: -C "<source>|<destination>" 171: File/Directory to recursively copy 172: from the global zone into the non- 173: global zone. The <pre or post boot> 174: option defines if you want the source 175: copied before the non-global zone is 176: booted (pre) or after (post) the zone 177: has completed its final boot. 178: The <destination> option is used to 179: specify a different destination location 180: in the non-global zone that presently 181: exists in the global zone. 182: 183: -s "<method>|<method_arguments>" 184: This feature hardens the non-global 185: zone by disabling (or enabling) 186: un-necessary operating system 187: services of the non-global zone 188: according to the method specified. 189: Hardening methods and corresponding 190: arguments are as follows: 191: 192: Secure by default: 193: Method: netservices or sbd 194: Arguments: 195: limited - Eliminate un-necessary services 196: open - Enable standard services 197: 198: Service Management Facility Site 199: Profile: 200: Method: smf 201: Argument: <fullpath>/<smf_xml_file> 202: 203: JumpStart Architecture and Security 204: Scripts (aka Solaris Security 205: Toolkit): 206: Method: jass 207: Argument: <jass_driver_name> 208: 209: Basic service management: 210: Method: basic or enable or disable or lock or unlock 211: Argument: One of the following: 212: disable 213: lock 214: enable 215: unlock 216: disable|<service_list_file> 217: lock|<service_list_file> 218: enable|<service_list_file> 219: unlock|<service_list_file> 220: 221: -S "<service>" Restart specified service after 222: adding zone. A special case is 223: ’reboot’ to restart all services in 224: the zone. 225: 226: -M [basic|<file>] Minimize the non-global zone by 227: either excluding or removing un- 228: necessary packages. The optional 229: <file> is a file containing a list 230: of packages that you would like 231: removed from the zone. If no <file> 232: is specified, the following 233: categories will be removed with 234: pkgrm -Y <category>: 235: JDS4 JDS3 JDS JDSosol GNOME2 CTL 236: ALE APOC CTL EVO146 G11NTOLS GLOW 237: JAI JAVAAPPS JDIC 238: 239: -X "<command> <args>" 240: Runs <command> inside the non-global 241: command once it is successfully 242: created. Note that you may need to 243: include the full path to the command 244: as well. And you can pass <args> 245: (arguments) to the command if you 246: include them in the quoted the 247: command. 248: 249: -G <package> Fully automates the installation of 250: specified BlastWave package. For a 251: full list of available BlastWave 252: packages, visit the following URL: 253: http://blastwave.org/packages 254: 255: -L "<priv>[,<priv>,...]" 256: Specifies the limit set for privileges 257: allowed in this zone. See manual page 258: privileges for more info and list of 259: available privileges. 260: 261: del -n <zonename> [-F] 262: The del action deletes an existing zone 263: 264: The "del" action supports the following optional option: 265: 266: -F Don’t confirm an action; Just do it. 267: 268: modify -n <zonename> 269: The "modify" action enables you to add, modify and delete 270: select zone properties. Zone properties that can be modified 271: include the following: 272: 273: Modify the zone name: 274: -m "zonename:<value>" 275: 276: Modify the comment that describes the zone: 277: -m "comment:<value>" 278: 279: Modify the autoboot value. The autoboot property determines 280: whether or not the zone will boot when the global zone is 281: booted. 282: -m "autoboot:<true|false>" 283: 284: Modify the boot arguments of the zone: 285: -m "bootargs:<value>" 286: 287: Modify an existing filesystem (fs) property: 288: -m "fs:<dir>|<resource_type>:<value>" 289: Where net resource types include the following: 290: dir - Global zone directory 291: special - Non-global zone directory 292: options - Filesystem mount options 293: 294: Modify an existing network property: 295: -m "net:<ipaddr/netmask>|<resource_type>:<value>" 296: Where net resource types include the following: 297: address - Network address and netmask in CIDR format 298: physical - The network interface 299: 300: Zone properties that can be deleted include the following: 301: 302: Modify an existing filesystem property: 303: -m "del:fs:<dir_value>" 304: 305: Modify an existing network property: 306: -m "del:net:<address/cidr_netmask>" 307: 308: In addition to modifying and deleting existing properties, 309: you can also add a few types of properties. The arguments 310: used to add these properties are listed below. 311: 312: -I "<IP Address>|<Interface>|<Netmask>|<Host name>" 313: IP Address of the non-global zone 314: plus the network interface for that 315: IP address, the netmask in CIDR 316: format, and the host name for that IP 317: address. 318: 319: If not specified the default network 320: interface is the first non-loopback 321: interface listed by ifconfig. The 322: default netmask is the netmask that 323: corresponds to the IP address that 324: you specify. There is no default host 325: name. 326: 327: Note that a zone can be created 328: without a network address. 329: 330: -r "<gdir>|<ldir>" Loopback mount global zone directory 331: (gdir) on a non-global zone directory 332: (ldir) in read only mode. 333: 334: -w "<gdir>|<ldir>" Loopback mount global zone directory 335: (gdir) on a non-global zone directory 336: (ldir) in read write mode. 337: 338: -w "zfs|<dir>|zpool|zname" 339: Create a ZFS filesystem using legacy mode 340: and mount the ZFS filesystem within the 341: zone. Note that this filesystem is not 342: mounted in the global zone. However, the 343: root user in the global zone can access 344: the contents of the mounted zfs 345: filesystem because the root mount point of 346: the non-global zone is accessible as a 347: directory in the global zone. 348: dir = The mount point inside the non-global 349: zone 350: zpool = The ZFS pool name 351: zname = The ZFS filesystem name 352: 353: -C "<pre or post boot>|<source>|<destination>" 354: or 355: -C "<source>|<destination>" 356: File/Directory to recursively copy 357: from the global zone into the non- 358: global zone. The <pre or post boot> 359: option defines if you want the source 360: copied before the non-global zone is 361: booted (pre) or after (post) the zone 362: has completed its final boot. 363: The <destination> option is used to 364: specify a different destination location 365: in the non-global zone that presently 366: exists in the global zone. 367: 368: -s "<method>|<method_arguments>" 369: This feature hardens the non-global 370: zone by disabling (or enabling) 371: un-necessary operating system 372: services of the non-global zone 373: according to the method specified. 374: Hardening methods and corresponding 375: arguments are as follows: 376: 377: Secure by default: 378: Method: netservices or sbd 379: Arguments: 380: limited - Eliminate un-necessary services 381: open - Enable standard services 382: 383: Service Management Facility Site 384: Profile: 385: Method: smf 386: Argument: <fullpath>/<smf_xml_file> 387: 388: JumpStart Architecture and Security 389: Scripts (aka Solaris Security 390: Toolkit): 391: Method: jass 392: Argument: <jass_driver_name> 393: 394: Basic service management: 395: Method: basic or enable or disable or lock or unlock 396: Argument: One of the following: 397: disable 398: lock 399: enable 400: unlock 401: disable|<service_list_file> 402: lock|<service_list_file> 403: enable|<service_list_file> 404: unlock|<service_list_file> 405: 406: -M [basic|<file>] Minimize the non-global zone by 407: either excluding or removing un- 408: necessary packages. The optional 409: <file> is a file containing a list 410: of packages that you would like 411: removed from the zone. If no <file> 412: is specified, the following 413: categories will be removed with 414: pkgrm -Y <category>: 415: JDS4 JDS3 JDS JDSosol GNOME2 CTL 416: ALE APOC CTL EVO146 G11NTOLS GLOW 417: JAI JAVAAPPS JDIC 418: 419: -X "<command> <args>" 420: Runs <command> inside the non-global 421: command once it is successfully 422: created. Note that you may need to 423: include the full path to the command 424: as well. And you can pass <args> 425: (arguments) to the command if you 426: include them in the quoted the 427: command. 428: 429: -G <package> Fully automates the installation of 430: specified BlastWave package. For a 431: full list of available BlastWave 432: packages, visit the following URL: 433: http://blastwave.org/packages 434: 435: list 436: The "list" action lists all current zones 437: 438: clone -n <zonename> -y <sourceZoneName> [clone_options] 439: The "clone" action clones an existing zone into a 440: new zone. The new zone can be tailored via the 441: optional arguments used when creating a new zone. 442: 443: The "clone" action supports the following required 444: options: 445: 446: The following clone_options are required: 447: 448: -z "<dir>" Base directory for this zone. 449: 450: -P "<file or password>" 451: Unencrypted password of the root user 452: of this new non-global zone. The 453: password can either be specified in 454: a file or as a quoted string. 455: 456: The following clone_options can be used as substitutes for 457: the required options: 458: 459: -Z "<dir>" Root zone directory for this zone. 460: This is an alternate way from 461: -z <dir> of specifying the zones root 462: directory. 463: 464: -E "<file or password>" 465: This is an alternate way from 466: -P <password> of specifying the non- 467: global root user’s password via an 468: encrypted format. The encrypted 469: password can either be specified in 470: a file or as a quoted string. You 471: can copy and paste the user’s 472: password from /etc/shadow). 473: 474: The following optional clone_options are supported: 475: 476: -F Don’t confirm an action; Just do it. 477: 478: -t <w or s> Type of zone where w=Whole Root and 479: s=Sparse [default: s] 480: 481: -d "<ns1>,<ns2>,.." 482: Ordered list of DNS Name Servers 483: 484: -D "<domain>" DNS Domain Name 485: 486: -A Disable autoboot (prevent zone from 487: booting on system reboots) 488: 489: -I "<IP Address>|<Interface>|<Netmask>|<Host name>" 490: IP Address of the non-global zone 491: plus the network interface for that 492: IP address, the netmask in CIDR 493: format, and the host name for that IP 494: address. 495: 496: If not specified the default network 497: interface is the first non-loopback 498: interface listed by ifconfig. The 499: default netmask is the netmask that 500: corresponds to the IP address that 501: you specify. There is no default host 502: name. 503: 504: Note that a zone can be created 505: without a network address. 506: 507: -r "<gdir>|<ldir>" Mount global zone directory (gdir) on 508: a non-global zone directory (ldir) in 509: read only mode 510: 511: -w "<gdir>|<ldir>" Mount global zone directory (gdir) on 512: a non-global zone directory (ldir) in 513: read write mode 514: 515: -N "<server>|<export_dir>|<mount_dir>|<options>" 516: Mount an NFS directory where <server> 517: is the NFS server host name or IP 518: address, <export_dir> is the NFS 519: exported directory, <mount_dir> is 520: the mount point within the non-global 521: zone to mount the NFS filesystem, and 522: <options> are the NFS mount options. 523: 524: Note that zones only supports 525: mounting an NFS filesystem from a 526: host on a separate physical server. 527: e.g. You cannot at the present time 528: mount an NFS filesystem from another 529: zone on this physical server. 530: 531: -p "<resource>|<resource_arg>" 532: <resource> can be either cpu or ram. 533: 534: <resource_arg> is either number of processors 535: or Mb of RAM depending on the resource specified. 536: 537: Processor count enables you to specify the number 538: of processors that will be assigned to this zone. 539: 540: (Not yet available) RAM count enables you to 541: specifiy the maximum amount of RAM in bytes that 542: this zone can use. 543: 544: move -n <zonename> -Z <newzonepath> [-F] 545: The "move" action moves an existing zone from its current 546: directory to a new directory. 547: 548: The "move" action supports the following required 549: options: 550: 551: The following options are required: 552: 553: -Z "<dir>" New directory for this zone. 554: 555: detach -n <zonename> [-F] 556: The "detach" action detaches a zone so that it can be 557: attached to a different server. 558: 559: The "detach" action supports the following required 560: options: 561: 562: The following options are required: 563: 564: -F Don’t confirm an action; Just do it. 565: 566: attach -n <zonename> [-F] 567: The "attach" action attaches a detached zone. 568: 569: The "attach" action supports the following required 570: options: 571: 572: The following options are required: 573: 574: -F Don’t confirm an action; Just do it. 575: 576: shutdown -n <zonename> [-F] 577: The "shutdown" action shuts down a zone. 578: 579: The "shutdown" action supports the following optional 580: option: 581: 582: -F Don’t confirm an action; Just do it. 583: 584: boot -n <zonename> 585: The "boot" action boots a zone. 586: 587: The "boot" action supports the following optional 588: option: 589: 590: -F Don’t confirm an action; Just do it. 591: 592: reboot -n <zonename> [-F] 593: The "reboot" action reboots a zone. 594: 595: The "reboot" action supports the following optional 596: option: 597: 598: -F Don’t confirm an action; Just do it. 599: 600: halt -n <zonename> [-F] 601: The "halt" action halts a zone. 602: 603: The "halt" action supports the following optional 604: option: 605: 606: -F Don’t confirm an action; Just do it. 607: 608: only -n <zonename> [-F] 609: The "only" action halts all non-global zones but those 610: specified by -n "<zonename> <zonename>" and boot any of 611: these specified zones that are not currently running. 612: 613: There are two zone name special cases. 614: bootall 615: This zone name makes sure all non-global zones 616: are booted. 617: 618: haltall 619: This zone name makes sure all zones are halted. 620: 621: The "only" action supports the following optional 622: option: 623: 624: -F Don’t confirm an action; Just do it. 625: 626: runcmd -n <zonename> -X "<cmd_with_args>" [-F] 627: The "runcmd" action runs commands specified with the 628: -X "<cmd_with_args>" flags in all non-global zones 629: specified by -n "<zonename> <zonename>" flag. 630: 631: There is one zone name special case. 632: all 633: This zone name runs the specified commands on 634: all non-global zones. 635: 636: The following options are required: 637: 638: -n "<zone1> <zone2> ..." 639: Specify the name of the zones 640: 641: -X <command> Runs <command> inside the non-global 642: command once it is successfully 643: created. Note that you may need to 644: include the full path to the command 645: as well. 646: 647: The "runcmd" action supports the following optional 648: option: 649: 650: -F Don’t confirm an action; Just do it. 651: 652: zcontainer -n <zonename> -p "<resource>|<resource_arg>" 653: 654: The "zcontainer" action transforms the zone into a container 655: by applying resource controls to the zone. 656: 657: The following option is required: 658: 659: -p "<resource>|<resource_arg>" 660: <resource> can be either cpu or ram. 661: 662: <resource_arg> is either number of processors 663: or Mb of RAM depending on the resource specified. 664: 665: Processor count enables you to specify the number 666: of processors that will be assigned to this zone. 667: 668: (Not yet available) RAM count enables you to 669: specifiy the maximum amount of RAM in bytes that 670: this zone can use. 671: 672: The "zcontainer" action supports the following optional 673: option: 674: 675: -F Don’t confirm an action; Just do it. 676: 677: EXAMPLES 678: 679: Example 1: Create A Zone 680: 681: The following command will create a non-global zone named 682: m1. 683: 684: # zonemgr -a add -n m1 -z "/zones" -P "abc123" \ 685: -I "192.168.0.10|hme0|24|myzonehost" 686: 687: Example 2: Delete A Zone 688: 689: The following command will delete the non-global zone named 690: m1 and it will not be prompted to continue because the 691: action is forced with the -F flag. 692: 693: # zonemgr -F -a del -n m1 694: 695: Example 3: Create A Zone With Multiple IP Addresses 696: 697: The following command will create a non-global zone named 698: m1 with three IP addresses where each IP address is configured 699: on its own network interface. 700: 701: # zonemgr -a add -n m1 -z "/zones" -P "abc123" \ 702: -I "192.168.0.10|hme0|24|myzonehost1" \ 703: -I "192.168.5.27|bge0|24|myzonehost2" \ 704: -I "192.168.10.5|bge1|24|myzonehost3" 705: 706: Example 4: A Complex Example 707: 708: The following command will perform the details stated below. 709: # zonemgr -a add -n m2 -t w -z "/zones" \ 710: -P "abc123" -R /root \ 711: -I "192.168.0.10|hme0|24|myzonehost" \ 712: -r "/ds/build11/bits|/bits" \ 713: -w "/zones/m2|/ds/m2" \ 714: -s "basic|lock" -S ssh \ 715: -C /etc/ssh/sshd_config -C /etc/resolv.conf \ 716: -C /etc/nsswitch.conf \ 717: -L default,dtrace_proc,dtrace_user 718: 719: 1. Create a whole root zone named m2 in /zones/m2. 720: 2. Set the root password of that zone to abc123. 721: 3. Set the home directory of the root user of the non-global 722: zone to /root. 723: 4. Set the IP address of the zone to 192.168.0.10, the 724: netmask to 255.255.255.0, assign it to interface hme0, and 725: assign it a host name of myzonehost. 726: 5. Read only mount /ds/build11/bits from the global zone to 727: /bits in the non-global zone. 728: 6. Read write mount /zones/m2 from the global zone to /ds/m2 729: in the non-global zone. 730: 7. Disable all un-necessary services in the non-global zone 731: and restart the ssh service once the lockdown is complete. 732: 8. Copy the /etc/ssh/sshd_config, /etc/resolv.conf, and 733: /etc/nsswitch.conf files from the global zone to the 734: non-global zone 735: 9. Add the dtrace_proc and dtrace_user privileges to the 736: non-global zone 737: 738: Example 5: List All Zones 739: 740: The following command will list all available zones. 741: 742: # zonemgr -a list 743: 744: Example 6: Reboot A Zone 745: 746: The following command will reboot non-global zone m1. 747: 748: # zonemgr -a reboot -n m1 749: 750: Example 7: Disable Un-necessary Services 751: 752: The following command will disable all un-necessary services 753: of non-global zone m1. 754: 755: # zonemgr -a modify -n m1 -s "basic|lock" 756: 757: Example 8: Enable Un-necessary Services 758: 759: The following command will enable all un-necessary services 760: of non-global zone m1. 761: 762: # zonemgr -a modify -n m1 -s "basic|unlock" 763: 764: Example 9: Manage State Of Multiple Zones 765: 766: The following command will halt all non-global zones but 767: those specified by the -n parameter and will boot any of the 768: specified zones that are not currently running. 769: 770: # zonemgr -a only -n "m1 m2" 771: 772: Example 10: Halt All Zones 773: 774: The following command will halt all non-global zones. 775: 776: # zonemgr -a only -n "haltall" 777: 778: Example 11: Boot All Zones 779: 780: The following command will boot all non-global zones. 781: 782: # zonemgr -a only -n "bootall" 783: 784: Example 12: Creating A BrandZ (e.g. Linux) Zone 785: 786: The following command will add a BrandZ zone 787: # zonemgr -a add -n m1 -z "/zones" -P "abc123" \ 788: -I "192.168.0.10|hme0|24|myzonehost" \ 789: -B "SUNWlx|all|/data/brandz/centos_fs_image.tar" 790: 791: The parameters passed to -B break down as follows: 792: * SUNWlx: The zone brand (only lx is currently supported) 793: 794: * all: The brand subset to install. Valid values include 795: desktop, applications, server, development, system, 796: and all. I don’t yet have an idea as to how this 797: option will impact other distributions that folks come 798: up with. These options may or may not be valid. TBD. 799: 800: * /data/brandz/centos_fs_image.tar: The path to the 801: brand bits. I simply pointed them to the BrandZ 802: community’s CentOS image. 803: 804: Example 13: Create A Zone AND Install MySQL5 From BlastWave 805: 806: The following command will add a zone named m1, download and 807: install mysql5 and all requisite bits from Blastwave.org, 808: and install all those bits in the proper order in the m1 809: zone. 810: # zonemgr -a add -n m1 -z "/zones" -P "abc123" \ 811: -I "192.168.0.10|hme0|24|myzonehost" -G "mysql5" 812: 813: Example 14: Add a ZFS filesystem to an existing zone 814: 815: The following command will create a legacy mode ZFS 816: filesystem from the myzfspool pool, set the ZFS mount 817: point to /zfsdata, and mount that filesystem exclusively 818: within the m1 zone. 819: # zonemgr -a modify -n m1 -w "zfs|/zfsdata|myzfspool" 820: 821: Example 15: Move a zone 822: 823: The following command will move a zone to a new directory. 824: # zonemgr -a move -n m1 -Z /zones/newm1 825: 826: Example 16: Detach and attach a zone 827: 828: The following two commands will detach a zone and then 829: re-attach it. 830: # zonemgr -a detach -n m1 -F 831: # zonemgr -a attach -n m1 -F 832: 833: Example 17: Clone a zone 834: 835: The following command will move a zone to a new directory. 836: # zonemgr -a clone -n m1 -y m1clone -Z /zones/m1clone \ 837: -P "pw" 838: 839: Example 18: Apply CPU containment to a zone 840: 841: The following command will put a zone into a CPU processor 842: set that will limit all process of the zone to running on 843: the specified number of CPUs. 844: # zonemgr -a zcontainer -n m1 -p "cpu|1" 845: 846: NOTES 847: Note that most parameters are multivalued. In other words, 848: you can specify the same parameter multiple times. For 849: example, to mount the /data1 and /data2 directories in read 850: only mode from the global zone to the non-global zone, add 851: the following to the add action: 852: -r "/data1" -r "/data2" 853: 854: EXIT STATUS 855: The following exit values are returned: 856: 857: 0 Successful completion. 858: 859: 1 An error occurred. 860: 861: 2 Invalid usage. 862: 863: SEE ALSO 864: svcs(1), zlogin(1), zonename(1), svcadm(1M), svc.startd(1M) 865: and init(1M), svc.startd(1M), zoneadm(1M), zonecfg(1M), 866: attributes(5), smf(5), zones(5) 867: 868: }}}
Search
Collectives
Community Group
Academic and Research
Accessibility
Advocacy
Appliances
Approachability
Architecture Process and Tools
BrandZ
Chinese Users
Community Advisory Board
Databases
Desktop
Device Drivers
Distribution
Documentation
DTrace
Emerging Platforms
Fault Management
Games on OpenSolaris
HA Clusters
HPC Developer
Installation and Packaging
Internationalization and Localization
Laptop
Logical Domains
Modular Debugger (MDB)
Networking
NFS
Observability
OpenSolaris Governing Board (OGB)
OpenSolaris Printing
OS/Net (ON)
Performance
Power Management
PowerPC
Security
Service Management Facility (smf(5))
Software Porters
Solaris Volume Manager
Storage
Systems Administration Community Group
Testing
Tools Home
Unix File Systems (UFS)
Website Community
X Window System
Xen
ZFS
Zones
Project
ADSL Modem Enhancement
ARC Process Definition
ARM Platform Port
Automatic Data Migration
BIND Update
Bluetooth Stack & Drivers
Brocade FC HBA - Initiator
Brocade FC HBA - Target
Brussels - unified network link configuration
Caiman, Solaris Install Revisited
Celeste
Český portál
Chime Visualization Tool for DTrace
CIFS client for Solaris
CIFS Server
Clearview: Network Interface Coherence
Cluster Agent: Informix Dynamic Server
Cluster Agent: OpenSolaris Container
Cluster Agent: OpenSolaris xVM
Cluster Agent: Oracle E-Business Suite
Cluster agent: PostgreSQL
Cluster Agent: Samba
Cluster Agent: Tomcat
CMT
Coarse Data Flow Parallelism
Colorado: Open HA Cluster on OpenSolaris
Command Assistant
Common Array Manager
Companion - /opt/sfw: Free and Open Source software
COMSTAR: Common Multiprotocol SCSI Target
Content
Contest
CPU Observability
Credentials Process Groups
Crossbow: Network Virtualization and Resource Control
Crypto KMS Agent Toolkit
Cryptographic Framework
Data Migration Manager
Data Tethers
Deutsches Portal
Device Detection Tool
Device Driver Utility
Device Manager
Device Mapper
Direct Rendering Infrastructure & 3D drivers
DTrace Guide
Duckwater: Simplified name services management
Easy Tools
Emancipation
Emulex Fibre Channel Device Driver
Emulex Advanced Ethernet Device Driver
Enable/Enhance Solaris support for Intel Platform
Enhance the support of USB webcams
Enhanced SMF Profiles
Enhancements for AMD-based Platforms
Erlang DTrace Integration
Ethernet bridge module for Solaris
Evaluate Conary
Events Registry
Ext3 file system support
F/OSS Package Base
Facilitation
Fibre Channel over Ethernet
Fine Grained Access Policy (FGAP)
Fingerprint Authentication
Flexible Mandatory Access Control
Forensic Tools
Fully Open X Project
Fuse on Solaris
gcore
Generic Machine Check Architecture Improvements
Google SOC
HA-JBoss
HA-MySQL
Hadoop Live CD
Hitachi
HoneyComb Fixed Content Storage
HPC Stack
Image Packaging System
Improved Performance MIB
Indiana
Innovation Awards
Input Method
Intel Graphics
Internet Key Exchange, version 2
Interrupt Resource Management
IP Datapath Refactoring
IP over Infiniband
IPsec Tunnel Reform
iSCSI Extensions for Remote DMA (iSER)
iSNS Server
JeOS - Just enough Operating System
JKstat - a java binding for libkstat
Journaled File System (JFS)
K Desktop Environment
Kerberos
Kernel Sockets
Kernel SSL Enhancements
Key Management Framework
Korn Shell 93 integration/migration project
Labeled IPsec
LatencyTOP
Layer 2 Filtering
LDoms Manager
Lending
libMicro - portable microbenchmarks
Link Layer Discovery
Live Media: Technologies for distributions running from CD and other media
Locale Data
lofi compression and cryptography support
lx64 brand
Media Management System
Mega_sas
Mexico
MilaX minimal Live Distribution
MIPS Platform Port
Mozilla DTrace
MRSL.NONsharedDevice
Multi-lingual Glossary
Multi-pathing software (MPxIO)
Multiple disk sector size support
Multiple DOI
Muskoka: An open repository for OpenSolaris technical content
Navigator
Nemo: A Framework for High-Performance Networking
Network Auto-Magic
Network Data Management Protocol
Network MIBs
Network Storage
Network Time Protocol (NTP)
Nevada Globalization
New Design of 4over6 Mechanism Based on OpenSolaris
NFS RDMA transport update and performance analysis
NFS Server in non-Global Zones
NFS version 4.1 pNFS
NFSv4 namespace extensions
Nightingale: Port Songbird to OpenSolaris
NPort ID Virtualization (NPIV)
NUMA
Object Storage Device (OSD) support for Solaris
OHACGE Script Based Plug-in
ON/Nevada (ONNV) Project
Open Development Infrastructure
Open HA Cluster Utilities
Open Sound System
OpenGrok
OpenPegasus CIM Server
OpenRTI
OpenSolaris Busybox
OpenSolaris Desktop
OpenSolaris Hispano
OpenSolaris Security Audit
OpenSolaris support for the QEMU processor emulator: host and guest
PEF: Packet Event Framework
Performance Wrappers
Pkgfactory
Polski Portal
Portail Francophone
Portal Brasil
Portals
Power Management Usability Interfaces
Presto: Automatic Printing Configuration
Printable Many Page Solaris Manuals
Promise SuperTrak RAID HBA Driver
QLogic Converged Network Adapter GLDv3 NIC Driver
Quagga Routing Protocol Suite Integration
RAID Configuration Utility
RBridge (IETF TRILL) support
RDMA Offload Framework
Reno: Login Process Enhancements for Interop
Resource Management
s10brand
SAM/QFS
SCM Migration Project
SCSI RDMA Protocol
SDcard Drivers
Sensor Abstraction Layer
Session Initiation Protocol
SFW
Shell: bourne shell, korn shell, C shell, etc.
Sierra: Intel WiFi Chipsets Support
Simple Panels
SM-HBA Based SAS HBA Management
SMF Documentation
Solaris iSCSI Target
Solaris PowerPC Port
SourceJuicer
Sparks: name service switch/nscd enhancements
Squashfs
Star integration/migration project
Starfish
Starter Kit
Storage Power Management
Sun Security Toolkit
Sun StorageTek Availability Suite
Support for OpenFabrics User Verbs / API on OpenSolaris OS
Support gcc4/GCCfss in Solaris
Suspend/Resume
SVR4 Packaging
Systemz
Tamarack: Removable Media Enhancements in Solaris
Tesla: OpenSolaris Enhanced Power Management
Test Development
Tickless Kernel Architecture
TIPC
Trademarks
Trusted networking interface policy database for Trusted Extensions
Trusted Platform Module support
Use Case
Validated Execution Project
Virtual Console
Virtual Network Machines
Visual Panels
Visualization for HPC
Volo
VRRP: Virtual Router Redundancy Protocol Implementation
VSCAN service
Web Stack
Website
Winchester: Schema mapping and ID mapping for AD Interoperability
Wireless USB Support
Wireless Wide Area Network
X Consolidation
x86 Generic FMA Topology Enumerator
Xen Gate
Xfce: A lightweight desktop environment
ZFS Boot and Install
ZFS on disk encryption support
Zone Manager
Zone Statistics
Русский портал
البوابة العربية
भारतीय पोर्टल
中国门户
日本ポータル
한국 포탈
User Group
Adelaide
Argentina
Arizona
Atlanta
Baltimore-Washington
Bangalore
Bangkok
Bangladesh
Beijing
Bélem
Berlin
Bhimavaram
Bloomington
Campus Ambassadors
Capital Region
Cardiff
Charlotte
Chengdu
Chennai
Chihuahua
Chile
Cleveland
Colombia
Columbus
Connecticut
Cracow
Czech
Dallas/Ft. Worth
Danish
Delaware
Edinburgh
Egypt
Finland
Florida
Front Range
FuZhou
Great Lakes
Greece
Hangzhou
Hawaii
HeFei
Houston
Hyderabad
Indonesia
Irish
Israel
Italian
Jinan
Kabul
Kansas City
Latvia
London
Madurai
Manchester
Mato Grosso
Melbourne
Minas Gerais
Minnesota
Montreal
Moscow
Mumbai
Munich
NEA
Netherlands
New England
New York City
New Zealand
NIT Hamirpur
Noroeste
Oklahoma City
Osnabrück
Peru
Philadelphia
Piaski
Pittsburgh
Porto Alegre
Puget Sound
Pune
Queensland
Research Triangle Park
Romania
Russia
San Antonio
San Diego
San Francisco
São Paulo
Scottish
Serbia
Shanghai
Shenzhen
Silicon Valley
Singapore
Slovak
South African
Southern Connecticut
St. Louis
Sweden
Switzerland
Sydney
Szczecin
Taiwan
Tecum
Thames Valley
Tokyo
Toronto
Trondheim
Tulsa
Turkey
Ukraine
University of Melbourne
Vale do Paraíba
Vancouver
Venezuela
Welsh - Cymru
Wisconsin
Xi'an
Subsites
Code Reviews
Code Repositories
Package Search
Bugster
Bugzilla
Test Machines
Planet
Mailing Lists
Elections & Polls
ARC Case Logs
Source Juicer
Package Factory
User Authentication
Project zonemgr Pages
Governance
Other Zones Management Projects
Thanks
Bugs
Version Changelog
Documentation
1.8 Release Notes
Version 1.8 Help
Version 2.0.6 Help
Files
RFE List