CREATING SOLARIS 8 BRANDED ZONE

Attempting to configure a Solaris8 branded zone on a SunFireV125 (running Sol10_10/09). Got to the "zoneadm -z s8-zone boot" step and configuring for NIS when I received the following error:
"The following error occurred while trying to set the netmask 255.255.248.0 on the network interface bge0:1: ioctl: Not owner"
Running ifconfig -a on the global zone, bge0:1 shows up but with only the IP address. Any ideas out there in Sun land? I've tried a few things (even google) but to no affect.
Btw, it is created as a shared-ip zone.
Thanks,

I would suggest setting the interface's netmask in the zone configuration.
As an example:
address=192.168.0.5/22
Cheers,

Similar Messages

[Solved] Arch Linux in a Solaris branded Zone

Hello,
After having read this article at the Genunix WiKi, I 'd very much like to install Arch Linux (http://204.152.191.100/wiki/index.php/I … anded_zone) in a Solaris branded Zone. However, the Arch Linux file to download is about two years old now, so I 'd like to roll one with a bit more recent kernel.
I just wonder what might be the procedure to do so.
a) Is it just unpacking the ISO inside the zone and let it enroll whilst booting?, or
b) is it advisable to install the old package and upgrade from there?
I am quite curious to learn how this works.
TIA, Algey
Last edited by algernonz (2011-11-28 18:42:31)

Hi,
it does indeed sound like an interesting little project. You should, however, revert to your procedure (a) and use one of the recent ISO images the Arch team has updated this year.
Using that old tar will give you numerous headaches when trying to upgrade. Doing a simple upgrade from that old file will most probably break the system, thats why they took the effort to provide the new ones.
Good luck.

Cannot create solaris 10 zone with flar archive

Hello,
i'm trying to configure a solaris zones with a flar archive of a solaris 10 system.
i've followed the procedure described here : http://www.sun.com/bigadmin/content/submitted/branded_zones_flash.jsp
whenever i try to create a zone and use: set brand=solaris10 the commit will fail with Unknown brand Missing document.
solaris version is Solaris 10 5/08 s10s_u5wos_10 SPARC and i have both the Solaris 8 and Solaris 9 container software installed.
is there another way to install a zone with the native brand or solaris 10 using an archive of some sort?
kind regards,

Thanks,
I've figured as much as using a whole root zone but i still struggle with the configuration of a solaris10 brand and the creation of a zone config with that brand.
I might be bettor of installing the zone without the flar image and try to copy the needed files and applications to the zone.
I only need the solaris10 brand zone to test the flar image so i can use it to restore the system with flar and jumpstart.

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.

Partial Install of base pkgs upon creating Solaris 10 zone

