A zone won't boot. Identify the five causes.
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 non-global 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.
Currently there are no comments in this discussion, be the first to comment!