Upgrading Solaris with Zones

I have just found the following statement in the Solaris 10 Install Guide, section "Upgrade Limitations":
"If you have configured Solaris Zones on your system, you are not able to upgrade until you have unconfigured and uninstalled your non-global zones"
I have a serious problem with this limitation. It seems to be impossible to upgrade a Solaris 10 system with zones configured. I would have to shut down and uninstall my zones and applications to upgrade the OS.
There's not even a way to move the affected zones to another system to keep the application running if the host with the global zone needs maintenance due to OS upgrade, HW maintenance or if simply has too many zones configured on it and all resources are exhausted.
With these limitations I don't see much reasonable use for zones. In particular, once a zone and an application is set up on a physical box with a particular OS release I am stuck with it for all times.
How are you going to solve these problems. And when? What are zones good for in the current implementation? I am still waiting for convincing arguments to use zones ...

I guess I'll state for the record, lest anyone should be confused by my last post, that LiveUpgrade doesn't allow upgrade anymore. I guess I got away with it before LU was upgraded to restrict such activity.
ERROR: Unable to upgrade boot environment <Solaris10-B58>.
INFORMATION: Boot environment <Solaris10-B58> has one or more non-global
zones installed. This version of Live Upgrade cannot upgrade a boot
Guess I'd better figure out how to backup my zones so I clean remove them. A simple tar will probly do the trick for now.
benr.

Similar Messages

  • Upgrading Solaris with Zones installed

    So Solaris 5/09 was released. Previously I have upgraded Solaris the simplest way by simply downloading the DVD, throwing it in and running the upgrade. However that was before we started using the zones feature and I'm not sure if there is anything special I have to take into account now.
    They're simply native zones. Is there anything special I have to do or will the simple disk upgrade work still?

    Upgrading 10/08 to 5/09, including zones, should be very clean, with or without Live Upgrade. The advantage is Live upgrade is minimal downtime and a safe backout if the upgrade does cause something to break. If you use ZFS root filesystems, it is even easier and 'wastes' very little disk space.
    Mark

  • How to upgrade solaris with disk under ODS

    upgrade wsolaris

    Robert,
    I am just worried about what might happen, if our internal SSD should fail. The system files, your user settings, mail boxes, everything in your user library and system library, the installed applications, plug-ins, Aperture presets, etc. From what you are describing, you are taking good care of your documents, but the system itself and the work you are putting into configuring it is not backed up. Should your system drive crash you would have a hard time to recover from that.
    The easiest way to backup your system drive and the internal HD2 would be to use one of your 3TB drives with Time Machine. You need not necessarily Time Capsule to be able to do that. Time Machine can work with any external disk, that is formatted MacOS X extended.
    Just plug in the backup drive you want to use, then open "System Preferences" and click the Time Machine icon.
    Click the "Select Backup Disk" button.
    Enable "Show Time Machine in Menu Bar".
    Click the "Options" Button. If your backup drive is not large enough to include your Aperture library, deselect the other external drives in the "Options" panel. You may even deselect the second internal drive, if you are backing that up differently and only want to create a backup of the system. Then a small 500GB drive should suffice to get you started with system backups. But backing up both internal drives at once using TimeMachine would be much preferable.
    Then set the switch to "on".
    The first backup may take a very long time, but it will run in the background, so let it run.
    Léonie

  • Live upgrade - solaris 8/07 (U4) , with non-global zones and SC 3.2

    Dears,
    I need to use live upgrade for SC3.2 with non-global zones, solaris 10 U4 to Solaris 10 10/09 (latest release) and update the cluster to 3.2 U3.
    i dont know where to start, i've read lots of documents, but couldn't find one complete document to cover the whole process.
    i know that upgrade for solaris 10 with non-global zones is supported since my soalris 10 release, but i am not sure if its supported with SC.
    Appreciate your help

    Hi,
    I am not sure whether this document:
    http://wikis.sun.com/display/BluePrints/Maintaining+Solaris+with+Live+Upgrade+and+Update+On+Attach
    has been on the list of docs you found already.
    If you click on the download link, it won't work. But if you use the Tools icon on the upper right hand corner and click on attachements, you'll find the document. Its content is solely based on configurations with ZFS as root and zone root, but should have valuable information for other deployments as well.
    Regards
    Hartmut

  • 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

  • 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?

  • 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 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

  • 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

  • Cloning Solaris 10 with zones

    What is the best method to use when cloning a Solaris machine with zones, to ensure all software is included and can be easily installed
    on new hardware?
    Thank you!

    If you use UFS, then ufsdump/ufsrestore
    If you use ZFS, then zfs send/zfs receive
    But, if you are using hardware or software RAID, you can also try to move one disk to an another machine.
    You can see with these simple examples, that you have several methods and it depends how you configured your machine, Solaris and the zones. And finally, it depends too what is the source machine and what is the target machine, and how they are configured.

  • 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

  • [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.

  • 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?

  • Upgrading Solaris 10 from 32-bit to 64-bit in a VirtualBox VM

    Hello,
    I am running 32-bit Sol 10 u5 x86 as a guest in a Sun VirtualBox (Vbox) virtual machine on a 32-bit WinXP host with 64-bit VT-capable Xeon processors, and am considering upgrading Solaris 10 to 64-bit using the latest version of Vbox (2.0.0). After installing WinXP Professional x64 and the 64-bit version of Vbox, will I have to completely re-install Sol 10 to get it to run in 64-bit, or is there some way to get it to 64-bit without a re-install? The Vbox forums suggested that I post this question on a Solaris forum, as they don't know the answer.
    They apparently also do not know if Windows XP x64 is a compatible host OS on which to run 64-bit guests. They list only Vista, Linux, and OpenSolaris as supported 64-bit host OSs. Has anyone used WinXP x64 as a host for Vbox 64-bit guests? Due to policy, Vista is not available to me on my system/network.
    Thank you...

    The x86 installer will place both 32-bit and 64-bit code on the disk.
    The loader fired by GRUB will attempt to detect the proper hardware and launch the correct kernel.
    Other portions of the upgrade could conceivably cause a problem, but having the CPUs go from 32-bit only to 64-bit capable shouldn't be an issue. You don't have to make any changes.
    Darren

  • 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

Maybe you are looking for