Greetings,
I have this weird situation when attempting to create a zone. Hoping I can get a bit of insight as to a resolution here.
The procedure I follow is:
root@was07:/root
zonecfg -z was07zonewas07zone: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:was07zone> create
zonecfg:was07zone> set autoboot=true
zonecfg:was07zone> set zonepath=/was07zone
zonecfg:was07zone> add net
zonecfg:was07zone:net> set address=xxx.xxx.xxx.107
zonecfg:was07zone:net> set physical=ce0
zonecfg:was07zone:net> end
zonecfg:was07zone> info
zonepath: /was07zone
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: xxx.xxx.xxx.107
physical: ce0
zonecfg:was07zone> verify
zonecfg:was07zone> commit
zonecfg:was07zone> exit
root@was07:/root
zoneadm -z was07zone installPreparing to install zone <was07zone>.
Creating list of files to copy from the global zone.
Copying <12701> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <937> packages on the zone.
Initialized <937> packages on zone.
Zone <was07zone> is initialized.
Installation of these packages generated warnings: <SUNWocfd SUNWkvm SUNWcsl SUNWcsr SUNWzlib SUNWgss SUNWopenssl-libraries SUNWsshcu SUNWsshdu SUNWperl584core SUNWperl584usr SUNWesu SUNWlibC SUNWlibms SUNWlexpt SUNWwbsup SUNWswmt SUNWbzip SUNWxwdv SUNWcpp SUNWctpls SUNWtecla SUNWtftp SUNWpr SUNWtls SUNWtnamd SUNWkrbu SUNWtnetc SUNWtnetd SUNWtoo SUNWudaplu SUNWudapltu SUNWudf SUNWnfscu SUNWlxml SUNWocf SUNWgzip SUNWadmlib-sysid SUNWadmap SUNWmdu SUNWadmc SUNWbip SUNWrcmdc SUNWrcmds SUNWscpu SUNWnisu SUNWfmd SUNWmdb SUNWpiclu SUNWlccom SUNWbsu SUNWnfssu SUNWidnl SUNWluxop SUNWadmfw SUNWinst SUNWipc SUNWipfu SUNWipmi SUNWiscsiu SUNWloc SUNWatfsu SUNWauda SUNWcfcl SUNWcfpl SUNWpcu SUNWpsu SUNWcnsu SUNWjfcau SUNWjss SUNWkey SUNWlibCf SUNWdtrc SUNWlibsasl SUNWllc SUNWlldap SUNWfchba SUNWfcmdb SUNWflexruntime SUNWftpu SUNWpkgcmdsu SUNWqusu SUNWrmodu SUNWroute SUNWsndmu SUNWsshu SUNWter SUNWgcmn SUNWtiu8 SUNWdoc SUNWvolu SUNWadmj SUNWwbapi SUNWaudit SUNWjsnmp SUNWwbcou SUNWjhrt SUNWwbpro SUNWxcu4 SUNWxcu6 SUNWeurf SUNWmgapp SUNWpmu SUNWowbcp SUNWlxsl SUNWzip SUNWsmbau SUNWscplp SUNWpool SUNWzoneu SUNWcpcu SUNW1251f SUNWGlib SUNWGtku SUNWTcl SUNWfruid SUNWfruip SUNWTk SUNWimagick SUNWbash SUNWpsutils SUNWa2psu SUNWbcp SUNWgsfot SUNWgsfst SUNWhpijs SUNWgimpprint SUNWgscr SUNWrsg SUNWgssdh SUNWgtar SUNWhiu8 SUNWhmdu SUNWiniu8 SUNWpapi SUNWippcore SUNWislcc SUNWisolc SUNWaudf SUNWciu8 SUNWjiu8 SUNWkiu8 SUNWbart SUNWbind SUNWgccruntime SUNWjcom SUNWppm SUNWpsf SUNWctlu SUNWjib SUNWffiltersu SUNWsmapi SUNWmdau SUNWfppd SUNWfss SUNWmibii SUNWsasnm SUNWsadmi SUNWmlib SUNWggrp SUNWntpu SUNWopenssl-commands SUNWpamsc SUNWpcsclite SUNWpsm-lpd SUNWqosu SUNWrcapu SUNWrmwbu SUNWscbcp SUNWscmhdlr SUNWslpu SUNWsmagt SUNWsmbac SUNWsmcmd SUNWtcatu SUNWtcpd SUNWprd SUNWtcsh SUNWpl5u SUNWtexi SUNWtlsd SUNWtlsu SUNWtnfc SUNWtnfd SUNWucbt SUNWugenu SUNWusbu SUNWwbdev SUNWwbdoc SUNWwbmc SUNWwebminu SUNWwgetu SUNWsprot SUNWxcu4t SUNWxsrt SUNWxrgrt SUNWxrpcrt SUNWmga SUNWrmui SUNWsadml SUNWypu SUNWzebrau SUNWzsh SUNW1394h SUNWaccu SUNWgpch SUNWpstl SUNWhea SUNWant SUNWapch2u SUNWapch2d SUNWapchu SUNWapchd SUNWbtool SUNWapct SUNWarc SUNWdclnt SUNWdhcsu SUNWdhcm SUNWipplu SUNWiqfs SUNWiquc SUNWiqum SUNWiqdoc SUNWladm SUNWiqjx SUNWfsmgtu SUNWdmgtu SUNWlvma SUNWlvmg SUNWiqu SUNWjhdev SUNWjato SUNWmctag SUNWmcon SUNWast SUNWpprou SUNWaudh SUNWbinutils SUNWbison SUNWbnuu SUNWcdrw SUNWjatodoc SUNWjatodmo SUNWjaxp SUNWcstl SUNWjhdem SUNWdfbh SUNWdhcsb SUNWdpl SUNWkdcu SUNWless SUNWlibm SUNWlibusb SUNWlibusbugen SUNWfac SUNWmcos SUNWflexlex SUNWmcosx SUNWmdbdm SUNWmddr SUNWftduu SUNWgcc SUNWmipu SUNWmkcd SUNWmlibe SUNWmlibh SUNWgm4 SUNWgmake SUNWmysqlu SUNWmysqlt SUNWncau SUNWncft SUNWocfh SUNWopenssl-include SUNWopenssl-man SUNWosdem SUNWpcsclite-devel SUNWpdu SUNWpiclh SUNWpl5v SUNWpl5p SUNWpmgr SUNWpppd SUNWpppdu SUNWpppdt SUNWpppg SUNWppro-plugin-sunos-base SUNWrpm SUNWrsm SUNWseru SUNWserweb SUNWsfdoc SUNWsfinf SUNWsfman SUNWsfwdemo SUNWsfwhea SUNWsmdoc SUNWspnego SUNWsra SUNWsrh SUNWcsu>
The file </was07zone/root/var/sadm/system/logs/install_log> contains a log of the zone installation.
All of the errors in the above log look like this:
*** package <SUNWcsr> installed with warnings:
pkgadd: ERROR: unable to create package object </was07zone/root/usr>.
unable to fix attributes
Installation of <SUNWcsr> on zone <was07zone> partially failed.
I have performed this procedure on 8 identical machines in the past week with no problems, except this one.
uname -aSunOS was07 5.10 Generic_118822-23 sun4u sparc SUNW,Sun-Fire-V440
cat /etc/releaseSolaris 10 3/05 s10_74L2a SPARC
Copyright 2005 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 22 January 2005
Now I can finish the the install and boot the zone just fine, but those packages are listed as partially installed, thusly when they are a prereq for any application, the application install fails with dependancy issues. If I try to install those pkgs, the dependancy loop gets very deep.
Plus I know that this isnt the expected results of my command chain above.
TIA for any assistance that can be provided.

