Multiple VNICs in Solaris 11 Zone

Is there a best way to create a vnic within a solaris 11 zone on top of the zone's interface. I was able to create a vnic from the ipmp interface but this
may not be a proper way.
Does multiple vnics within a zone need to be created outside the zone first? This is not using a vsw because it's not a private network.

There are a couple of options:
1. If 'anet' resource type is specified in zonecfg(1M) for creating the VNIC,
add another anet for the zone. This will create a second VNIC when the zone is rebooted.
2. If 'dladm set-linkprop -p zone=... <vnic-link-name>' is used for assigning the
VNIC to the zone, create a second VNIC and assign it to the zone the same way.
-Krishna

Similar Messages

Solaris 10 Zone for Solaris 11.1 creation with template fails.

Hi,
We are trying to use the Oracle VM Template for Oracle Solaris 10 Zone to create a solaris 10 zone on a solaris 11.1 GZ
root@exsolh0005:/opt/scripts# ./solaris-10u11-sparc -v
This is an Oracle VM Template for Oracle Solaris Zones.
Copyright Â© 2011, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license
agreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly
permitted in your license agreement or allowed by law, you may not
use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any
part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by
law for interoperability, is prohibited.
Version: 1.0.9.12
root@exsolh0005:/opt/scripts# ./solaris-10u11-sparc -p /rpool -a 10.83.128.35/24 -i net6 -z testzone
This is an Oracle VM Template for Oracle Solaris Zones.
Copyright Â© 2011, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license
agreement containing restrictions on use and disclosure and are
protected by intellectual property laws. Except as expressly
permitted in your license agreement or allowed by law, you may not
use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any
part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by
law for interoperability, is prohibited.
IMAGE: ./solaris-10u11-sparc
ZONE: testzone
ZONEPATH: /rpool/testzone
VNIC: vnicZBI83273795
IP ADDR: 10.83.128.35
NETMASK: 255.255.255.0
DEFROUTER: 10.83.128.1
TIMEZONE: Europe/Copenhagen
Checking disk-space for extraction
Ok
Extracting in /opt/scripts/bootimage.8Ham6r ...
100% [===============================>]
Checking data integrity
Ok
Checking platform compatibility
The host and the image do not have the same Solaris release:
host Solaris release: 5.11
image Solaris release: 5.10
Will create a Solaris 10 branded zone.
Checking disk-space for installation
Ok
Installing in /rpool/testzone ...
100% [===============================>]
Attaching testzone
Problem attaching testzone.
More details in /var/sadm/install/logs/solaris-10u11-sparc.log
Cleaning up and exiting.
Friday, May 10, 2013 03:18:01 PM CEST: cleaning up
root@exsolh0005:/opt/scripts#
root@exsolh0005:/opt/scripts# cat /var/log/zones/zoneadm.20130510T131756Z.testzone.attach
[Friday, May 10, 2013 03:17:56 PM CEST] ==== Starting: /usr/lib/brand/solaris10/attach testzone /rpool/testzone -c /opt/scripts/bootimage.8Ham6r/sysidcfg.testzone ====
[Friday, May 10, 2013 03:17:56 PM CEST] Progress being logged to /var/log/zones/zoneadm.20130510T131756Z.testzone.attach
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning datasets under rpool/testzone
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning rpool/testzone
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning rpool/testzone/rpool
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning rpool/testzone/rpool/ROOT
[Friday, May 10, 2013 03:17:56 PM CEST] Pinning rpool/testzone/rpool/ROOT/zbe
[Friday, May 10, 2013 03:17:56 PM CEST] Log File: /var/log/zones/zoneadm.20130510T131756Z.testzone.attach
[Friday, May 10, 2013 03:17:57 PM CEST] Converting detached zone boot environment 'zbe'.
[Friday, May 10, 2013 03:17:57 PM CEST] Unmounting /rpool/testzone/root
[Friday, May 10, 2013 03:18:00 PM CEST] setting ZFS property zoned=on on rpool/testzone/rpool
[Friday, May 10, 2013 03:18:00 PM CEST] setting ZFS property canmount=noauto on rpool/testzone/rpool/ROOT
[Friday, May 10, 2013 03:18:00 PM CEST] setting ZFS property mountpoint=legacy on rpool/testzone/rpool/ROOT
[Friday, May 10, 2013 03:18:01 PM CEST] Mounting boot environment in rpool/testzone/rpool/ROOT/zbe-0 at /rpool/testzone/root (including child datasets)
cannot open 'ERROR: Error: Command <zfs list -H -o name -t filesystem -r rpool/testzone/rpool/ROOT/zbe-0> exited with status 1': invalid dataset name
[Friday, May 10, 2013 03:18:01 PM CEST] ERROR: refresh of ERROR: Error: Command <zfs list -H -o name -t filesystem -r rpool/testzone/rpool/ROOT/zbe-0> exited with status 1 failed
[Friday, May 10, 2013 03:18:01 PM CEST] ERROR: Error: rpool/testzone/rpool/ROOT/zbe-0: No such dataset.
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning datasets under rpool/testzone
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning rpool/testzone
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning rpool/testzone/rpool
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning rpool/testzone/rpool/ROOT
[Friday, May 10, 2013 03:18:01 PM CEST] Unpinning rpool/testzone/rpool/ROOT/zbe
[Friday, May 10, 2013 03:18:01 PM CEST] Result: Attach Failed.
[Friday, May 10, 2013 03:18:01 PM CEST] Exiting with exit code 254
[Friday, May 10, 2013 03:18:01 PM CEST] ==== Completed: /usr/lib/brand/solaris10/attach testzone /rpool/testzone -c /opt/scripts/bootimage.8Ham6r/sysidcfg.testzone ====
Looks like a script bug..
Regards
Claus

