Go to main content

Creating and Administering Oracle® Solaris 11.4 Boot Environments

Exit Print View

Updated: November 2019
 
 

Working With Non-Global Zone BEs From the Global Zone

You can manage non-global zone BEs from the global zone, provided that you use BeFMRIs when performing management tasks. See About Boot Environment FMRIs.

The following example shows how you can destroy as well as rename non-global zone BEs directly from the global zone.

global$ beadm list -z zone1
Non-global Zone BE Names   Parent BE       Flags Mountpoint               Space  
------------------------   --------------   ---- ------------------------ -------
zbe://zone1/BE10           -               RO    -                        705.10M
zbe://zone1/BE3            be://rpool/BE3  R     -                        803.73M
zbe://zone1/solaris        be://rpool/BE2  N     /system/zones/zone1/root 1.04M  
zbe://zone1/zbe1           be://rpool/BE2  R     -                        17.10M 
zbe://zone1/zbe2           be://rpool/BE2  -     -                        2.00K  

global$ beadm destroy zbe://zone1/BE10

global$ beadm rename zbe://zone1/BE3 zbe://zone1/sol-11be

global$ beadm list -z zone1
Non-global Zone BE Names   Parent BE       Flags Mountpoint               Space  
------------------------   --------------   ---- ------------------------ -------
zbe://zone1/sol-11be       be://rpool/BE3  R     -                        803.73M
zbe://zone1/solaris        be://rpool/BE2  N     /system/zones/zone1/root 1.04M  
zbe://zone1/zbe1           be://rpool/BE2  R     -                        17.10M 
zbe://zone1/zbe2           be://rpool/BE2  -     -                        2.00K