One cant perform a zoneadm -z was07zone install
if the permissions on the zonepath are other than 700, correct?
/was07zone with permisisons=777
/was07zone must not be group readable.
/was07zone must not be group writable.
/was07zone must not be group executable.
/was07zone must not be world readable.
/was07zone must not be world writable.
/was07zone must not be world executable.
could not verify zonepath /was07zone because of the above errors.
zoneadm: zone was07zone failed to verify
/was07zone with permissions=755
/was07zone must not be group readable.
/was07zone must not be group executable.
/was07zone must not be world readable.
/was07zone must not be world executable.
could not verify zonepath /was07zone because of the above errors.
zoneadm: zone was07zone failed to verify
/was07zone with permissions=744
/was07zone must not be group readable.
/was07zone must not be world readable.
could not verify zonepath /was07zone because of the above errors.
zoneadm: zone was07zone failed to verify
/was07zone with permissions=711
/was07zone must not be group executable.
/was07zone must not be world executable.
could not verify zonepath /was07zone because of the above errors.
zoneadm: zone was07zone failed to verify
I did open up another terminal window while creating the zone.. and /was07zone/root is created with permisisons of 755

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.

Creating a Solaris 8 branded zone

I am in the process of configuring a Solaris 8 branded zone using the SUNWsolaris8 package and the instructions in the Solaris8 Container Guide. Solaris 10 08/07 is installed in the global zone. I have the following kernel patches installed as required: 127111-08 and 128548-08. I get the following error after configuring the zone when I try to verify the zone:
-bash-3.00# zonecfg -z gfxc-qazone
gfxc-qazone: No such zone configured
Use 'create' to begin configuring a new zone.
zonecfg:gfxc-qazone> create -t SUNWsolaris8
zonecfg:gfxc-qazone> set autoboot=true
zonecfg:gfxc-qazone> set zonepath=/export/zones/gfxc-qazone
zonecfg:gfxc-qazone> add attr
zonecfg:gfxc-qazone:attr> set name=machine
zonecfg:gfxc-qazone:attr> set type=string
zonecfg:gfxc-qazone:attr> set value=sun4u
zonecfg:gfxc-qazone:attr> end
zonecfg:gfxc-qazone> verify
gfxc-qazone: unknown brand.
gfxc-qazone: Invalid document
I cannot find any other information anywhere on this error. I am hoping those that have successfully installed a Solaris 8 branded zone can help me out. Thanks.