Hello All,
I would love to know if someone has a solution to this as I am seeing a similar issue with a slightly different setup.
Solaris 8 and Netra 240. I get the same result with and without patches and finish scripts. After the jumpstart and the failed boot attempt from disk. I can boot from cd, copy the glm driver from the cd to disk, and then everything works as it should. Obviously this is not a solution but only a work around.
Is it something to do with the SCSI hardware architecture used in the *240s?
Edited by: Gareth_Mann on Oct 2, 2007 7:41 PM

Installation of Oracle 10g in Solaris 10 zones

Hi Everybody,
Is there any Documentation for Installation of Oracle 10g in Solaris 10 Zones.
I am having multiple zones shared by one common SAN Storage.
I want to install oracle 10g in one of the particular local zone.
Regards,
Prosenjit Mukherjee.

Last time I looked at metalink the documentation said zones and containers were not supported. That may no longer be true so you should check there first.

Solaris 8 Container in Solaris 10 Zone

Hi All,
one of our customers wants to run Solaris 8 with Oracle 8.1.7 in a BrandZ Zone. Does anybody have an idea about how stable Solaris 8 is in a Zone environment? Are there any known issues with Solaris 8 running in a Zone?
Since Solaris 8 is EndOfShipment, are there chances to get up-to-date Sun Hardware bundled with Solaris 8 apart of using Solaris 10 Zones?
Thanks in Advace,
Dog

i didnt however i wasnt hammering it. if the load was expected to be high i would have done the io layout diff (try and follow some of oracles ideas: SAME for one, if possible).
some depends on the load and the load from the other zones. you can use allocate resource limits to give more priority to more important zones or make sure you have enough resources to start. what type of load are you expecting?

Route add problem in solaris 10 zone

hi all
when i add route in one of my solaris 10 zone.. i get the following error. any workaround?
# route add xxx.xxx.255/24 10.xxx.xxx.1
add net xxx.xxx.255/24: gateway 10.xxx.xxx.1: insufficient privileges
thanks
peter

it means i can only add route in globle zone? but
global zone and sub-zones are using diff IP and
interface cards. so how?But they're children of the same kernel. There can only be one routing table (at the moment, anyway). So make your route adds from global and watch them appear in the netstat output of your non-global zones.
I agree that this is a confusing and poorly documented aspect of zones, however. I will admit to you that I barely understand it myself. However, there is a good answer to a question I had about this in comp.unix.solaris. Search that newsgroup for "Viewing non-global routes from global zone". A similar question fell on deaf ears here.
Also, I would recommend searching this forum for "zone routes" or "zone routing" as this is a frequently hit topic.
--gc1973

Problem with Java in solaris 10 zone

