My Oracle Support Banner

Migrating an Existing Non-Global Zone on Solaris 10 System to Solaris 11 (Doc ID 1619436.1)

Last updated on OCTOBER 14, 2020

Applies to:

Solaris Operating System - Version 10 and later
Solaris x64/x86 Operating System - Version 10 and later
Information in this document applies to any platform.
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)

Symptoms

Migrating an existing Solaris 10 (native) non-global zone running on a Solaris 10 global zone to a Solaris10 branded zone on a Solaris 11 global zone fails when using one of following methods:

1) Attaching a Solaris 10 non-global zone to a Solaris 11 server. 
For example:

    - Move the LUN with the zone path from Solaris 10 global zone to the Solaris 11 global zone.
    - Create the configuration for the Solaris10 branded zone on the Solaris 11 global zone via zonecfg.
    - Attach the Solaris 10 non-global zone to the Solaris 11 server.  This fails with the error seen below:

 

# zoneadm -z <ZONE> attach
Progress being logged to /var/log/zones/zoneadm.20140210T185319Z.<ZONE>.attach
Log File: /var/log/zones/zoneadm.20140210T185319Z.<ZONE>.attach
ERROR: Error: No active boot environment found.
Result: Attach Failed.
Log saved in non-global zone as /<ZONE>/s10zone/root/var/log/zones/zoneadm.20140210T185319Z.<ZONE>.attach

# cat /var/log/zones/zoneadm.20140210T185319Z.<ZONE>.attach
[Monday, February 10, 2014 06:53:19 PM GMT] ==== Starting: /usr/lib/brand/solaris10/attach <ZONE>/<ZONE>/s10zone ====
[Monday, February 10, 2014 06:53:19 PM GMT] Progress being logged to /var/log/zones/zoneadm.20140210T185319Z.<ZONE>.attach
[Monday, February 10, 2014 06:53:19 PM GMT] Pinning datasets under <ZONE>/s10zone
[Monday, February 10, 2014 06:53:19 PM GMT] Pinning <ZONE>/s10zone
[Monday, February 10, 2014 06:53:19 PM GMT] Log File: /var/log/zones/zoneadm.20140210T185319Z.<ZONE>.attach
cannot open '<ZONE>/s10zone/rpool/ROOT': filesystem does not exist
[Monday, February 10, 2014 06:53:19 PM GMT] ERROR: Error: No active boot environment found.
[Monday, February 10, 2014 06:53:19 PM GMT] Unpinning datasets under <ZONE>/s10zone
[Monday, February 10, 2014 06:53:19 PM GMT] Unpinning <ZONE>/s10zone
[Monday, February 10, 2014 06:53:19 PM GMT] Result: Attach Failed.
[Monday, February 10, 2014 06:53:19 PM GMT] Exiting with exit code 254
[Monday, February 10, 2014 06:53:19 PM GMT] ==== Completed: /usr/lib/brand/solaris10/attach <ZONE>/<ZONE>/s10zone  ====

 

2) Installing a 'sparse' native zone from Solaris 10 to a branded Solaris 10 zone on Solaris 11 using "zoneadm -z zonename install" fails with error:

"The image was created with an incompatible libc.so.1 hwcap lofs mount."

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.