I have installed the SUNWs8brand packages before I started the configuration and I also installed the patch. I am not sure what you mean if the package installed in the correct order. I cannot find what I am missing. The original installation for the global zone was using the SUNCreq with other packages added during the installation. I realized after the O/S installation that I needed the zone packages as well as the live upgrade packages. After installing those packages I installed the SUNWs8brand packages. Let me know if there is something else that I am missing. I am thinking of re-installing the O/S with the End User software group.

Solaris 8 branded zone and privileges

Hello,
I've just installed a Solaris 8 Branded zone to migrate an old server. The migration worked like a charm, and everything seems ok excepted one thing. The zone must run a Lotus Domino server, so the process needs to bind ports 80, 443 and 389, but it can't.
I've found things about the limitpriv directive for the zone configuration, and the net_privaddr privilege to allow a process to bind ports under 1024.
So now, if I run the process in the non global zone as root, it can bind, but if it is launched as the user notes, it can't.
If I use the ppriv command to see what are the privileges of the process, I see :
1945:   /opt/lotus/notes/latest/sunspa/server
flags = <none>
        E: file_link_any,proc_exec,proc_fork,proc_info,proc_session
        I: file_link_any,proc_exec,proc_fork,proc_info,proc_session
        P: file_link_any,proc_exec,proc_fork,proc_info,proc_session
        L: contract_event,contract_observer,file_chown,file_chown_self,file_dac_execute,file_dac_read,file_dac_search,
        file_dac_write,file_link_any,file_owner,file_setid,ipc_dac_read,ipc_dac_write,ipc_owner,net_bindmlp,net_icmpaccess,
        net_mac_aware,net_privaddr,net_rawaccess,proc_audit,proc_chroot,proc_exec,proc_fork,proc_info,proc_lock_memory,
        proc_owner,proc_session,proc_setid,proc_taskid,sys_acct,sys_admin,sys_audit,sys_mount,sys_nfs,sys_resourceSo, the net_privaddr appears in the limit, but it is not enabled. How can I make it enabled for that process?
Thanks

Thanks for the link, good explanations about privileges but they seem unusable in Solaris 8 branded zone. It suggests to create a role with the privileges my process needs, using the "rolemod -K" command, but this option does not exist for the rolemod command in my Solaris 8 zone, it just supports "classic" RBAC.
Maybe the solution would be to create the good profile for the user running the process, but I'm a little bit lost with RBAC and I can't find an existing profile corresponding to what I want.
Actually, the limitpriv for my zone is "default,net_rawaccess,net_privaddr,file_dac_read" and that's all. I added net_privaddr and file_dac_read because I saw that a "ppriv -D" on the Lotus server complained about the lack of these privileges, but in fact they are already included in default privileges.

Trouble w/installing Solaris 10 branded zone on solaris 11.

Having issues creating a policy that works installing solaris 10 u10 branded nfs zone on sol11 in opscenter 12c u1. Maybe i'm just overlooking something basic or it isn't supported in opscenter. I'm able to create the policy but seem to get a very non-informative error message when deploying it.
Error Message:
"The DeploymentPlan execution job failed because the DeploymentProvider ZoneDeploymentProvider for Step Create Solaris Zones failed to generate tasks for the job: Cannot prepare zone tasks: java.lang.NullPointerException. Contact My Oracle Support if the problem persists. (10445)"
Here is the OpsCenter Profile:
Name Prefix:      hous
Starting Number:      1
Zone Description:      solaris 10 update 10
ZoneType:
Branded Zone
Branded Zone Image:
s10-update10-flar
Automatic Recovery:
Yes
Priority of Recovery:      0
CPU Shares:      1
CPU Cap:      0
Physical Memory Cap:      0
Locked Memory Cap:      0
Virtual Memory Cap:      0
Language:      en_US.ISO8859-15
Time Zone:      US/Central
Terminal Type:      xterm
NFSv4 Domain Name:      dynamic
Automatically boot zone when the global zone is booted:
Yes
Automatically boot zone after creation:
Yes
Storage for the metadata Library:      NAS, zone-prod1