HI ,
i get this error message in my solaris 10 zone :
#./java version
Exception java.lang.OutOfMemoryError: requested -4 bytes for size_t in /BUILD_AREA/jdk1.5.0_11/hotspot/src/os/solaris/vm/os_solaris.cpp. Out of swap space?
in global zone , java works fine !
uname -a
SunOS Server 5.10 Generic_141414-07 sun4u sparc SUNW,SPARC-Enterprise
best regards

I see mention of a similar problem, but only with early development releases of solaris10 branded zones running on Solaris 11 development bits. It seems as though this is not what you are running.
Since there are no swap caps nor brand emulation in place, the next thing I would suspect would be that you somehow have inconsistencies between key libraries (e.g. libc) and the kernel. This could happen if you have a full-root zone that has been force attached (zoneadm -z <zone> attach -F). In the past, I've seen products that do this under the covers (e.g. Veritas Cluster) so it may have happened without your knowledge. If it is a sparse root zone, you may want to run "zoneadm -z <zone> detach; zoneadm -z <zone> attach -u". Prior to doing so, take whatever precautions you would normally take when patching a system.
If you open a support call about this I bet the first advice you are going to get is to patch, as you seem to be 2+ years behind. Also, newer releases of Java 5 are available at http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase5-419410.html.

Solaris 10 zone config for JES

Setup a zone to install JES - Web servers, but when I launch the installer I get the following:
WARNING: Unsupported non-global zone
EntSysResources:zoneCheckPanel-Gui-LocalZoneSupported
Something in the zone setup is incorrect, but not sure what.
Anyone else out running JES in Solaris 10 zones?
Thanks!
Steve
[email protected]

From docs.sun.com -
The following Java ES and zones scenarios are supported in this release of Java ES:
* Installing Java ES in a non-global zone that uses the whole root file system (Using the default sparse root file system is not supported.)
* Installing Java ES in the global zone with no non-global zones
Zone can be 2 type - sparse root and whole root . sparse root model has following folders inherited - /lib, /platform, /sbin and /usr.
If a non-global zone doesn't have any inherit-pkg-dir resources, such a zone is said to be a whole root one
If you want to create a whole root zone but default shared file systems resources have been added by using inherit-pkg-dir, you must remove these default inherit-pkg-dir resources using zonecfg before you install the zone:
zonecfg:my-zone> remove inherit-pkg-dir dir=/lib
zonecfg:my-zone> remove inherit-pkg-dir dir=/platform
zonecfg:my-zone> remove inherit-pkg-dir dir=/sbin
zonecfg:my-zone> remove inherit-pkg-dir dir=/usr

Solaris 8 Zone

Hi,
What's wrong with my config ? I can't create a Solaris 8 Zone.
I think there is problem with the template...
Thanks !
Test 1 :
# zonecfg -z s8-zone
s8-zone: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:s8-zone> create -t SUNWsolaris8
zonecfg:s8-zone> set zonepath=/zones/sol8
zonecfg:s8-zone> set autoboot=true
zonecfg:s8-zone> add net
zonecfg:s8-zone:net> set address=192.168.20.192
zonecfg:s8-zone:net> set physical=eri0
zonecfg:s8-zone:net> end
zonecfg:s8-zone> commit
s8-zone: unknown brand.
s8-zone: Invalid document
Test 2 :
# zonecfg -z sol8
sol8: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:sol8> create -t SUNWsolaris8
zonecfg:sol8> verify
zonepath cannot be empty.
sol8: unknown brand.
sol8: Invalid document
zonecfg:sol8> quit
Config
Kernel patch : 120011-14
Migration Assistant patch : 128548-03
Release : Solaris 10 8/07 s10s_u4wos_12b SPARC
# pkginfo | grep -i bran
system SUNWs8brandr Solaris 8 Migration Assistant: solaris8 brand support (Root)
system SUNWs8brandu Solaris 8 Migration Assistant: solaris8 brand support (
# pkginfo | grep -i p2v
system SUNWs8p2v Solaris 8 p2v Tool
SUNWsolaris8.xml :
root@sf280test:/ # more /etc/zones/SUNWsolaris8.xml
<?xml version="1.0"?>

<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">
<zone name="default" zonepath="" autoboot="false" brand="solaris8">
</zone>

Your problem is that you can only create Solaris 10 zones. Zones is not a true virtual machine so it can not support older version of Solaris. you want to install. If you need to run Solaris 8 on the same machine as Solaris 10 your only choice is to use something like VMware.

Solaris 8 on a solaris 10 zone?

Can i install and configure solaris 8 OS on a solaris 10 zone? If yes , is it supported by sun in case we run into any issues and is it a straight forward way of doing it or is there any implication.complexities involved in configuring so?
Thanks in advance

Ah, attitudes, everyone has one...
As the link awhile back implied, there is something called the "Solaris 8 migration assistant" which is a Solaris 8 "branded" zone. It's still running the Solaris 10 kernel under the covers (so technically you're not running Solaris 8 in a zone) but it's impersonating a Solaris 8 system. I think there's a Solaris 9 version now too.
The last I heard, Sun was saying these can only be implemented with Sun Professional Services but I don't know where that stands. I don't believe it's free either.
Here's a link to the docs: [http://docs.sun.com/app/docs/doc/820-2914/|http://docs.sun.com/app/docs/doc/820-2914/]

