JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones
search filter icon
search icon

Document Information

Preface

Part I Resource Management

1.  Introduction to Solaris 10 Resource Management

2.  Projects and Tasks (Overview)

3.  Administering Projects and Tasks

4.  Extended Accounting (Overview)

5.  Administering Extended Accounting (Tasks)

6.  Resource Controls (Overview)

7.  Administering Resource Controls (Tasks)

8.  Fair Share Scheduler (Overview)

9.  Administering the Fair Share Scheduler (Tasks)

10.  Physical Memory Control Using the Resource Capping Daemon (Overview)

11.  Administering the Resource Capping Daemon (Tasks)

12.  Resource Pools (Overview)

13.  Creating and Administering Resource Pools (Tasks)

14.  Resource Management Configuration Example

15.  Resource Control Functionality in the Solaris Management Console

Part II Zones

16.  Introduction to Solaris Zones

17.  Non-Global Zone Configuration (Overview)

18.  Planning and Configuring Non-Global Zones (Tasks)

19.  About Installing, Halting, Cloning, and Uninstalling Non-Global Zones (Overview)

20.  Installing, Booting, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)

Zone Installation (Task Map)

Installing and Booting Zones

(Optional) How to Verify a Configured Zone Before It Is Installed

How to Install a Configured Zone

Solaris 10 8/07: How to Obtain the UUID of an Installed Non-Global Zone

Solaris 10 8/07: How to Mark an Installed Non-Global Zone Incomplete

(Optional) How to Transition the Installed Zone to the Ready State

How to Boot a Zone

How to Boot a Zone in Single-User Mode

Where to Go From Here

Halting, Rebooting, Uninstalling, Cloning, and Deleting Non-Global Zones (Task Map)

Halting, Rebooting, and Uninstalling Zones

How to Halt a Zone

How to Reboot a Zone

How to Uninstall a Zone

Solaris 10 11/06: Cloning a Non-Global Zone on the Same System

How to Clone a Zone

Solaris 10 5/09: How to Clone a Zone from an Existing Snapshot

Solaris 10 5/09: How to Use Copy Instead of ZFS Clone

Deleting a Non-Global Zone From the System

How to Remove a Non-Global Zone

21.  Non-Global Zone Login (Overview)

22.  Logging In to Non-Global Zones (Tasks)

23.  Moving and Migrating Non-Global Zones (Tasks)

24.  Solaris 10 9/10: Migrating a Physical Solaris System Into a Zone (Tasks)

25.  About Packages and Patches on a Solaris System With Zones Installed (Overview)

26.  Adding and Removing Packages and Patches on a Solaris System With Zones Installed (Tasks)

27.  Solaris Zones Administration (Overview)

28.  Solaris Zones Administration (Tasks)

29.  Upgrading a Solaris 10 System That Has Installed Non-Global Zones

30.  Troubleshooting Miscellaneous Solaris Zones Problems

Part III lx Branded Zones

31.  About Branded Zones and the Linux Branded Zone

32.  Planning the lx Branded Zone Configuration (Overview)

33.  Configuring the lx Branded Zone (Tasks)

34.  About Installing, Booting, Halting, Cloning, and Uninstalling lx Branded Zones (Overview)

35.  Installing, Booting, Halting, Uninstalling and Cloning lx Branded Zones (Tasks)

36.  Logging In to lx Branded Zones (Tasks)

37.  Moving and Migrating lx Branded Zones (Tasks)

38.  Administering and Running Applications in lx Branded Zones (Tasks)

Glossary

Index

Halting, Rebooting, and Uninstalling Zones

How to Halt a Zone

The halt procedure is used to remove both the application environment and the virtual platform for a zone. To cleanly shut down a zone, see How to Use zlogin to Shut Down a Zone.

You must be the global administrator in the global zone to perform this procedure.

  1. Become superuser, or assume the Primary Administrator role.

    To create the role and assign the role to a user, see Using the Solaris Management Tools With RBAC (Task Map) in System Administration Guide: Basic Administration.

  2. List the zones running on the system.
    global# zoneadm list -v

    You will see a display that is similar to the following:

    ID  NAME     STATUS       PATH                           BRAND      IP
     0  global   running      /                              native     shared
     1  my-zone  running      /export/home/my-zone           native     shared
  3. Use the zoneadm command with the -z option, the name of the zone, for example, my-zone, and the halt subcommand to halt the given zone.
    global# zoneadm -z my-zone halt
  4. List the zones on the system again, to verify that my-zone has been halted.
    global# zoneadm list -iv

    You will see a display that is similar to the following:

    ID  NAME     STATUS       PATH                           BRAND      IP
     0  global   running      /                              native     shared
     -  my-zone  installed    /export/home/my-zone           native     shared
  5. Boot the zone if you want to restart it.
    global# zoneadm -z my-zone boot
Troubleshooting

If the halt operation fails, see Zone Does not Halt for troubleshooting tips.

How to Reboot a Zone

You must be the global administrator in the global zone to perform this procedure.

  1. Become superuser, or assume the Primary Administrator role.

    To create the role and assign the role to a user, see Using the Solaris Management Tools With RBAC (Task Map) in System Administration Guide: Basic Administration.

  2. List the zones running on the system.
    global# zoneadm list -v

    You will see a display that is similar to the following:

    ID  NAME     STATUS       PATH                           BRAND      IP
     0  global   running      /                              native     shared
     1  my-zone  running      /export/home/my-zone           native     shared
  3. Use the zoneadm command with the -z reboot option to reboot the zone my-zone.
    global# zoneadm -z my-zone reboot
  4. List the zones on the system again to verify that my-zone has been rebooted.
    global# zoneadm list -v

    You will see a display that is similar to the following:

    ID  NAME     STATUS       PATH                           BRAND      IP
     0  global   running      /                              native     shared
     2  my-zone  running      /export/home/my-zone           native     shared

    Tip - Note that the zone ID for my-zone has changed. The zone ID generally changes after a reboot.


How to Uninstall a Zone


Caution

Caution - Use this procedure with caution. The action of removing all of the files in the zone's root file system is irreversible.


The zone cannot be in the running state. The uninstall operation is invalid for running zones.

You must be the global administrator in the global zone to perform this procedure.

  1. Become superuser, or assume the Primary Administrator role.

    To create the role and assign the role to a user, see Using the Solaris Management Tools With RBAC (Task Map) in System Administration Guide: Basic Administration.

  2. List the zones on the system.
    global# zoneadm list -v

    You will see a display that is similar to the following:

    ID  NAME     STATUS       PATH                           BRAND      IP
     0  global   running      /                              native     shared
     -  my-zone  installed    /export/home/my-zone           native     shared
  3. Use the zoneadm command with the -z uninstall option to remove the zone my-zone.

    You can also use the -F option to force the action. If this option is not specified, the system will prompt for confirmation.

    global# zoneadm -z my-zone uninstall -F
  4. List the zones on the system again, to verify that my-zone is no longer listed.
    global# zoneadm list -v

    You will see a display that is similar to the following:

    ID  NAME     STATUS       PATH                           BRAND      IP
     0  global   running      /                              native     shared
Troubleshooting

If a zone uninstall is interrupted, the zone is left in the incomplete state. Use the zoneadm uninstall command to reset the zone to the configured state.

Use the uninstall command with caution because the action is irreversible.