Problem found. To jumpstart last two HP Blades we used the copies of AI templates. When we did it from scratch and re-installed the Solaris 11.0 we have no more errors.

Solaris 10-Branded Zone

Hi,
I am trying to establish whether the following configuration is officially supported (and documented):
"Non-Global zone running a release of Solaris 10 which is older than the release of Solaris 10 running in the Global Zone".
I'm familiar with the idea of Branded Zones to support Solaris 8, 9 & some Linux kernels, and have seen some forum posts where people have created Solaris 10-branded zones, but haven't really seen anything that puts the official seal of approval on that configuration. Also I'm familiar with LDOMs and appreciate that I could get to where I want to be that way too.
Any help welcome.
Thanks,
Paul.

This will be supported in Solaris 10 Upate 9 to a degree, using p2v. Below is a reply I had to a request I'd put in. You might also want to read this
http://blogs.sun.com/jerrysblog/entry/zones_p2v
Hi Sean,
I got information that p2v project is being backported for S10u9
This means, that you will be able to install a native zone from a flar.
I don't have detailed information at the moment, how this will work in terms of
patching in combination with Global Zone and other sibling NGZ's.
+According to Jerry Jelinek, Solaris10-branded zones will not being backported to Solaris 10,+
Got this info yesterday evening from Jerry.
I'll provide some more info about the p2v project for native zones in coming Solaris 10_U9,
once I got more details.
So, I'd suggest to check, whether the mentioned p2v project with flar on native zones might fit your requirements.
Thanks,
Alfred
Edited by: ftoomsh on Sep 2, 2010 3:02 AM

Add zfs volume to Solaris 8 branded zone

Hi,
I need to add a zfs volume to a Solaris 8 branded zone.
Basically ive created the zvol and added the following to the zone configuration.
# zonecfg -z test
zonecfg:test> add device
zonecfg:test:device> set match=/dev/zvol/dsk/sol8/vol
zonecfg:test:device> end
When I boot the zone it comes up ok but I am unable to see the device, nothing in format, /dev/dsk etc etc
Ive also tried to setmatch to the raw device as well to no avail.
Basically I have numerous zvols to add and dont really want a load of mount points from the global zone then lofs back to the local zone
Any ideas please??
Thanks...

Thanks but that's why I created zfs volumes and newfs'ed them to create UFS and presented those to the zone.
In the end I just create a script in /etc/rc2.d and mounted the filesystems in there.

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

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

Possible to upgrade Solaris 9 branded zone to 10?

We have an application running in a Solaris 9 branded zone. The application version is not compatible with Solaris 10, however, the next version of the application is compatible with Solaris 10.
So the plan is to upgrade the application in the branded zone, then upgrade the branded zone to Solaris 10.
All the reading I have found so far indicates that it is not possible to upgrade a Solaris 9 branded zone to !0.
Can it be done, and if so, pointers to a documented process would be helpful.

fog-on-the-tyne wrote:
We have an application running in a Solaris 9 branded zone. The application version is not compatible with Solaris 10, however, the next version of the application is compatible with Solaris 10.
So the plan is to upgrade the application in the branded zone, then upgrade the branded zone to Solaris 10.If the next version is compatible with Solaris 10 then backup the data,
create a new Solaris 10 zone
install the new version into the zone
migrate the data
test
destroy the now unnecessary Solaris 9 branded zone.
For something like this play in a dev environment first.
alan

Q:Creating Solaris 11.1 zone inside Solaris 11.1 LDOM fails

