Identify the five causes.

A zone won’t boot. Identify the five causes.

A zone won’t boot. Identify the five causes.

A.
The zone is configured to have its own CPUs, and there aren’t enough.

B.
The zone isconfigured to have exclusive access to an NIC,and the NIC is alreadyup.

C.
The zone is configured to mount a file system, which is already mounted.

D.
The zone iscurrently running or shutting down.

E.
The zone has been uninstalled.

F.
Your terminal session is missing the SYS_TIME privilege.

Explanation:
A:dedicated-cpu Resource
The dedicated-cpu resource specifies that a subset of the system’s processors should be
dedicated to a non-global zone while it is running. When the zone boots, the system will
dynamically create a temporary pool for use while the zone is running.
C:s the global administrator in the global zone, you can import raw and block devices into a nonglobal zone. After the devices are imported, the zone administrator has access to the disk. The
zone administrator can then create a new file system on the disk and perform one of the following
actions:
Mount the file system manually
Place the file system in /etc/vfstab so that it will be mounted on zone boot
D, E:Booting a zone places the zone in the running state. A zone can be booted from the ready
state or from the installed state. A zone in the installed state that is booted transparently
transitions through the ready state to the running state. Zone login is allowed for zones in the
running state.
Incorrect:
Not F: Sys_time not related to booting a zone.



Leave a Reply 1

Your email address will not be published. Required fields are marked *