Inetd service/program crashes with core dump in Solaris 8 zone/container

I have developed a service in C that is launched from inetd when something comes on a specific port.
When a connection is opened to the port a core dump is created in the same directory where the executable file is located.
If you run the same service program from the command line everything is working perfect.
This is running in a Solaris 8 zone/container on a Solaris 10 machine.
Everything is set correctly in /etc/inetd.conf and in /etc/services.
I have even stripped down the program to a hello world program that is just printing a string to the screen and it is still crashing with a core dump.
# ldd test_srv
/usr/lib/secure/s8_preload.so.1
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1
The same service is running on a Linux machine and on a Solaris 10 machine without zones/containers without any problems.
Can you please help me figure out what am I missing. Is there something specific with zones/containers that should be set / configured?
Do I have to set some specific env. variables to work in a Solaris 8 zone/container environment or is it something very simple that I'm missing?

Could you please examine the truss log and advice what the problem is and how to fix it?
(some lines deleted)
bash-2.03# truss -f -p 18361 #### /usr/sbin/inetd -s -t &
18361: poll(0xFFBFF528, 53, -1)        (sleeping...)
18361: poll(0xFFBFF528, 53, -1)                        = 1
18361: accept(63, 0xFFBFF870, 0xFFBFF914, 1)           = 3
18361: sigprocmask(SIG_BLOCK, 0xFFBFF5F0, 0xFFBFF600) = 0
18361: lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
18361: lwp_sigtimedwait(0xFFBFF568, 0xFFBFF728, 0x00000010) = 0
18361: fork()                                          = 1921
1921:   fork()          (returning as child ...)        = 18361
1921:   sigprocmask(0, 0x00000000, 0xFFBFF600)          = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFF600)          = 0
1921:   lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
18361: sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
18361: close(3)                                        = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFF600)          = 0
1921:   lwp_sigtimedwait(0xFFBFF668, 0xFFBFF528, 0x00000020) = 0
1921:   sigaction(SIGHUP, 0xFFBFF528, 0xFFBFF500)       = 0
18361: lwp_sigtimedwait(0xFFBFF568, 0xFFBFF5F0, 0x00000010) = 0
1921:   lwp_sigtimedwait(0xFFBFF508, 0xFFBFF458, 0x00000010) = 0
18361: sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
1921:   sigprocmask(SIG_SETMASK, 0xFFBFF5F0, 0xFFBFF600) = 0
1921:   lwp_sigtimedwait(0xFFBFF600, 0xFFBFF578, 0x00000010) = 0
1921:   lwp_sigtimedwait(0xFFBFF568, 0xFFBFF728, 0x00000010) = 0
1921:   fcntl(3, F_DUP2FD, 0x00000000)                  = 0
1921:   close(3)                                        = 0
1921:   fcntl(0, F_DUP2FD, 0x00000001)                  = 1
1921:   fcntl(0, F_DUP2FD, 0x00000002)                  = 2
1921:   open64("/etc/.name_service_door", O_RDONLY)     = 3
1921:   fcntl(3, F_SETFD, 0x00000001)                   = 0
1921:   door_info(3, 0xFF0C2748)                        = 0
1921:   door_call(3, 0xFFBFF278)                        = 0
1921:   close(67)                                       Err#9 EBADF
1921:   close(66)                                       Err#9 EBADF
1921:   close(65)                                       Err#9 EBADF
1921:   close(64)                                       Err#9 EBADF
1921:   close(63)                                       = 0
1921:   close(62)                                       = 0
1921:   close(12)                                       = 0
1921:   close(11)                                       = 0
1921:   close(10)                                       Err#9 EBADF
1921:   close(9)                                        Err#9 EBADF
1921:   close(8)                                        Err#9 EBADF
1921:   close(7)                                        Err#9 EBADF
1921:   close(6)                                        Err#9 EBADF
1921:   close(5)                                        Err#9 EBADF
1921:   close(4)                                        Err#9 EBADF
1921:   setrlimit(RLIMIT_NOFILE, 0xFFBFFD20)            = 0
1921:   xenix(398872, 0xFFBFF5E4, 0x00000040)           = 38
1921:   execve("/tmp/srv/t_srv", 0x0008B5FC, 0xFFBFFDA0) argc = 0
1921:   getuid()                                        = 0 [0]
1921:   resolvepath("/usr/lib/ld.so.1", "/usr/lib/ld.so.1", 1023) = 16
1921:   open("/var/ld/ld.config", O_RDONLY)             = 3
1921:   fstat(3, 0xFFBFF5E8)                            = 0
1921:   mmap(0x00000000, 148, PROT_READ, MAP_SHARED, 3, 0) = 0xFF3E0000
1921:   close(3)                                        = 0
1921:   stat("/usr/lib/libc.so.1", 0xFFBFF648)          = 0
1921:   resolvepath("/usr/lib/libc.so.1", "/usr/lib/libc.so.1", 1023) = 18
1921:   open("/usr/lib/libc.so.1", O_RDONLY)            = 3
1921:   mmap(0x00000000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xFF340000
1921:   mmap(0x00000000, 802816, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON, -1, 0) = 0xFF200000
1921:   mmap(0xFF200000, 703520, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF200000
1921:   mmap(0xFF2BC000, 24772, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 704512) = 0xFF2BC000
1921:   munmap(0xFF2AC000, 65536)                       = 0
1921:   memcntl(0xFF200000, 113528, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0
1921:   close(3)                                        = 0
1921:   stat("/usr/lib/libdl.so.1", 0xFFBFF648)         = 0
1921:   resolvepath("/usr/lib/libdl.so.1", "/usr/lib/libdl.so.1", 1023) = 19
1921:   open("/usr/lib/libdl.so.1", O_RDONLY)           = 3
1921:   mmap(0xFF340000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF340000
1921:   mmap(0x00000000, 8192, PROT_NONE, MAP_PRIVATE|MAP_NORESERVE|MAP_ANON, -1, 0) = 0xFF330000
1921:   mmap(0xFF330000, 2638, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF330000
1921:   close(3)                                        = 0
1921:   stat("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", 0xFFBFF368) = 0
1921:   resolvepath("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", "/usr/platform/sun4u-us3/lib/libc_psr.so.1", 1023) = 41
1921:   open("/usr/platform/SUNW,Sun-Fire-480R/lib/libc_psr.so.1", O_RDONLY) = 3
1921:   mmap(0xFF340000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0xFF340000
1921:   close(3)                                        = 0
1921:   mmap(0x00000000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFF320000
1921:   dup(0)                                          = 3
1921:   llseek(0, 0, SEEK_CUR)                          Err#29 ESPIPE
1921:   close(0)                                        = 0
1921:   fcntl(3, F_DUP2FD, 0x00000000)                  = 0
1921:   close(3)                                        = 0
1921:   dup(1)                                          = 3
1921:   close(1)                                        = 0
1921:   fcntl(3, F_DUP2FD, 0x00000001)                  = 1
1921:   close(3)                                        = 0
1921:   dup(2)                                          = 3
1921:   close(2)                                        = 0
1921:   fcntl(3, F_DUP2FD, 0x00000002)                  = 2
1921:   close(3)                                        = 0
1921:   sys#177(0x00000080, 0xFFBFFB7C, 0xFF3F0518, 0x00000000, 0xFF3C2EF8, 0xFF2C0284) = 0x00000000 [0xFFBFFB7C]
1921:   sys#227(0x00000006, 0x00000000, 0x0001ADF0, 0xFF3F0518, 0xFF3C3C18, 0xFF3C2670) = 0x0000000C [0x00000000]
1921:   sys#227(0x00000002, 0x0000000C, 0x0000000E, 0xFFBFFCAE, 0x00000002, 0xFF3C2670) = 0x00000002 [0x00000000]
1921:       Incurred fault #6, FLTBOUNDS %pc = 0xFF232E2C
1921:         siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
1921:       Received signal #11, SIGSEGV [default]
1921:         siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000
1921:           *** process killed ***
18361:      Received signal #18, SIGCLD, in poll() [caught]
18361:        siginfo: SIGCLD CLD_DUMPED pid=1921 status=0x000B
18361: poll(0xFFBFF528, 53, -1)                        Err#4 EINTR
18361: lwp_sigtimedwait(0xFFBFF218, 0xFFBFF140, 0x00000010) = 0
18361: lwp_sigtimedwait(0xFFBFF130, 0xFFBFF218, 0x00000010) = 0
18361: sigprocmask(0, 0x00000000, 0xFFBFEF28)          = 0
18361: poll(0xFFBFF528, 53, -1)        (sleeping...)Thank you in advance

Fusion Middleware 11g Weblogic, forms and Reports in Solaris 11 zone

Hi,
Any one Installed Fusion Middleware 11g Weblogic, forms and Reports on Solaris 11 zone ??
So Pls Let me know Weblogic and Fusion Middleware 11g versions which are working
I try
Weblogic 10.3.3 Installed 64 Bit Went OK
Fusion Middleware 11g 11.1.1.2.0 Errors While Relink few items like frmbldr etc
Then Fusion Middleware 11g Patchset5 11.1.1.6 Still Same Errors Relink few items like frmbldr etc
Then Cconfig.sh failed at create domain
Regards

Hi Deepak,
Just config.sh or config.cmd file and try to change the JDK with in and try to configure new domain from there.
Regards,
Kal

Error messages during booting of Solaris 8 zone

I have installed a Solaris 8 zone from a flash archive of a Solaris 8 server that is currently in production. I get no errors during the installation of the zone and when I boot the zone I get the following messages on the zone console:
SunOS Release 5.8 Version Generic_Virtual 64-bit
Copyright 1983-2000 Sun Microsystems, Inc. All rights reserved
Hostname: madison1xl
The system is coming up. Please wait.
NIS domainname is eam.rjf.com
operation failed, Not owner
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
device name given is not a stream device (No such device or address)
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
operation failed, Not owner
Sun BluePrints network security settings applied.
syslog service starting.
I am not sure what is causing these errors. The zone appears to be running properly, but I am concerned that something is not starting during the boot process. /var/adm/messages file does not show any errors. Thanks for any help you can give me.

Thanks. That helped alot. I found out that all the messages came from a start up script named nddconfig. Since the ngz cannot change anything about devices this was causing a lot of errors. I stopped the script from starting and now do not receive any errors.

How do I get from Branded Zones to "real" Solaris 10 Zones?

My head is beginning to spin! I am beginning to think I have been led down a blind alley.
We have vast numbers of old Solaris 8 systems that we want to consolidate on new hardware in Solaris 10 Zones. We have been bombarded with advice that the way to go is to move it first to Branded Zones, as a stepping stone, and then migrate/upgrade it from there to Solaris 10. So we have started on our journey.
We now have our first bunch of Solaris 8 containers happily installed and running. And yes, it was relatively easy and painless, and the tool support was good. But now what? What are the steps and tools that will make the second step, from Solaris 8 to Solaris 10?
Everything out there hints that it is supposed to be easy. But every time I try and spec out the steps for our teams to follow I come unstuck. Does Live Upgrade feature in this anywhere? (And if so, at what point does my zone lose its Brand identity?) Is there some way to use archives? (And if so, how do I only include the bits I need to move?) Is there something magic under the covers of the Zone administration commands? (And if so, what pulls in my Solaris 8 stuff?) Is there at least some tool somewhere that will capture the configuration I need and build me a new one?
If the answer is that I just define the new Zone by hand and re-install all my applications from scratch, then can somebody explain just what I have achieved so far, and in what way it can be construed as a "stepping stone"?

Correct. But we have now invested in the time taken to learn about Branded Zones, do the migrations, teach the support teams how to manage them... Plus we are paying the subscription for the Branded Zone software. And we still have pure Solaris 8 applications staring end-of-support in the face. We could have made the same investment to re-install the applications in a real Solaris 10 Zone and make them work "properly". All the publicity tells me I've made my migration to Solaris 10 much easier, but I still can't see how I'm any nearer my end point.Here's where your losing it. There is no real distinction between what you call a normal Solaris 10 zone and a Solaris Branded 8 zone. They could have called it something else and you would still insist that somehow one is normal and one is not. There are a variety of Branded Zones. There's a Solaris 8, Solaris 9, and Linux Branded Zones. They differ from what you call "normal" zones in that you basically are adding an OS to the Base OS and are not just copying files from the Base OS. That's the only difference. In all other respects they are the same. The only differentiators is for a Branded Zone you are adding the files from some other OS, even if it's just an earlier version of Solaris.
How do you migrate from a Solaris 8 zone to a Solaris 10 zone. The same way that you moved from the Solaris 8 physical box to the Solaris 8 branded zone. The steps should be the same. Implicite_Order pretty much said the same thing.
You seem to have a hang up on the words "normal zone." Yea I know, you've spent time and money and educated everyone and now your looking for the payoff. As I already stated and has been echoed by I_O, contact the vendor to see if they have Solaris 10 support, if they do, create a zone on a dev box, do some testing, and then create the zone on the real box, do the install, migrate the data. Just as you already did from the Solaris 8 box. If they don't have a Solaris 10 specific version you can still setup a test box, create a "normal" zone, install the app and some test data, make sure it works, and then create the "normal" zone, install the app, migrate the data, and relax.
alan

Solaris Branded Zones, Unable to reboot/Halt

Hi People,
Hoping someone can help. Im running Solaris 10 on a Sun Workstation Ultra 45. I have two disks. One disk has the default install of solaris 10 all updated to the latest patches.The second disk is mounted as /zones and holds each of the zones on ZFS. I have then downloaded and installed successfully Solaris 8 and Solaris 9 and Solaris 10 zones. So I have 3 zones.
The problem I am facing is I can boot up all 3 zones fine and they work great, however when I halt or reboot either Solaris 8 or solaris 9, they never come back up. I try and zlogin to them and telnet and ssh and they are totally unresponsive and quite literally dont boot. I have tried to pkill -9 -z zonename ; umount /zonesfilesystem; zpool clear and even rebooted the Global zone. Still will not come up. The only way they will boot after being shutdown is if i shutdown the global zones and turn the server off and back on.
Solaris 10 Zone boots up and down fine with no isses. I have tried this on both UFS and ZFS thinking it might be a file lock issue. Still unable to reboot or halt a zone and bring it back up.
Any help please :)
Thanks in advance.

When they are unable to come back up, what does 'zoneadm list -cv' say? If the state of the zone is "down" or "shutting_down", you can probably benefit from the fix for:
7038404 outstanding zone references should not cause zone_destroy(2) to hang
This is available in 147440-05 (sparc) / 147441-05 (x86) or later.

Global swap is not reflected in branded solaris 8 zone

I have 32 GB in my global zone
root@Z21-AP-02 # swap -s
total: 5753912k bytes allocated + 511136k reserved = 6265048k used, 32257984k available
when I look in my branded solaris 8 zone I see a much smaller value
root@txpwrsrv07-2:/ # swap -s
total: 3202696k bytes allocated + 0k reserved = 3202696k used, 2040184k available
Tried
zonecfg -z txpwrsrv07-2
select capped-memory
set swap=32g
end
exit
no difference.
Any help would be appreciated.

Thanks for the reply
did the following
prctl -n project.max-shm-memory $$
project.max-shm-memory
privileged 7.71GB - deny -
system 16.0EB max deny
prctl -n project.max-shm-memory -r -v 32G -i project 3
prctl -n project.max-shm-memory $$
project.max-shm-memory
privileged 7.71GB - deny -
system 16.0EB max deny
no change. Is there something else restricting this?

Multiple VNICs in Solaris 11 Zone

Similar Messages

Maybe you are looking for