Hello,
I have a server where I've created a LDOM and I'd like to create zones inside that LDOMs and it isn't working at all for me. If I try to create a zone outside of my LDOM it works perfectly fine. What am I missing here?
Control domain: host-22
LDOM hostname is host-40.
Zone name is wls-zone.
OS: Solaris 11.1
Server: T5220Some information from the SP:
============================ FW Version ============================
Version
Sun System Firmware 7.4.4.f 2012/09/07 17:21
====================== System PROM revisions =======================
Version
OBP 4.33.6.a 2012/03/29 11:22I am trying this when I am creating the zone and I get an error message when I am trying to boot the zone, which I don't know the solution or how to debug. AFAIK, in Solaris 11.1, the VNIC should be created automatically when creating the zone (as it does on a bare metal machine without LDOMs)?
root@host-40:~# zoneadm -z wls-zone boot
zone 'wls-zone': failed to create vnic for net0: operation failed
zoneadm: zone 'wls-zone': call to zoneadmd failedThe zone is very simple:
root@host-40:~# zonecfg -z wls-zone info
zonename: wls-zone
zonepath: /rpool/zones/wls-zone
brand: solaris
autoboot: true
bootargs: -m verbose
file-mac-profile:
pool:
limitpriv:
scheduling-class:
ip-type: exclusive
hostid:
fs-allowed:
anet:
     linkname: net0
     lower-link: auto
     allowed-address not specified
     configure-allowed-address: true
     defrouter not specified
     allowed-dhcp-cids not specified
     link-protection: mac-nospoof
     mac-address: random
     mac-prefix not specified
     mac-slot not specified
     vlan-id not specified
     priority not specified
     rxrings not specified
     txrings not specified
     mtu not specified
     maxbw not specified
     rxfanout not specified
     vsi-typeid not specified
     vsi-vers not specified
     vsi-mgrid not specified
     etsbw-lcl not specified
     cos not specified
     pkey not specified
     linkmode not specifiedSome more information executed inside the LDOM:
root@host-40:~# dladm show-phys
LINK              MEDIA                STATE      SPEED DUPLEX    DEVICE
net0              Ethernet             up         0      unknown   vnet0
root@host-40:~# dladm show-link
LINK                CLASS     MTU    STATE    OVER
net0                phys      1500   up       --And even more information from the control domain (host-22):
root@host-22:~# ldm list-services
VCC
    NAME             LDOM             PORT-RANGE
    primary-vcc0     primary          5000-5100
VSW
    NAME             LDOM             MAC               NET-DEV   ID   DEVICE     LINKPROP   DEFAULT-VLAN-ID PVID VID                  MTU   MODE   INTER-VNET-LINK
    primary-vsw0     primary          00:14:4f:fb:93:c6 net0      0    switch@0              1               1                         1500         on
    primary-vsw1     primary          00:14:4f:f8:bb:62 net1      1    switch@1              1               1                         1500         on
VDS
    NAME             LDOM             VOLUME         OPTIONS          MPGROUP        DEVICE
    primary-vds0     primary          vol1                                           /dev/zvol/dsk/dpool/ldoms/ldmdev/disk_image
                                      vol2                                           /dev/zvol/dsk/dpool/ldoms/ldmprod/disk_image
root@host-22:~# dladm show-phys
LINK              MEDIA                STATE      SPEED DUPLEX    DEVICE
net1              Ethernet             up         1000   full      e1000g1
net2              Ethernet             unknown    0      unknown   e1000g2
net0              Ethernet             up         1000   full      e1000g0
net3              Ethernet             unknown    0      unknown   e1000g3
net4              Ethernet             up         1000   full      vsw0
net5              Ethernet             up         1000   full      vsw1Any ideas what could be wrong?
Thanks,
Andy
Edited by: A Tael on Nov 13, 2012 9:54 PM

To use a Solaris 11 zone with an exclusive IP based on a VNIC, you need to be at a recent SRU of Solaris 11.1 and run a recent version of the logical domains manager (3.0.0.2 or later) - and then configure the virtual network device to have additional MAC addresses. Please have a look at https://blogs.oracle.com/jsavit/entry/vnics_on_vnets_now_available
regards, Jeff

CREATING SOLARIS 8 BRANDED ZONE

Similar Messages

Maybe you are looking for