"Virtual Terminal (Console) showing non-global zone?"

Post #303037492 by hicksd8 on Saturday 3rd of August 2019 05:23:42 AM

Which version of Illumos are you talking? I guess it's the equivalent of Solaris 10 or Solaris 11?

Why are you trying to do this?

A zone can be configured to boot automatically when the global boots (set when the zone is configured). So you can stop the zone booting automatically and start it manually using zoneadm.

A connection to the zone virtual console will persist across zone reboots.

Are you trying to debug something? Looking for an error message?

When you boot a zone manually (zoneadm) it will return to a prompt long before the zone is actually 'ready'. You can use truss to provide more feedback if the zone crashes on boot:

Code:
 # truss -o /var/tmp/zoneadm.out -aef -vall -wall zoneadm -z <zone name> boot

You can then view the /var/tmp/zoneadm.out file to see if it tells you anything.

Reference material from Oracle:
Non-Global Zone Login Methods - Oracle Solaris Administration: Oracle Solaris Zones, Oracle Solaris 10 Zones, and Resource Management

More information please. The skillset on this forum is awesome and I'm sure somebody here will help once we know what you are trying to achieve.

Last edited by hicksd8; 08-03-2019 at 09:40 AM..
 
Test Your Knowledge in Science: Mathematics
Difficulty: Easy
An isosceles triangle has two sides of equal length as opposed to three.
True or False?

9 More Discussions You Might Find Interesting

1. Solaris

Adding multiple virtual interfaces on a non global zone.

Hello All, I have a requirement to add multiple virtual interfaces on a non-global zone (Solaris 10). The global zone is a 2 node Veritas Cluster Server. So, my question is do we have to make any modifications to the cluster config (which I think should not be the case)? Can anyone help with me... (11 Replies)
Discussion started by: mahive
11 Replies

2. Solaris

[b]How to mount a folder from global zone to non global zone??

Hi All There is one folder in global zone I just want to share the same folder innon global zone. How can i do it? pls send me script for this. (2 Replies)
Discussion started by: vijaysachin
2 Replies

3. Solaris

How to access ENV variables of non global zones in global zone???

Hi Guys, My requirement is I have file called /opt/orahome/.profile in non global zone. PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/usr/local/bin:/usr/openwin/bin:. export PATH PS1="\${ORACLE_SID}:`hostname`:\$PWD$ " export PS1 EDITOR=vi export EDITOR ENV=/opt/orahome/.kshrc export ENV... (1 Reply)
Discussion started by: vijaysachin
1 Replies

4. Solaris

how to add a default gateway in a zone of different VLAN of global zone

Hi Greetings... I have an issue in connecting the zone from outside the network and it is because of default gateway. I can ping default gateway from inside the zone and not able to ping from global zone due to different VLAN issue. If i add two different gateways and restart network services,... (2 Replies)
Discussion started by: vvpotugunta
2 Replies

5. Solaris

showing 2 different time zones in global zone and nonglobal zone

can some one help me out as it is showing 2 different time zones in global zone and nonglobal zone .In global zone it is showing in GMT while in nonglobal zone i it showing as PDT. System in running with solaris 10 (3 Replies)
Discussion started by: ravijanjanam12
3 Replies

6. Solaris

Global and non-global zone resource sharing - tricky

hi all, Just a simple question but i cant get the answers in the book - In my globalzone , assuming i have 4 cpus (psrinfo -pv = 0-3), if i set dedicated-cpu (ncpus=2) for my local zone Is my globalzone left with 2 cpus or still 4 cpus ? Does localzone "resource reservation.e.g. cpu in... (6 Replies)
Discussion started by: javanoob
6 Replies

7. Solaris

Date and time change in global and non global zone

Hi, If I change date and time in global zone, then it will affect in non global zones. During this process what files will get affect in non global zones and which mechanism it's using to change. gloabl zone:Solaris 11.3 X86 TIA (1 Reply)
Discussion started by: Sumanthsv
1 Replies

8. Solaris

Unable to login via console mode to non-global zone

tldr; We've installed a non-global-zone from a unified archive which once booted, we're unable to gain access to the system either through zlogin or zlogin -C. Errors; svc.startd: instance svc:/system/console-login:default exited with status 127 Investigation; 1) Already opened a SR with... (1 Reply)
Discussion started by: samthewildone
1 Replies

9. Solaris

Solaris 11 zone has no external network access (except to Global Zone)

Hi, hoping someone can help, its been a while since I used Solaris. After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin) However, the NGZ cannot access any other netwqork devices, it can't even see the default router ... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
zones(5)						Standards, Environments, and Macros						  zones(5)

