Upgrading a Zone - Solaris9 to Solaris10

I provide systems for a software development team that wants to make sure the upgrade from Solaris 9 to Solaris 10 will go smoothly. So... we started with a Solaris 9 container. How do we upgrade a 9 container to be 10?
I've spent a considerable amount of time looking for this and it and in theory, this is a great way to quickly test, and retest the upgrades and the impact they have our our code.
Thanks

Its very hard to change the size of the root partition.
Your best bet is to do a fresh install.
Note the default parition sizes are ludicrous. Get rid of /export/home and add its size to /

Similar Messages

Live Upgrade with Zones - still not working ?

Hi Guys,
I'm trying to do LiveUpdate from Solaris update 3 to update 4 with non-global zone installed. It's driving me crazy now.
I did everything as described in documentation, installed SUNWlucfg and supposedly updated SUNWluu and SUNWlur (supposedly because they are exactly the same as were in update 3) both from packages and with script from update 4 DVD, installed all patches mentioned in 72099, but lucreate process still complains about missing patches and I've checked if they're installed five times. They are. It doesn't even allow to create second BE. Once I detached Zone - everything went smooth, but I had an impression that Live Upgrade with Zones will work in Update 4.
It did create second BE before SUNWlucfg was installed, but failed on update stage with exactly the same message - install patches according to 72099. After installation of SUNWlucfg Live Upgrade process fails instantly, that's a real progress, must admit.
Is it still "mission impossible" to Live Upgrade with non-global zones installed ? Or am I missed something ?
Any ideas or success stories are greatly appreciated. Thanks.

I upgraded from u3 to u5.
The upgrade went fine, the zones boot up but there are problems.
sshd doesn't work
svsc -vx prints out this.
svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Fri Apr 18 09:54:33 2008
Reason: Restarter svc:/network/inetd:default is not running.
See: http://sun.com/msg/SMF-8000-5H
See: man -M /usr/share/man -s 1M gssd
Impact: 8 dependent services are not running:
svc:/network/nfs/client:default
svc:/system/filesystem/autofs:default
svc:/system/system-log:default
svc:/milestone/multi-user:default
svc:/system/webconsole:console
svc:/milestone/multi-user-server:default
svc:/network/smtp:sendmail
svc:/network/ssh:default
svc:/network/inetd:default (inetd)
State: maintenance since Fri Apr 18 09:54:41 2008
Reason: Restarting too quickly.
See: http://sun.com/msg/SMF-8000-L5
See: man -M /usr/share/man -s 1M inetd
See: /var/svc/log/network-inetd:default.log
Impact: This service is not running.
It seems as thought the container is not upgraded.
more /etc/release in the container shows this
Solaris 10 11/06 s10s_u3wos_10 SPARC
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 14 November 2006
How do I get it to fix the inetd service?

Upgrading secure zone

Hi all,
I am looking to create a free trial secure zone and let users upgrade to a paid secure zone after 2 months.
When i pre-populate the fields with their username and email (the user will be logged into their trial account to access this form), when they submit the form, does business catalyst automatically add the new secure zone to the existing account, such that the account that the current user has will be subscribed to 2 secure zones?
Also, is it possible to program it such that the system will automatically send a notification via email when the user's subscription is about to expire? Like 2 weeks in advance,,

Hi,
Most likely you are under site plan webBasic or webBasic+ which does not include Secure Zone features.
For a breakdown of features per plan please view here. -> http://helpx.adobe.com/business-catalyst/kb/detailed-plan-breakdown.html
For information on how to upgrade your Muse site you may want to visit this thread below.
- http://forums.adobe.com/message/4827272#4827272
Hope this helps!
-Sidney

Zone issue in Solaris10

