Find knowledge base article(s) by searching for keywords in the title e.g. type linux in the search box below
Find knowledge base article(s) by browsing the subject categories of articles
Technology quick references, cheatsheets, user manuals etc.
Shop Online through ShopifyLite
Tutorials on various IT applications.
Search Title    (UL:0 |SS:f)

Software >> OS >> Unix >> Solaris >> 11 >> Boot Environment >> What is the relationship between BE in global zone and BE in non global zone and why a BE can be unbootable in non-global zone

Both global zones and non-global zones contain boot environments. Each boot environment in
a non-global zone is associated with a parent boot environment in the global zone, so that, if a
global zone boot environment is inactive, the related non-global zone boot environment is
unbootable.However, if you boot into that parent boot environment in the global zone, the
related boot environment in the non-global zone becomes bootable.
 

Note – If the boot environment is unbootable, it is marked with an exclamation point (!) in the
Active column in the beadm list output.

 

 


The beadm command restricts actions on unbootable boot environments as follows:
 

■ You cannot activate an unbootable boot environment.
■ You cannot destroy a boot environment that is both unbootable and marked as active on
reboot.
■ You cannot create a snapshot of an unbootable boot environment.
■ You cannot use an unbootable boot environment or boot environment snapshot with the -e
option of beadm create.
■ You cannot rename an unbootable boot environment.

 

 

[ © 2008-2021 myfaqbase.com - A property of WPDC Consulting ]