Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 11.1 Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management Oracle Solaris 11.1 Information Library |
Part I Oracle Solaris Resource Management
1. Introduction to 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. Introduction to Oracle Solaris Zones
16. Non-Global Zone Configuration (Overview)
17. Planning and Configuring Non-Global Zones (Tasks)
18. About Installing, Shutting Down, Halting, Uninstalling, and Cloning Non-Global Zones (Overview)
19. Installing, Booting, Shutting Down, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)
20. Non-Global Zone Login (Overview)
21. Logging In to Non-Global Zones (Tasks)
Initial Zone Boot and Zone Login Procedures (Task Map)
How to Create a Configuration Profile
How to Log In to the Zone Console to Perform the Internal Zone Configuration
How to Log In to the Zone Console
How to Use Interactive Mode to Access a Zone
How to Use Non-Interactive Mode to Access a Zone
Printing the Name of the Current Zone
22. About Zone Migrations and the zonep2vchk Tool
23. Migrating Oracle Solaris Systems and Migrating Non-Global Zones (Tasks)
24. About Automatic Installation and Packages on an Oracle Solaris 11.1 System With Zones Installed
25. Oracle Solaris Zones Administration (Overview)
26. Administering Oracle Solaris Zones (Tasks)
27. Configuring and Administering Immutable Zones
28. Troubleshooting Miscellaneous Oracle Solaris Zones Problems
Part III Oracle Solaris 10 Zones
29. Introduction to Oracle Solaris 10 Zones
30. Assessing an Oracle Solaris 10 System and Creating an Archive
31. (Optional) Migrating an Oracle Solaris 10 native Non-Global Zone Into an Oracle Solaris 10 Zone
32. Configuring the solaris10 Branded Zone
33. Installing the solaris10 Branded Zone
Use the zlogin command to log in from the global zone to any zone that is running or in the ready state. See the zlogin(1) man page for more information.
You can log in to a zone in various ways, as described in the following procedures. You can also log in remotely, as described in Remote Login.
Caution - Note that all data required must be supplied. If you provide a profile with missing data, then the zone is configured with missing data. This configuration might prevent the user from logging in or getting the network running. |
You must be the global administrator or a user with appropriate authorizations in the global zone to perform this procedure.
# sysconfig create-profile -o /path/sysconf.xml
# sysconfig create-profile -o /path/sysconf.xml -g location,identity,naming_services,users
# zoneadm -z my-zone install -c /path/sysconf.xml
If the configuration file is used, the system will not start the System Configuration Interactive (SCI) Tool on the console at initial zlogin. The file argument must be specified with an absolute path.
If a config.xml file was passed to the zoneadm clone, attach, or install commands, this configuration file is used to configure the system. If no config.xml file was provided during the clone, attach, or install operation, then the first boot of the zone will start the SCI Tool on the console.
To avoid missing the initial prompt for configuration information, it is recommended that two terminal windows be used, so that zlogin is running before the zone is booted in a second session.
You must be the global administrator or a user with appropriate authorizations in the global zone to perform this procedure.
global# zlogin -C my-zone
global# zoneadm -z my-zone boot
You will see a display similar to the following in the zlogin terminal window:
[NOTICE: Zone booting up]
Troubleshooting
If the initial SCI screen doesn't appear, you can type Ctrl L to refresh the SCI screen.
You must be the global administrator or a user with appropriate authorizations in the global zone to perform this procedure.
global# zlogin -C -d my-zone
Using the zlogin command with the -C option starts the SCI Tool if the configuration has not been performed.
my-zone console login: root Password:
In interactive mode, a new pseudo-terminal is allocated for use inside the zone.
You must be the global administrator or a user with appropriate authorizations in the global zone to perform this procedure.
global# zlogin my-zone
Information similar to the following will display:
[Connected to zone 'my-zone' pts/2] Last login: Wed Jul 3 16:25:00 on console
You will see a message similar to the following:
[Connection to zone 'my-zone' pts/2 closed]
Non-interactive mode is enabled when the user supplies a command to be run inside the zone. Non-interactive mode does not allocate a new pseudo-terminal.
Note that the command or any files that the command acts upon cannot reside on NFS.
You must be the global administrator or a user with appropriate authorizations in the global zone to perform this procedure.
The command zonename is used here.
global# zlogin my-zone zonename
You will see the following output:
my-zone
zonename# exit
zonename# ~.
Your screen will look similar to this:
[Connection to zone 'my-zone' pts/6 closed]
Note - The default escape sequence for ssh is also ~, which causes the ssh session to exit. If using ssh to remotely login to a server, use ~~. to exit the zone.
See Also
For more information about zlogin command options, see the zlogin(1) man page.
When a connection to the zone is denied, the zlogin command can be used with the -S option to enter a minimal environment in the zone.
You must be the global administrator or a user with appropriate authorizations in the global zone to perform this procedure.
global# zlogin -S my-zone
Note - Running init 0 in the global zone to cleanly shut down a Oracle Solaris system also runs init 0 in each of the non-global zones on the system. Note that init 0 does not warn local and remote users to log off before the system is taken down.
Use this procedure to cleanly shut down a zone. To halt a zone without running shutdown scripts, see How to Halt a Zone.
You must be the global administrator or a user with appropriate authorizations in the global zone to perform this procedure.