NAME
zones - Solaris application containers DESCRIPTION
The zones facility in Solaris provides an isolated environment for running applications. Processes running in a zone are prevented from monitoring or interfering with other activity in the system. Access to other processes, network interfaces, file systems, devices, and inter-process communication facilities are restricted to prevent interaction between processes in different zones. The privileges available within a zone are restricted to prevent operations with system-wide impact. See privileges(5). You can configure and administer zones with the zoneadm(1M) and zonecfg(1M) utilities. You can specify the configuration details a zone, install file system contents including software packages into the zone, and manage the runtime state of the zone. You can use the zlogin(1) to run commands within an active zone. You can do this without logging in through a network-based login server such as in.rlogind(1M) or sshd(1M). An alphanumeric name and numeric ID identify each active zone. Alphanumeric names are configured using the zonecfg(1M) utility. Numeric IDs are automatically assigned when the zone is booted. The zonename(1) utility reports the current zone name, and the zoneadm(1M) utility can be used to report the names and IDs of configured zones. A zone can be in one of several states: CONFIGURED Indicates that the configuration for the zone has been completely specified and committed to stable storage. INCOMPLETE Indicates that the zone is in the midst of being installed or uninstalled, or was interrupted in the midst of such a transition. INSTALLED Indicates that the zone's configuration has been instantiated on the system: packages have been installed under the zone's root path. READY Indicates that the "virtual platform" for the zone has been established. Network interfaces have been plumbed, file systems have been mounted, devices have been configured, but no processes associated with the zone have been started. RUNNING Indicates that user processes associated with the zone application environment are running. SHUTTING_DOWN Indicates that the zone is being halted. The zone can become stuck in one of these states if it is unable to tear DOWN down the application environment state (such as mounted file systems) or if some portion of the virtual platform cannot be destroyed. Such cases require operator intervention. Process Access Restrictions Processes running inside a zone (aside from the global zone) have restricted access to other processes. Only processes in the same zone are visible through /proc (see proc(4) or through system call interfaces that take process IDs such as kill(2) and priocntl(2). Attempts to access processes that exist in other zones (including the global zone) fail with the same error code that would be issued if the specified process did not exist. Privilege Restrictions Processes running within a non-global zone are restricted to a subset of privileges, in order to prevent one zone from being able to per- form operations that might affect other zones. The set of privileges limits the capabilities of privileged users (such as the super-user or root user) within the zone. The list of privileges available within a zone can be displayed using the ppriv(1) utility. For more informa- tion about privileges, see privileges(5). Device Restrictions The set of devices available within a zone is restricted, to prevent a process in one zone from interfering with processes in other zones. For example, a process in a zone should not be able to modify kernel memory using /dev/kmem, or modify the contents of the root disk. Thus, by default, only a few pseudo devices considered safe for use within a zone are available. Additional devices can be made available within specific zones using the zonecfg(1M) utility. The device and privilege restrictions have a number of effects on the utilities that can run in a non-global zone. For example, the eep- rom(1M), prtdiag(1M), and prtconf(1M) utilities do not work in a zone since they rely on devices that are not normally available. File Systems Each zone has its own section of the file system hierarchy, rooted at a directory known as the zone root. Processes inside the zone can access only files within that part of the hierarchy, that is, files that are located beneath the zone root. This prevents processes in one zone from corrupting or examining file system data associated with another zone. The chroot(1M) utility can be used within a zone, but can only restrict the process to a root path accessible within the zone. In order to preserve file system space, sections of the file system can be mounted into one or more zones using the read-only option of the lofs(7FS) file system. This allows the same file system data to be shared in multiple zones, while preserving the security guarantees supplied by zones. NFS and autofs mounts established within a zone are local to that zone; they cannot be accessed from other zones, including the global zone. The mounts are removed when the zone is halted or rebooted. Networking Zones can be assigned logical network interfaces, which can be used to communicate over the network. These interfaces are configured using the zonecfg(1M) utility. The interface is removed when the zone is halted or rebooted. Only logical interfaces can be assigned to a zone. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
zlogin(1), zonename(1), in.rlogind(1M), sshd(1M), zoneadm(1M), zonecfg(1M), getzoneid(3C), kill(2), priocntl(2), ucred_get(3C), get- zoneid(3C), proc(4), attributes(5), privileges(5), crgetzoneid(9F) SunOS 5.10 13 Apr 2004 zones(5)

Featured Tech Videos

All times are GMT -4. The time now is 03:30 AM.
Unix & Linux Forums Content Copyright 1993-2019. All Rights Reserved.
Privacy Policy