Hi Experts
I have small problem and doubt
If i login to global zone ... "zlogin -C -e @ testzone" how to logout from global zone......
testzone# when i press exit button it is comeing to zone login prompt
zone1 console login: @ ( from Zone login prompt i want to come
back to my normal solaris prompt i tried with pressing "shift+@ "
nothing is happening could you please tell me how to come out from zonelogin prompt ................
one more query after installation we are using " zlogin -C -e testzone "
is it rquire this same login commmand we have to use every time or only one time after installation of zone. we can use
"zlogin testzone " also what is difrrent these two... if you use " zlogin -C -e testzone " then only it will prompt for locale and language settings......
i have seen it is asking for locale setting and language ...... and it is asking only one time but if you use "zlogin testzone" it won't ask any such seetings......( only one time it will ask after the zone configuration)
Thanks

Same response as for your other posting.
http://forum.java.sun.com/thread.jspa?messageID=9755130ﳶ&#56826;
You are in the wrong forum.
Go to the forum for Solaris Zones.
http://forum.java.sun.com/index.jspa?tab=solaris

Live upgrade with zones

Hi,
While trying to create a new be environment in solaris 10 update 6 i 'm getting following errors for my zone
Updating compare databases on boot environment <zfsBE>.
Making boot environment <zfsBE> bootable.
ERROR: unable to mount zones:
zoneadm: zone 'OTM1_wa_lab': "/usr/lib/fs/lofs/mount -o ro /.alt.tmp.b-AKc.mnt/swdump /zones/app/OTM1_wa_lab-zfsBE/lu/a/swdump" failed with exit code 33
zoneadm: zone 'OTM1_wa_lab': call to zoneadmd failed
ERROR: unable to mount zone <OTM1_wa_lab> in </.alt.tmp.b-AKc.mnt>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.1>
ERROR: Unable to remount ABE <zfsBE>: cannot make ABE bootable
ERROR: no boot environment is mounted on root device <rootpool/ROOT/zfsBE>
Making the ABE <zfsBE> bootable FAILED.
Although my zone is running fine
zoneadm -z OTM1_wa_lab list -v
ID NAME STATUS PATH BRAND IP
3 OTM1_wa_lab running /zones/app/OTM1_wa_lab native shared
Does any body know what could be the reason for this ?

http://opensolaris.org/jive/thread.jspa?messageID=322728

Solaris10 branded zone creation error on Solaris 11.1

Hello,
We are having the problem in creating the Solaris10 branded zone on the solaris 11.1 version. We are trying to install this branded zone using the solaris10 VM template. Please can some one through some pointers ?
The installation steps stops at "Waiting for boot to complete" but never successfully boots even waiting for long times. We can see that Zone status in configured only.
root@localhost:~# /home/solaris-10u10-sparc.bin -p /solaris10 -i net0 -a xxx.xxx.xxx.xxx -z zone10
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.
Checking disk-space for extraction
Ok
Extracting in /root/bootimage.dnaqaD ...
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.
IMAGE: /home/solaris-10u10-sparc.bin
ZONE: zone10
ZONEPATH: /solaris10/zone10
INTERFACE: net0
VNIC: vnicZBI6783
MAC ADDR: 2:8:20:5c:92:f5
IP ADDR: xxx.xxx.xxx.xxx
NETMASK: 255.0.0.0
DEFROUTER: # # This file is deprecated. Default routes will be created for any router # addresses specified here, but they will not change when the underlying # network configuration profile (NCP) changes. For NCP-specific static # routes, the '-p' option of the route(1M) command should be used. # # See netcfg(1M) for information about network configuration profiles. #
TIMEZONE: Asia/Kolkata
Checking disk-space for installation
Ok
Installing in /solaris10/zone10 ...
100% [===============================>]
Using a static exclusive-IP
./setupSysidcfgStaticIP[50]: file/sysidcfg.zone10: cannot create [No such file or directory]
cp: cannot access file/sysidcfg.zone10
chmod: WARNING: can't access file/sysidcfg.zone10
Attaching zone10
Booting zone10
zoneadm: zone 'zone10': must be installed before boot.
Waiting for boot to complete
booting...
booting...
booting...
root@localhost:# zoneadm list -cv
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
4 zone1 running /zone1 solaris excl
5 zone2 running /zone2 solaris excl
- zone10 configured /solaris10/zone10 solaris10 excl
root@localhost:#
I have installed the package pkg:/system/zones/brand/brand-solaris10 on the system.
# cat /etc/release
Oracle Solaris 11.1 SPARC
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
Assembled 19 September 2012

Sorry, please ignore my previous message about the wrong ip address (I assume you entered a valid ip address).
The problem you are facing is related to the defaultrouter, and I assume you are running Solaris 11 update 1.
If so, to workaround the problem for the time being you may edit the /etc/defaultrouter file in the global-zone and enter the ip address of the default router (you can remove this change when the template deployment is completed).
If you have no idea about the default router ip address, just rename /etc/defaultrouter (e.g. to /etc/defaultrouter.orig) so that it cannot be found by the template. Again, you can undo the change when deployment is complete.
Thierry

Live Upgrade fails on cluster node with zfs root zones

We are having issues using Live Upgrade in the following environment:
-UFS root
-ZFS zone root
-Zones are not under cluster control
-System is fully up to date for patching
We also use Live Upgrade with the exact same same system configuration on other nodes except the zones are UFS root and Live Upgrade works fine.
Here is the output of a Live Upgrade:
bash-3.2# lucreate -n sol10-20110505 -m /:/dev/md/dsk/d302:ufs,mirror -m /:/dev/md/dsk/d320:detach,attach,preserve -m /var:/dev/md/dsk/d303:ufs,mirror -m /var:/dev/md/dsk/d323:detach,attach,preserve
Determining types of file systems supported
Validating file system requests
The device name </dev/md/dsk/d302> expands to device path </dev/md/dsk/d302>
The device name </dev/md/dsk/d303> expands to device path </dev/md/dsk/d303>
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <sol10> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Updating system configuration files.
The device </dev/dsk/c0t1d0s0> is not a root device for any boot environment; cannot get BE ID.
Creating configuration for boot environment <sol10-20110505>.
Source boot environment is <sol10>.
Creating boot environment <sol10-20110505>.
Creating file systems on boot environment <sol10-20110505>.
Preserving <ufs> file system for </> on </dev/md/dsk/d302>.
Preserving <ufs> file system for </var> on </dev/md/dsk/d303>.
Mounting file systems for boot environment <sol10-20110505>.
Calculating required sizes of file systems for boot environment <sol10-20110505>.
Populating file systems on boot environment <sol10-20110505>.
Checking selection integrity.
Integrity check OK.
Preserving contents of mount point </>.
Preserving contents of mount point </var>.
Copying file systems that have not been preserved.
Creating shared file system mount points.
Creating snapshot for <data/zones/img1> on <data/zones/img1@sol10-20110505>.
Creating clone for <data/zones/img1@sol10-20110505> on <data/zones/img1-sol10-20110505>.
Creating snapshot for <data/zones/jdb3> on <data/zones/jdb3@sol10-20110505>.
Creating clone for <data/zones/jdb3@sol10-20110505> on <data/zones/jdb3-sol10-20110505>.
Creating snapshot for <data/zones/posdb5> on <data/zones/posdb5@sol10-20110505>.
Creating clone for <data/zones/posdb5@sol10-20110505> on <data/zones/posdb5-sol10-20110505>.
Creating snapshot for <data/zones/geodb3> on <data/zones/geodb3@sol10-20110505>.
Creating clone for <data/zones/geodb3@sol10-20110505> on <data/zones/geodb3-sol10-20110505>.
Creating snapshot for <data/zones/dbs9> on <data/zones/dbs9@sol10-20110505>.
Creating clone for <data/zones/dbs9@sol10-20110505> on <data/zones/dbs9-sol10-20110505>.
Creating snapshot for <data/zones/dbs17> on <data/zones/dbs17@sol10-20110505>.
Creating clone for <data/zones/dbs17@sol10-20110505> on <data/zones/dbs17-sol10-20110505>.
WARNING: The file </tmp/.liveupgrade.4474.7726/.lucopy.errors> contains a
list of <2> potential problems (issues) that were encountered while
populating boot environment <sol10-20110505>.
INFORMATION: You must review the issues listed in
</tmp/.liveupgrade.4474.7726/.lucopy.errors> and determine if any must be
resolved. In general, you can ignore warnings about files that were
skipped because they did not exist or could not be opened. You cannot
ignore errors such as directories or files that could not be created, or
file systems running out of disk space. You must manually resolve any such
problems before you activate boot environment <sol10-20110505>.
Creating compare databases for boot environment <sol10-20110505>.
Creating compare database for file system </var>.
Creating compare database for file system </>.
Updating compare databases on boot environment <sol10-20110505>.
Making boot environment <sol10-20110505> bootable.
ERROR: unable to mount zones:
WARNING: zone jdb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/jdb3-sol10-20110505 does not exist.
WARNING: zone posdb5 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/posdb5-sol10-20110505 does not exist.
WARNING: zone geodb3 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/geodb3-sol10-20110505 does not exist.
WARNING: zone dbs9 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs9-sol10-20110505 does not exist.
WARNING: zone dbs17 is installed, but its zonepath /.alt.tmp.b-tWc.mnt/zoneroot/dbs17-sol10-20110505 does not exist.
zoneadm: zone 'img1': "/usr/lib/fs/lofs/mount /.alt.tmp.b-tWc.mnt/global/backups/backups/img1 /.alt.tmp.b-tWc.mnt/zoneroot/img1-sol10-20110505/lu/a/backups" failed with exit code 111
zoneadm: zone 'img1': call to zoneadmd failed
ERROR: unable to mount zone <img1> in </.alt.tmp.b-tWc.mnt>
ERROR: unmounting partially mounted boot environment file systems
ERROR: cannot mount boot environment by icf file </etc/lu/ICF.2>
ERROR: Unable to remount ABE <sol10-20110505>: cannot make ABE bootable
ERROR: no boot environment is mounted on root device </dev/md/dsk/d302>
Making the ABE <sol10-20110505> bootable FAILED.
ERROR: Unable to make boot environment <sol10-20110505> bootable.
ERROR: Unable to populate file systems on boot environment <sol10-20110505>.
ERROR: Cannot make file systems for boot environment <sol10-20110505>.
Any ideas why it can't mount that "backups" lofs filesystem into /.alt? I am going to try and remove the lofs from the zone configuration and try again. But if that works I still need to find a way to use LOFS filesystems in the zones while using Live Upgrade
Thanks

I was able to successfully do a Live Upgrade with Zones with a ZFS root in Solaris 10 update 9.
When attempting to do a "lumount s10u9c33zfs", it gave the following error:
ERROR: unable to mount zones:
zoneadm: zone 'edd313': "/usr/lib/fs/lofs/mount -o rw,nodevices /.alt.s10u9c33zfs/global/ora_export/stage /zonepool/edd313 -s10u9c33zfs/lu/a/u04" failed with exit code 111
zoneadm: zone 'edd313': call to zoneadmd failed
ERROR: unable to mount zone <edd313> in </.alt.s10u9c33zfs>
ERROR: unmounting partially mounted boot environment file systems
ERROR: No such file or directory: error unmounting <rpool1/ROOT/s10u9c33zfs>
ERROR: cannot mount boot environment by name <s10u9c33zfs>
The solution in this case was:
zonecfg -z edd313
info ;# display current setting
remove fs dir=/u05 ;#remove filesystem linked to a "/global/" filesystem in the GLOBAL zone
verify ;# check change
commit ;# commit change
exit

Live upgrade, zones and separate mount points

Hi,
We have a quite large zone environment based on Solaris zones located on VxVM/VxFS. I know this is a doubtful configuration but the choice was made before i got here and now we need to upgrade the environment. Veritas guides says its fine to locate zones on Veritas, but i am not sure Sun would approve.
Anyway, sine all zones are located on a separate volume i want to create a new one for every zonepath, something like:
lucreate -n upgrade -m /:/dev/dsk/c2t1d0s0:ufs -m /zones/zone01:/dev/vx/dsk/zone01/zone01_root02:ufs
This works fine for a while after integration of 6620317 in 121430-23, but when the new environment is to be activated i get errors, see below[1]. If i look at the command executed by lucreate i see that the global root is mounted, but by zoneroot does not seem to have been mounted before the call to zoneadmd[2]. While this might not be a supported configuration, VxVM seems to be supported and i think that there are a few people out there with zonepaths on separate disks. Live upgrade probably has no issues with the files moved from the VxFS filesystem, that parts has been done, but the new filesystems does not seem to get mounted correctly.
Anyone tried something similar or has any idea on how to solve this?
The system is a s10s_u4 with kernel 127111-10 and Live upgrade patches 121430-25, 121428-10.
1:
Integrity check OK.
Populating contents of mount point </>.
Populating contents of mount point </zones/zone01>.
Copying.
Creating shared file system mount points.
Copying root of zone <zone01>.
Creating compare databases for boot environment <upgrade>.
Creating compare database for file system </zones/zone01>.
Creating compare database for file system </>.
Updating compare databases on boot environment <upgrade>.
Making boot environment <upgrade> bootable.
ERROR: unable to mount zones:
zoneadm: zone 'zone01': can't stat /.alt.upgrade/zones/zone01/root: No such file or directory
zoneadm: zone 'zone01': call to zoneadmd failed
ERROR: unable to mount zone <zone01> in </.alt.upgrade>
ERROR: unmounting partially mounted boot environment file systems
ERROR: umount: warning: /dev/dsk/c2t1d0s0 not in mnttab
umount: /dev/dsk/c2t1d0s0 not mounted
ERROR: cannot unmount </dev/dsk/c2t1d0s0>
ERROR: cannot mount boot environment by name <upgrade>
ERROR: Unable to determine the configuration of the target boot environment <upgrade>.
ERROR: Update of loader failed.
ERROR: Unable to umount ABE <upgrade>: cannot make ABE bootable.
Making the ABE <upgrade> bootable FAILED.
ERROR: Unable to make boot environment <upgrade> bootable.
ERROR: Unable to populate file systems on boot environment <upgrade>.
ERROR: Cannot make file systems for boot environment <upgrade>.
2:
0 21191 21113 /usr/lib/lu/lumount -f upgrade
0 21192 21191 /etc/lib/lu/plugins/lupi_bebasic plugin
0 21193 21191 /etc/lib/lu/plugins/lupi_svmio plugin
0 21194 21191 /etc/lib/lu/plugins/lupi_zones plugin
0 21195 21192 mount /dev/dsk/c2t1d0s0 /.alt.upgrade
0 21195 21192 mount /dev/dsk/c2t1d0s0 /.alt.upgrade
0 21196 21192 mount -F tmpfs swap /.alt.upgrade/var/run
0 21196 21192 mount swap /.alt.upgrade/var/run
0 21197 21192 mount -F tmpfs swap /.alt.upgrade/tmp
0 21197 21192 mount swap /.alt.upgrade/tmp
0 21198 21192 /bin/sh /usr/lib/lu/lumount_zones -- /.alt.upgrade
0 21199 21198 /bin/expr 2 - 1
0 21200 21198 egrep -v ^(#|global:) /.alt.upgrade/etc/zones/index
0 21201 21198 /usr/sbin/zonecfg -R /.alt.upgrade -z test exit
0 21202 21198 false
0 21205 21204 /usr/sbin/zoneadm -R /.alt.upgrade list -i -p
0 21206 21204 sed s/$[^\]$::/\1:-:/
0 21207 21203 zoneadm -R /.alt.upgrade -z zone01 mount
0 21208 21207 zoneadmd -z zone01 -R /.alt.upgrade
0 21210 21203 false
0 21211 21203 gettext unable to mount zone <%s> in <%s>
0 21212 21203 /etc/lib/lu/luprintf -Eelp2 unable to mount zone <%s> in <%s> zone01 /.alt.up
Edited by: henrikj_ on Sep 8, 2008 11:55 AM Added Solaris release and patch information.

I updated my manual pages got a reminder of the zonename field for the -m option of lucreate. But i still have no success, if i have the root filesystem for the zone in vfstab it tries to mount it the current root into the alternate BE:
# lucreate -u upgrade -m /:/dev/dsk/c2t1d0s0:ufs -m /:/dev/vx/dsk/zone01/zone01_rootvol02:ufs:zone01
<snip>
Creating file systems on boot environment <upgrade>.
Creating <ufs> file system for </> in zone <global> on </dev/dsk/c2t1d0s0>.
Creating <ufs> file system for </> in zone <zone01> on </dev/vx/dsk/zone01/zone01_rootvol02>.
Mounting file systems for boot environment <upgrade>.
ERROR: UX:vxfs mount: ERROR: V-3-21264: /dev/vx/dsk/zone01/zone01_rootvol is already mounted, /.alt.tmp.b-gQg.mnt/zones/zone01 is busy,
allowable number of mount points exceeded
ERROR: cannot mount mount point </.alt.tmp.b-gQg.mnt/zones/zone01> device </dev/vx/dsk/zone01/zone01_rootvol>
ERROR: failed to mount file system </dev/vx/dsk/zone01/zone01_rootvol> on </.alt.tmp.b-gQg.mnt/zones/zone01>
ERROR: unmounting partially mounted boot environment file systems
If i tried to do the same but with the filesystem removed from vfstab, then i get another error:
<snip>
Creating boot environment <upgrade>.
Creating file systems on boot environment <upgrade>.
Creating <ufs> file system for </> in zone <global> on </dev/dsk/c2t1d0s0>.
Creating <ufs> file system for </> in zone <zone01> on </dev/vx/dsk/zone01/zone01_upgrade>.
Mounting file systems for boot environment <upgrade>.
Calculating required sizes of file systems for boot environment <upgrade>.
Populating file systems on boot environment <upgrade>.
Checking selection integrity.
Integrity check OK.
Populating contents of mount point </>.
Populating contents of mountED.
ERROR: Unable to make boot environment <upgrade> bootable.
ERROR: Unable to populate file systems on boot environment <upgrade>.
ERROR: Cannot make file systems for boot environment <upgrade>.
If i let lucreate copy the zonepath to the same slice as the OS, the creation of the BE works fine:
# lucreate -n upgrade -m /:/dev/dsk/c2t1d0s0:ufs

Is it possible to patch Global Zone and only specific Non-Global Zones?

Hi Champs,
Is it possible to patch Global Zone and only specific Non-Global Zones? Idea is to patch DEV-zones only on the system & test applications and then patch only the STG-zones on same server!
Not sure if it is possible but just throwing a question...
Cheers,
Nitin

M10vir wrote:
Yes, if you have branded (non-sparse) zone!Branded zones and sparse zones don't have the relation that you imply. In Solaris 10, native zones can be sparse or whole-root (non-sparse, as you say). Zones that are not native zones are branded zones. Branded zones on Solaris 10 include Solaris Legacy Containers, previously known as Solaris 8 Containers and Solaris 9 Containers. That add-on product allows you to run Solaris 8 and Solaris 9 application environments under a thin layer of virtualization provided by the brands framework. solaris8 and solaris9 branded zones can be patched independently of each other and of the global zone.
Solaris 11 has no "native zones" - all zones use the brands framework. The "solaris" brand does no emulation and in that respect is very similar to native zones on Solaris 10. Solaris 11 also provides Solaris 10 Zones via the solaris10 brand. This allows zones or the global zone from a Solaris 10 system to be transferred to a Solaris 11 system and run as solaris10 zones. When running on Solaris 11, solaris10 zones can each be patched independently from each other and the Solaris 11 global zone. Technically, Solaris 11 doesn't have patches - it just has newer versions of packages to which the system is updated.

Zone creation

Hi,
My machine is x86 , OS is winxp
Iam using solaris10 running on VMware player. I have created a test zone on solaris10 using solaris9 container and down loaded solaris9-image.flar and saved on Apps folder. But iam unable to install solaris9-image.flar to test zone.
#zonecfg -z testzone info
zonepath: /zones/testzone
autoboot:true
pool:
inherit-pkg-dir:
dir: /lib
inherit-pkg-dir:
dir: /platform
inherit-pkg-dir:
dir: /sbin
inherit-pkg-dir:
dir: /usr
net:
address:
Physical:
#zoneadm -z testzone install -u -a /Apps/solaris9-image.flar
-u: illegal option --u
usage: install
install the configuration on to the system
As iam new in solaris can anyone help on regard this......Thanks in advance.
Arunii2

one more thing, I just noticed, that you are using X86 solaris. so have a look at this:
"A Solaris 9 branded zone (solaris9) is a complete runtime environment for Solaris 9 applications on *SPARC* machines running the Solaris 10 8/07 Operating System or later."
http://docs.sun.com/app/docs/doc/820-4490/gfjbk?a=view
so, you won't be able to test those things on x86 machine.
Laszlo

Multicast between zones in Solaris 10 3/05

Hi
We have a Solaris 10 3/05 installation, with different zones. We have written a pair of test programs to test multicast traffic between zones: one of them joins a given IP/port, and the other sends datagrams with dummy text to a given IP/port. We want to ensure multicast traffic between zones using 239.255.2.3, port 6155/6156 works seamlessly.
We started trying that IP between different machines (with no zones, or between global zones in different machines), and it worked. Then we tried between a non-global zone and the global zone of the same machine, and it worked. But then we tried between different zones in the same machine, and it didn't worked: datagrams are not reaching other zones but the global one.
�Any ideas about this? Using 239.255.2.3 is a must, and being a valid multicast IP, it should work out-of-the-box. All zones have an exclusive IP, and are in the same subnet (also the global zone).
Edited by: E.Corral on Aug 22, 2008 5:49 AM

The zones stuff is tightly integrated with much of the other OS infrastructure eg kernel, libraries etc.
Its not possible to upgrade just the zones stuff by installing packages.
You could upgrade the zones stuff by applying patches, but it will drag a lot of other stuff in as preqrequisites.
Just installing a recommended patch set should accomplish this.
But it may be simpler to just upgrade to 5/08 and be done with it. Liveupgade or upgrade install should work.

Discover4i Applications 11.5.9 Solaris10

Hi folks,
I am currently cloning an EBS 11.5.9 running on Solaris9 to Solaris10. I am having problems with discoverer4i, and in particular the oadutil script and the vbj executable.
The vbj executable is core dumping.
So, I can start the osagent, the oad, but when I go to run unregistersession.sh, registersession.sh, registerall.sh or any other script that references oadutil/vbj.
The JDK is the same on Soalris9 and Solaris 10, 1.3.1_08.
Anyone experienced this before?

Hi All,
here is the relevant output from adstrtal.sh
addisctl.sh version 115.9
/d26/oracle/CRMR11/crmprodora/8.0.6/vbroker/bin/osagent
Started osagent.
Osagent logs messages to the file /d26/oracle/CRMR11/crmprodora/8.0.6/discwb4/uti
l/osagent.log.
Waiting for OAD to start...
Started OAD.
OAD logs messages to the file /d26/oracle/CRMR11/crmprodora/8.0.6/discwb4/util/oa
d.log.
Failed to start locator.
Cannot bind to OAD. Re-starting...
OAD is stopped
Osagent is stopped
Unable to stop locator. No process-id file found.
Unable to stop gatekeeper. No process-id file found.
No other discoverer processes running
/d26/oracle/CRMR11/crmprodora/8.0.6/vbroker/bin/osagent
Started osagent.
Osagent logs messages to the file /d26/oracle/CRMR11/crmprodora/8.0.6/discwb4/uti
l/osagent.log.
Waiting for OAD to start...
Started OAD.
OAD logs messages to the file /d26/oracle/CRMR11/crmprodora/8.0.6/discwb4/util/oa
d.log.
Failed to start locator.
Registering Discoverer Session
Registering the Collector
Applying preferences from file : /d26/oracle/CRMR11/crmprodora/8.0.6/discwb4/util
/pref.txt
Finished applying preferences
Closing down registry..
Registry File sync...
Registering Discoverer Preference Repository
addisctl.sh: exiting with status 134
.end std out.
SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation

Compilation problem on solaris9 x86

I am working on JAVA/J2EE . Am new to solaris9 . My requirement is to compile a source distribution of MOD-JK 1.2.21 (apache 2.0 server connector)and to produce binary distribution (*.so file) in solaris9 X86 box. But i got only source distribution of solaris10 X86 platform . Even with this source i tried to compile in solaris9 box its giving some error message and i can't able to make a executable file. Below i pasted the error message .
# ./configure -with-apxs=/usr/apache2/bin/apxs
checking build system type... i386-pc-solaris2.10
checking host system type... i386-pc-solaris2.10
checking target system type... i386-pc-solaris2.10
checking for a BSD-compatible install... scripts/build/unix/install-sh -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... no
checking for gcc... no
checking for cc... cc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
Can any body help me in this regards. Even i don't know, am proceeding in right direction to compile this file. If any body having the binary distribution for the same MOD-JK1.2.21 on solaris9 or solaris10 X86 platform for apache2.0 . please help me to compile this file .I given below the config.log file entries also.
Thanks in advance..........
karthikeyan.u
[email protected]
AIM or AOL :: karthikeyanu
CONFIG.log entries......
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.59. Invocation command line was
$ ./configure -with-apxs=/usr/apache2/bin/apxs
## Platform. ##
hostname = Solaris
uname -m = i86pc
uname -r = 5.10
uname -s = SunOS
uname -v = Generic_118844-26
/usr/bin/uname -p = i386
/bin/uname -X = System = SunOS
Node = Solaris
Release = 5.10
KernelID = Generic_118844-26
Machine = i86pc
BusType = <unknown>
Serial = <unknown>
Users = <unknown>
OEM# = 0
Origin# = 1
NumCPU = 1
/bin/arch = i86pc
/usr/bin/arch -k = i86pc
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/sbin
PATH: /usr/bin
PATH: /usr/openwin/bin
PATH: /usr/ucb
## Core tests. ##
configure:1546: checking build system type
configure:1564: result: i386-pc-solaris2.10
configure:1572: checking host system type
configure:1586: result: i386-pc-solaris2.10
configure:1594: checking target system type
configure:1608: result: i386-pc-solaris2.10
configure:1640: checking for a BSD-compatible install
configure:1695: result: scripts/build/unix/install-sh -c
configure:1706: checking whether build environment is sane
configure:1749: result: yes
configure:1814: checking for gawk
configure:1843: result: no
configure:1814: checking for mawk
configure:1843: result: no
configure:1814: checking for nawk
configure:1830: found /usr/bin/nawk
configure:1840: result: nawk
configure:1850: checking whether make sets $(MAKE)
configure:1874: result: no
configure:2085: checking for gcc
configure:2114: result: no
configure:2165: checking for cc
configure:2181: found /usr/ucb/cc
configure:2191: result: cc
configure:2355: checking for C compiler version
configure:2358: cc --version </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:2361: $? = 1
configure:2363: cc -v </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:2366: $? = 1
configure:2368: cc -V </dev/null >&5
/usr/ucb/cc: language optional software package not installed
configure:2371: $? = 1
configure:2394: checking for C compiler default output file name
configure:2397: cc conftest.c >&5
/usr/ucb/cc: language optional software package not installed
configure:2400: $? = 1
configure: failed program was:
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "mod_jk"
| #define VERSION "1.2.21"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2439: error: C compiler cannot create executables
See `config.log' for more details.
## Cache variables. ##
ac_cv_build=i386-pc-solaris2.10
ac_cv_build_alias=i386-pc-solaris2.10
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_host=i386-pc-solaris2.10
ac_cv_host_alias=i386-pc-solaris2.10
ac_cv_prog_AWK=nawk
ac_cv_prog_ac_ct_CC=cc
ac_cv_prog_make_make_set=no
ac_cv_target=i386-pc-solaris2.10
ac_cv_target_alias=i386-pc-solaris2.10
## Output variables. ##
ACLOCAL='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run aclocal-1.9'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run tar'
APACHE20_OEXT=''
APACHE_CONFIG_VARS=''
APACHE_DIR=''
APXS=''
APXSCFLAGS=''
APXSCPPFLAGS=''
APXSLDFLAGS=''
AR=''
AUTOCONF='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run autoconf'
AUTOHEADER='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run autoheader'
AUTOMAKE='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run automake-1.9'
AWK='nawk'
CC='cc'
CCDEPMODE=''
CFLAGS=''
CP=''
CPP=''
CPPFLAGS=''
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
F77=''
FFLAGS=''
GREP=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
INSTALL_TYPE=''
JAVA_HOME=''
JK_JNI_WORKER=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIB_JK_TYPE=''
LN_S=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/missing --run makeinfo'
MAKE_DYNAMIC_APACHE_FALSE=''
MAKE_DYNAMIC_APACHE_TRUE=''
MKDIR=''
OBJEXT=''
OS=''
PACKAGE='mod_jk'
PACKAGE_BUGREPORT=''
PACKAGE_NAME=''
PACKAGE_STRING=''
PACKAGE_TARNAME=''
PACKAGE_VERSION=''
PATH_SEPARATOR=':'
PERL=''
RANLIB=''
RM=''
SED=''
SET_MAKE='MAKE=make'
SHELL='/bin/bash'
STRIP=''
TEST=''
VERSION='1.2.21'
WEBSERVER=''
ac_ct_AR=''
ac_ct_CC='cc'
ac_ct_CXX=''
ac_ct_F77=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
apache_include=''
bindir='${exec_prefix}/bin'
build='i386-pc-solaris2.10'
build_alias=''
build_cpu='i386'
build_os='solaris2.10'
build_vendor='pc'
datadir='${prefix}/share'
exec_prefix='NONE'
host='i386-pc-solaris2.10'
host_alias=''
host_cpu='i386'
host_os='solaris2.10'
host_vendor='pc'
includedir='${prefix}/include'
infodir='${prefix}/info'
install_sh='/export/home/dump_208/workspace_SB_563/modjk/ModJK1/modjk/jkk/tomcat-connectors-1.2.21-src/native/scripts/build/unix/install-sh'
int32_t_fmt=''
int32_value=''
int64_t_fmt=''
int64_value=''
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
mkdir_p='$(install_sh) -d'
oldincludedir='/usr/include'
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target='i386-pc-solaris2.10'
target_alias=''
target_cpu='i386'
target_os='solaris2.10'
target_vendor='pc'
uint32_t_fmt=''
uint32_t_hex_fmt=''
uint64_t_fmt=''
uint64_t_hex_fmt=''
## confdefs.h. ##
#define PACKAGE "mod_jk"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_NAME ""
#define PACKAGE_STRING ""
#define PACKAGE_TARNAME ""
#define PACKAGE_VERSION ""
#define VERSION "1.2.21"
configure: exit 77

You need to make sure the source is for the same version i.e. if you run apache 2.0.52 you need the source of 2.0.52. I successfully ran mixed installs, but I would not recommend it. You can download the required source from Apache.
As for your compiler problem, make sure you have �/usr/ccs/bin/� in the your path, if you do not have it installed you will have to add the pkg �SUNWsprot�. You do not have 'make' in yout path.
Make sure you have the following packages installed:
SUNWbtool, SUNWsprot, SUNWtoo
SUNWhea, SUNWarc, SUNWlibm, SUNWlibms
SUNWdfbh, SUNWcg6h, SUNWxwinc, SUNWolinc,
SUNWxglh,SUNWarcx, SUNWbtoox, SUNWdplx,
SUNWscpux, SUNWsprox, SUNWlmsx, SUNWlmx
SUNWlibCx, SUNWtoox, SUNWsra, SUNWsrh

P2v migration,brandzone solaris10 on solaris 11-Exiting with exit code 254

hi...
doing p2v migration on vmware : solaris 10 as branded zone on solaris 11
im moving my physical machine solaris 10 to brand zone as in soialris 11
some how im facing the issues..while zone installation
it fails at the end
follwing are the logs::
root@solaris11:/var/log/zones# tail -f zoneadm.20120304T231155Z.s10zone.install
[Monday, March 5, 2012 04:42:03 AM IST] | install_flar
[Monday, March 5, 2012 04:42:07 AM IST] setting ZFS property zoned=on on zpool1/zones/rpool
[Monday, March 5, 2012 04:42:10 AM IST] setting ZFS property canmount=on on zpool1/zones/rpool
[Monday, March 5, 2012 04:42:10 AM IST] setting ZFS property mountpoint=/rpool on zpool1/zones/rpool
[Monday, March 5, 2012 04:42:14 AM IST] setting ZFS property canmount=noauto on zpool1/zones/rpool/ROOT
[Monday, March 5, 2012 04:42:14 AM IST] setting ZFS property mountpoint=legacy on zpool1/zones/rpool/ROOT
[Monday, March 5, 2012 04:42:15 AM IST] Creating active_ds zpool1/zones/rpool/ROOT/zbe-0
[Monday, March 5, 2012 04:42:16 AM IST] Mounting boot environment in zpool1/zones/rpool/ROOT/zbe-0 at /zpool1/zones/root (including child datasets)
[Monday, March 5, 2012 04:42:17 AM IST] Preparing to mount zpool1/zones/rpool/ROOT/zbe-0 at /zpool1/zones/root
[Monday, March 5, 2012 04:42:17 AM IST] Mounting zpool1/zones/rpool/ROOT/zbe-0 at /zpool1/zones/root/ with ZFS temporary mount
[Monday, March 5, 2012 05:23:37 AM IST] ERROR: Unpacking the archive failed
[Monday, March 5, 2012 05:23:37 AM IST] Destroying datasets under zpool1/zones that are not pinned
[Monday, March 5, 2012 05:24:57 AM IST] Destroyed unpinned dataset zpool1/zones/rpool/ROOT/zbe-0
[Monday, March 5, 2012 05:24:57 AM IST] Unpinning datasets under zpool1/zones
[Monday, March 5, 2012 05:24:58 AM IST] Unpinning zpool1/zones
[Monday, March 5, 2012 05:24:58 AM IST] Unpinning zpool1/zones/rpool
[Monday, March 5, 2012 05:24:58 AM IST] Unpinning zpool1/zones/rpool/ROOT
[Monday, March 5, 2012 05:24:58 AM IST] Unpinning zpool1/zones/rpool/export
[Monday, March 5, 2012 05:24:58 AM IST] Unpinning zpool1/zones/rpool/export/home
[Monday, March 5, 2012 05:24:58 AM IST] Exiting with exit code 254
[Monday, March 5, 2012 05:24:58 AM IST] ==== Completed: ====
zone configuration :
root@solaris11:/var/log/zones# zonecfg -z s10zone
zonecfg:s10zone> info
zonename: s10zone
zonepath: /zpool1/zones
brand: solaris10
autoboot: false
bootargs:
file-mac-profile:
pool:
limitpriv:
scheduling-class:
ip-type: exclusive
hostid: 0005b1bc
fs-allowed:
[max-lwps: 32500]
[max-processes: 16250]
attr:
name: zonep2vchk-info
type: string
value: "p2v of host test"
attr:
name: num-cpus
type: string
value: "original system had 2 cpus"
rctl:
name: zone.max-processes
value: (priv=privileged,limit=16250,action=deny)
rctl:
name: zone.max-lwps
value: (priv=privileged,limit=32500,action=deny)
will provide the truss o/p if needed..
my solaris 11 having the system/zones/brand/brand-solaris10
please guide me to clear the issue...any doc will really helpful....
thanks again
muvvas
Edited by: user13152599 on Mar 5, 2012 8:17 AM

source machine:::
bash-3.2# cat /etc/release
Solaris Express Community Edition snv_101a X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 31 October 2008
and its ufs
flarcreate -S -n s10-system /nfs/s10-system.flar
on target solaris 11::i have executed the following cmds::;
zonecfg -z s10-zone -f zone.config
zoneadm -z s10-zone install -u -a /export/home/muvvas/s10-system.flar
rpool 20G 39K 9.3G 1% /rpool
zpool1 47G 32K 40G 1% /zpool1
zpool1/zones 47G 6.5G 40G 14% /zpool1/zones

Cloning the branded zone

Hi
I have created a Solaris 10 branded zone on Solaris 11 SPARC system. Can I use clone option to clone the Solaris 10 zone to make a copy like we usually do with Sparse zones? Or is there any different way to clone the branded zones? Please point me to the document.
$ cat /etc/release
                            Oracle Solaris 11.1 SPARC
Copyright (c) 1983, 2012, Oracle and/or its affiliates. All rights reserved.
                           Assembled 19 September 2012
$ zoneadm list -iv
ID NAME             STATUS     PATH                           BRAND    IP
   0 global           running    /                              solaris shared
   1 s10-zone1        running    /zones/s10-zone1               solaris10 excl

okay. Thanks.
Is having the sysidcfg file mandatory for Branded zones? I think, I have never used them in the Sparse Zones. I had different files for configuration like /etc/defaultrouter, /etc/hosts, etc.. I guess in Branded zones, you do not need to have these files present or configured.. just have sysidcfg file, right? Or?

Upgrading a Zone - Solaris9 to Solaris10

Similar Messages

Maybe you are looking for