Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones Oracle Solaris 10 1/13 Information Library |
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)
13. Creating and Administering Resource Pools (Tasks)
14. Resource Management Configuration Example
15. Resource Control Functionality in the Solaris Management Console
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)
21. Non-Global Zone Login (Overview)
22. Logging In to Non-Global Zones (Tasks)
23. Moving and Migrating Non-Global Zones (Tasks)
24. Oracle Solaris 10 9/10: Migrating a Physical Oracle Solaris System Into a Zone (Tasks)
25. About Packages and Patches on an Oracle Solaris System With Zones Installed (Overview)
27. Oracle Solaris Zones Administration (Overview)
28. Oracle Solaris Zones Administration (Tasks)
29. Upgrading an Oracle Solaris 10 System That Has Installed Non-Global Zones
30. Troubleshooting Miscellaneous Oracle Solaris Zones Problems
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)
lx Branded Zone Installation (Task Map)
Installing and Booting lx Branded Zones
How to Obtain the Linux Archives
How to Install an lx Branded Zone
How to Install a Subset of the Packages
How to Enable Networking in an lx Branded Zone
How to Obtain the UUID of an Installed Branded Zone
How to Mark an Installed lx Branded Zone Incomplete
(Optional) Placing an Installed lxBranded Zone in the Ready State
How to Boot an lx Branded Zone
How to Boot an lx Branded Zone in Single-User Mode
Halting, Rebooting, Uninstalling, Cloning, and Deleting lx Branded Zones (Task Map)
Halting, Rebooting, and Uninstalling lx Branded Zones
How to Halt an lx Branded Zone
Cloning an lx Branded Zone on the Same System
How to Clone an lx Branded Zone
How to Clone a Zone from an Existing Snapshot
How to Use Copy Instead of ZFS Clone
Deleting an lx Branded Zone From the System
How to Remove an lx Branded Zone
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)
|
The halt procedure is used to remove both the application environment and the virtual platform for an lx branded zone. To cleanly shut down a zone, see How to Use zlogin to Shut Down an lx Branded Zone.
You must be the global administrator in the global zone to perform this procedure.
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.
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 lx-zone running /export/home/lx-zone lx shared
global# zoneadm -z lx-zone halt
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 - lx-zone installed /export/home/lx-zone lx shared
global# zoneadm -z lx-zone boot
Troubleshooting
If the zone does not halt properly, see Zone Does not Halt for troubleshooting tips.
You must be the global administrator in the global zone to perform this procedure.
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.
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 lx-zone running /export/home/lx-zone lx shared
global# zoneadm -z lx-zone reboot
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 lx-zone running /export/home/lx-zone lx shared
Tip - Note that the zone ID for lx-zone has changed. The zone ID generally changes after a reboot.
Caution - This procedure removes all of the files in the zone's root file system. The action 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.
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.
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 - lx-zone installed /export/home/lx-zone lx shared
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 lx-zone uninstall -F
Note that when you uninstall a zone that has its own ZFS file system for the zonepath, the ZFS file system is destroyed.
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.