01-26-2017
OK I don't think I am explaining this correct. I have a Solaris 11.3 system fully patched. I need to create 11.0, 11.1 and 11.2 zones on the Global zone which is 11.3. I have 11.0 11.1 and 11.2 IPS repo's available on the system. When I try to create a new zone with the 11.0 IPS repo set in pkg publisher the zone install fails with this message:
Failed Checkpoints:
Checkpoint execution error:
The following pattern(s) did not match any allowable packages. Try
using a different matching pattern, or refreshing publisher information:
Installation: Failed. See install log at /system/volatile/install.24386/install_log
ERROR: auto-install failed.
I have already refreshed the publisher information to no avail.
I don't understand that if I have the 11.0 repo set in pkg publisher on the global zone why I can't install an 11.0 zone on the global zone??
9 More Discussions You Might Find Interesting
1. Solaris
Hi,
I would like to implement zones in solaris 10 to simulate 2 nodes on a single solaris 10 using zones. Can some one tell me what does it mean by global and non-global zones
Also write what is the use of using non global or global and permissions like read-write on zones.
My requirement... (3 Replies)
Discussion started by: upengan78
3 Replies
2. Solaris
Hi All ,
I try to install some packages in my global zone...
On the execution of the installion of the script it quits by saying the error
"Non global zone check failed"
Kindly help me in this regard
Thanks in advance,
jeganr (7 Replies)
Discussion started by: jegaraman
7 Replies
3. Solaris
1. i read that VxFS (3.x) installed on a solaris 8 will not work on a branded zone. fair enough, but what is the impact of having the packages installed when the flarcreate is done? will the container fail to boot with those packages installed?
2. NTP client and server doesnt work on branded... (11 Replies)
Discussion started by: frustin
11 Replies
4. Solaris
Hi,
A quick question: Can Solaris 10 local zones be moved to a Solaris 11 global zone and work well?
Thank you in advance! (5 Replies)
Discussion started by: aixlover
5 Replies
5. UNIX for Advanced & Expert Users
Dear all,
recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes.
I did the following:
host1:
$ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed
$ zpool export zone1
host2:
$ zpool... (2 Replies)
Discussion started by: custos
2 Replies
6. Solaris
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Discussion started by: nick101
1 Replies
7. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
8. Solaris
I want to migrate a solaris 10 os to solaris 11.4 zone.
I did this
a)Collect some data like id sysid,disks,ip,etc..on solaris10
OK
b)Create this file.cfg with this command on solaris 10
zonep2vchk -c > /migration/sol10.cfg
OK
c)Create the archive flash on Solaris10 (1 Reply)
Discussion started by: Linusolaradm1
1 Replies
9. Solaris
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
LEARN ABOUT OPENSOLARIS
brands
brands(5) Standards, Environments, and Macros brands(5)
NAME
brands - alternate operating environments for non-global zones
DESCRIPTION
The branded zone (BrandZ) framework extends the Solaris Zones infrastructure described in zones(5) to include the creation of brands, which
provide non-global zones that contain non-native operating environments.
The term "brand" can refer to a wide range of operating environments. All brand management is performed as extensions to the current zones
structure.
Every zone is configured with an associated brand. The brand type is used to determine which scripts are executed when a zone is installed
and booted. In addition, a zone's brand is used to properly identify the correct application type at application launch time. The default
is the native brand.
A branded zone will support exactly one brand of non-native binary, which means that a branded zone provides a single operating environ-
ment. Once a zone has been assigned a brand, that brand cannot be changed or removed.
BrandZ extends the zones tools in the following ways:
o A brand is an attribute of a zone, set at zone create time.
o The zonecfg tool (see zonecfg(1M)) is used to set a zone's brand type and configure the zone.
o The zoneadm tool (see zoneadm(1M)) is used to report a zone's brand type and administer the zone.
Device Support
The devices supported by each zone are documented in the man pages and other documentation for that brand. The zones infrastructure detects
any attempt to add an unsupported device and issues a warning to the administrator. If the administrator chooses to add an unsupported
device despite that warning, that device might or might not work as expected. The configuration will be untested and unsupported.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWzoneu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
mdb(1), zlogin(1), zonename(1), dtrace(1M), in.rlogind(1M), sshd(1M), zoneadm(1M), zonecfg(1M), kill(2), priocntl(2), getzoneid(3C),
ucred_get(3C), getzoneid(3C), proc(4), attributes(5), lx(5), native(5), privileges(5), zones(5), lx_systrace(7D), crgetzoneid(9F)
SunOS 5.11 13 Feb 2009 brands(5)