Re: [zones-discuss] Impossible to install a zone on a new indiana b128a install

2009-12-09 Thread Vincent Boisard
I downloaded the modified files and will manually apply the patch to avoid 
other problems until I do the real b129 upgrade

Thanks again,

Vincent
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] solaris 10 branded zone

2009-12-09 Thread Jerry Jelinek

xx wrote:

i installed virtualbox and installed solaris 10 from an iso download. i used 
the flar command to create s10.flar as directed in:
http://hub.opensolaris.org/bin/view/Community+Group+zones/s10brand_dev_guide

i then tried to install s10.flar in the solaris 10 branded zone:
init...@dogpatch:~# zoneadm -z csuite install -a /virtualbox/s10.flar -u
WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed 
in the global zone.
A ZFS file system has been created for this zone.
  Log File: /var/tmp/csuite.install_log.2raajz
Installing: This may take several minutes...
Missing etc at /zones/csuite/root
Missing etc/svc at /zones/csuite/root
Missing var at /zones/csuite/root
Missing var/svc at /zones/csuite/root
Missing lib/svc at /zones/csuite/root
Is this a sparse zone image?  The image must be whole-root.
Missing sbin/zonename at /zones/csuite/root
Is this a sparse zone image?  The image must be whole-root.
Missing usr/bin/chmod at /zones/csuite/root
Is this a sparse zone image?  The image must be whole-root.
  Sanity Check: FAILED (see log for details).
ERROR: Result: *** Installation FAILED ***
init...@dogpatch:~# zonecfg -z csuite info
zonename: csuite
zonepath: /zones/csuite
brand: solaris10
autoboot: false
bootargs: 
pool: 
limitpriv: 
scheduling-class: 
ip-type: shared
hostid: 
net:

address: 192.168.30.4
physical: vnic0_3
defrouter not specified
init...@dogpatch:~#

did i skip a step?


How did you create the flar of the s10 system?  Did the s10 system
have a zfs root?  If so, then you must create the flar using an
explicit -L option to specify either a cpio or pax archive.  Otherwise
the flar will actually contain a zfs send stream of the root pool
and that is not suitable for installing a zone (since the zone root must
be a dataset, not a pool).  I recently integrated the following bug fix
to help address this:

6903478 need better error msg for flar made on system with zfs root

Jerry

___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] why not just bury zoneadm [-x nodataset] option ?

2009-12-09 Thread Jerry Jelinek

Frank Batschulat (Home) wrote:

friends,

I went back and forth with th bug pertaining the [-x nodataset] option

6880288 zoneadm install -x nodataset option should be brand-specifc
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6880288

and eventually I decided to ask for quorum to just bury this option
entirely.

When Jerry filed it, his intent was to make it brand specific
as that option means no zfs dataset should be created for a zoneroot.
the zone will be just put onder a zoneroot directory instead.

this really only makes sense for native brands that do not rely on all
the fancy beadm/ips features used in OSOL.

point is you can not really make this option brand specific.
the code to create datasets is generic (and for obvious reasons should be)
and thus lives in zoneadm.c:install_func() and is executed prior calling the 
brand specific install_func().


so one can only special case this in zoneadm.c:install_func() itself
and remove the mentioning of this option from zoneadm.c and put
it into the native brands sw_support.c:install_usage() func.

however I've been asking around people that use zones pretty much since
Solaris 10 came out the door, they do not even know about that option.

also I think it would be a reasonable thing to just always have datasets for
zoneroots created going forward in terms of managability and usage.
it's not applicable to UFS zoneroots and neither to all the other brands
except the native brand, which we're not going to use much anymore
going forward with the ipkg brand.

so may I ask for a positive vote to bury that thing rather then
attempting handstands ? that'd be marvellous...


Frank,

This sounds fine to me.

Thanks,
Jerry
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] solaris 10 branded zone

2009-12-09 Thread Enda O'Connor



Jerry Jelinek wrote:

xx wrote:
i installed virtualbox and installed solaris 10 from an iso download. 
i used the flar command to create s10.flar as directed in:
http://hub.opensolaris.org/bin/view/Community+Group+zones/s10brand_dev_guide 



i then tried to install s10.flar in the solaris 10 branded zone:
init...@dogpatch:~# zoneadm -z csuite install -a /virtualbox/s10.flar -u
WARNING: skipping network interface 'vnic0_3' which may not be 
present/plumbed in the global zone.

A ZFS file system has been created for this zone.
  Log File: /var/tmp/csuite.install_log.2raajz
Installing: This may take several minutes...
Missing etc at /zones/csuite/root
Missing etc/svc at /zones/csuite/root
Missing var at /zones/csuite/root
Missing var/svc at /zones/csuite/root
Missing lib/svc at /zones/csuite/root
Is this a sparse zone image?  The image must be whole-root.
Missing sbin/zonename at /zones/csuite/root
Is this a sparse zone image?  The image must be whole-root.
Missing usr/bin/chmod at /zones/csuite/root
Is this a sparse zone image?  The image must be whole-root.
  Sanity Check: FAILED (see log for details).
ERROR: Result: *** Installation FAILED ***
init...@dogpatch:~# zonecfg -z csuite info
zonename: csuite
zonepath: /zones/csuite
brand: solaris10
autoboot: false
bootargs: pool: limitpriv: scheduling-class: ip-type: shared
hostid: net:
address: 192.168.30.4
physical: vnic0_3
defrouter not specified
init...@dogpatch:~#

did i skip a step?


How did you create the flar of the s10 system?  Did the s10 system
have a zfs root?  If so, then you must create the flar using an
explicit -L option to specify either a cpio or pax archive.  Otherwise
the flar will actually contain a zfs send stream of the root pool
and that is not suitable for installing a zone (since the zone root must
be a dataset, not a pool).  I recently integrated the following bug fix
to help address this:

6903478 need better error msg for flar made on system with zfs root

Jerry


Also if the system has a separate /var and is zfs root based, you will 
need to manually build the cpio archive, ie flar create -L cpio will not 
work.
6889459 flarcreate using cpio of a system running SUNWCreq zfs root with 
seperate /var fails.


I used the following
cd /
find . \( \( -fstype nfs -o -fstype autofs \) -prune \) -o -print| egrep 
-v ^./proc|^./system|^./devices|^./dev|^./export/home|^./home|^./tmp 
|cpio -oc  /export/home/oryx.cpio


But that is only if you have zfs root and separate /var.

Enda


___
zones-discuss mailing list
zones-discuss@opensolaris.org


--
Enda O'Connor x19781  Software Product Engineering
Patch System Test : Ireland : x19781/353-1-8199718
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] solaris 10 branded zone

2009-12-09 Thread xx
according to my notes, i create the flar with:

#flar create -n myflash /export/home/s10-.flar

i picked up the command on the video:
http://mediacast.sun.com/users/flippedbits/media/s10c-demo-jerry.swf

when i installed solaris 10 in virtualbox, i opted for a zfs file system:

Sun Microsystems Inc.   SunOS 5.10  Generic January 2005
# zfs list
NAMEUSED  AVAIL  REFER  MOUNTPOINT
rpool  9.27G  6.35G33K  /rpool
rpool/ROOT 3.51G  6.35G21K  legacy
rpool/ROOT/s10x_u8wos_08a  3.51G  6.35G  3.51G  /
rpool/dump 1.00G  6.35G  1.00G  -
rpool/export   3.77G  6.35G23K  /export
rpool/export/home  3.77G  6.35G  3.77G  /export/home
rpool/swap1G  7.35G16K  -

can i go back and re-install solaris 10 with a UFS and make this flar problem 
go away? i am only installing solaris 10 on virtualbox to create the branded 
zone so a re-install will work for me.
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] solaris 10 branded zone

2009-12-09 Thread Enda O'Connor



xx wrote:

according to my notes, i create the flar with:

#flar create -n myflash /export/home/s10-.flar

i picked up the command on the video:
http://mediacast.sun.com/users/flippedbits/media/s10c-demo-jerry.swf

when i installed solaris 10 in virtualbox, i opted for a zfs file system:

Sun Microsystems Inc.   SunOS 5.10  Generic January 2005
# zfs list
NAMEUSED  AVAIL  REFER  MOUNTPOINT
rpool  9.27G  6.35G33K  /rpool
rpool/ROOT 3.51G  6.35G21K  legacy
rpool/ROOT/s10x_u8wos_08a  3.51G  6.35G  3.51G  /
rpool/dump 1.00G  6.35G  1.00G  -
rpool/export   3.77G  6.35G23K  /export
rpool/export/home  3.77G  6.35G  3.77G  /export/home
rpool/swap1G  7.35G16K  -

can i go back and re-install solaris 10 with a UFS and make this flar problem 
go away? i am only installing solaris 10 on virtualbox to create the branded 
zone so a re-install will work for me.


Hi
so flar create -L cpio -n myflash 
should work for you, but you need the -L cpio bit, ( or pax ), if you 
had a separate /var dataset you'd need to manually run cpio command.


Enda

Enda O'Connor x19781  Software Product Engineering
Patch System Test : Ireland : x19781/353-1-8199718
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] solaris 10 branded zone

2009-12-09 Thread xx
ok - i re-created the s10.flar:

# flar create -L cpio -n myflash /export/home/s10.cpio
Archive format requested is cpio
This archiver format is NOT VALID for flash installation of ZFS root pool.
This format is useful for installing the system image into a zone.
Reissue command without -L option to produce an archive for root pool install.
Full Flash
Checking integrity...
Integrity OK.
Running precreation scripts...
Precreation scripts done.
Determining the size of the archive...
The archive will be approximately 3.21GB.
6746651 blocks
Creating the archive...
6746653 blocks
Archive creation complete.
Running postcreation scripts...
Postcreation scripts done.

Running pre-exit scripts...
Pre-exit scripts done.

i copied it to the global zone:

init...@dogpatch:/virtualbox# scp r...@192.168.11.4:/export/home/s10.cpio .
Password: 
s10.cpio 100% |*|  
3294 MB07:30
init...@dogpatch:/virtualbox# ls -l
total 20440460
-rw-r--r--   1 65535other151 Oct  2 02:28 autoresponse
-rw-r--r--   1 65535other   2314 Oct  2 02:28 ReadMe.txt
-rw-r--r--   1 root root 3454295946 Dec  9 09:10 s10.cpio
-rw-r--r--   1 root root 4039699747 Dec  8 16:09 s10.flar
-rw-r--r--   1 initial  staff2563440640 Oct 17 13:35 
sol-10-u8-ga-x86-dvd.iso
-rw-r--r--   1 initial  staff4208274 Oct 17 11:19 UserManual.pdf
-rw-r--r--   1 initial  staff197888000 Oct 17 11:19 
VirtualBox-3.0.8-53138-SunOS.tar
-rw-r--r--   1 65535other197806592 Oct  2 02:28 
VirtualBox-3.0.8-SunOS-r53138.pkg
-rw-r--r--   1 65535other  67072 Oct  2 02:28 
VirtualBoxKern-3.0.8-SunOS-r53138.pkg
init...@dogpatch:/virtualbox# rm s10.flar

then i tried to install it:

init...@dogpatch:/virtualbox# zoneadm -z csuite install -a ./s10.cpio
WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed 
in the global zone.
A ZFS file system has been created for this zone.
ERROR: you must specify -u (sys-unconfig) or -p (preserve identity).
solaris10 brand usage:
install -u | -p [-v | -s] -a archive | -d directory.
The -a archive option specifies an archive name which can be a flar,
tar, pax or cpio archive.
The -d directory option specifies an existing directory.
The -u option unconfigures the zone, -p preserves the configuration.
usage:  install [-x nodataset] [brand-specific args]
Install the configuration on to the system.  The -x nodataset option
can be used to prevent the creation of a new ZFS file system for the
zone (assuming the zonepath is within a ZFS file system).
All other arguments are passed to the brand installation function;
see brands(5) for more information.
init...@dogpatch:/virtualbox# zoneadm -z csuite install -a ./s10.cpio -u
zoneadm: zone 'csuite': zone is incomplete; uninstall required.
init...@dogpatch:/virtualbox# zoneadm -z csuite uninstall
Are you sure you want to uninstall zone csuite (y/[n])? y
init...@dogpatch:/virtualbox# zoneadm -z csuite install -a ./s10.cpio -u
WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed 
in the global zone.
A ZFS file system has been created for this zone.
  Log File: /var/tmp/csuite.install_log.79aGOA
Error: Unknown archive format. Must be a flash archive, a cpio archive (can 
also be gzipped or bzipped), a pax XUSTAR archive, or a level 0 ufsdump archive.
ERROR: Installation aborted.

do i need to label it as a cpio archive somehow?
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] solaris 10 branded zone

2009-12-09 Thread Jerry Jelinek

xx wrote:

init...@dogpatch:/virtualbox# zoneadm -z csuite install -a ./s10.cpio -u
WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed 
in the global zone.
A ZFS file system has been created for this zone.
  Log File: /var/tmp/csuite.install_log.79aGOA
Error: Unknown archive format. Must be a flash archive, a cpio archive (can 
also be gzipped or bzipped), a pax XUSTAR archive, or a level 0 ufsdump archive.
ERROR: Installation aborted.

do i need to label it as a cpio archive somehow?


I think you've hit a bug in the code.  Can you re-run the
command with an absolute path to the flar.

Jerry


___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] solaris 10 branded zone

2009-12-09 Thread xx
ok - that appears to work:

init...@dogpatch:/virtualbox# zoneadm -z csuite install -a /virtualbox/s10.cpio 
-u
WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed 
in the global zone.
A ZFS file system has been created for this zone.
  Log File: /var/tmp/csuite.install_log.XEaWcB
Installing: This may take several minutes...
Postprocessing: This may take a while...
   Postprocess: Updating the image to run within a zone

Result: Installation completed successfully.
  Log File: /zones/csuite/root/var/log/csuite.install13777.log

and it booted:

bash-3.00# uname -a
SunOS csuite 5.10 Generic_Virtual i86pc i386 i86pc

and it gave me a 64 bit machine - even though i'm missing some fancy hardware:

# isainfo -v
64-bit amd64 applications
sse3 sse2 sse fxsr amd_3dnowx amd_3dnow amd_mmx mmx cmov amd_sysc cx8 
tsc fpu 0x2 
32-bit i386 applications
sse3 sse2 sse fxsr amd_3dnowx amd_3dnow amd_mmx mmx cmov amd_sysc cx8 
tsc fpu 0x2 

thanks so much everybody for helping me!
david
-- 
This message posted from opensolaris.org
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Impossible to install a zone on a new indiana b128a install

2009-12-09 Thread Frank Batschulat (Home)
On Tue, 08 Dec 2009 20:01:19 +0100, Ric Aleshire ric.alesh...@sun.com wrote:

 Vincent Boisard wrote:
 Hi,

 I just installed a new opensolaris dev b128a machine from an iso downloaded 
 from genunix.

 I tried to install a zone but it failed:
 r...@pasiphae:~# zoneadm -z template install
 A ZFS file system has been created for this zone.
Publisher: Using opensolaris.org (http://pkg.opensolaris.org/dev/ ).
Image: Preparing at /zones/template/root.
Cache: Using /var/pkg/download.
 Sanity Check: Looking for 'entire' incorporation.
   Installing: Core System (output follows)
 No updates necessary for this image.
 ERROR: failed to install package

 (it downloaded ~120MB of files into /var/pkg/download)
 The zone is in incomplete state and the zone root fs is mounted

 As it is the first time I'm using opensolaris (I used SXCE before), I have 
 no idea what's going on here.

 This is bug that is fixed in b129:
 http://defect.opensolaris.org/bz/show_bug.cgi?id=12995

Vincent, if you can not wait for build 129, there's a workaround:

edit the script: /usr/lib/brand/ipkg/pkgcreatezone

and comment out line 468 in the file and which looks like:
 
$PKG install --no-refresh --no-index SUNWcs || fail_fatal $f_pkg

if you comment it out, the zone will be installed fine.

cheers
frankB



___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Solaris10-Branded Zones Webrev: CR 6882732

2009-12-09 Thread Edward Pilatowicz
On Wed, Dec 09, 2009 at 02:54:05PM -0800, Jordan Vaughan wrote:
 I need someone to review my fix for

 6882732 unpacking archive with extended file attributes reports errors

 The webrev is accessible via

 http://cr.opensolaris.org/~flippedb/onnv-s10c


lgtm.
ed
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Solaris10-Branded Zones Webrev: CR 6882732

2009-12-09 Thread Jerry Jelinek

Jordan Vaughan wrote:

I need someone to review my fix for

6882732 unpacking archive with extended file attributes reports errors

The webrev is accessible via

http://cr.opensolaris.org/~flippedb/onnv-s10c


Jordan,

Nice job, this looks good to me.

Thanks,
Jerry
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Solaris10-Branded Zones Webrev: CR 6882732

2009-12-09 Thread Jordan Vaughan

On 12/ 9/09 03:04 PM, Edward Pilatowicz wrote:

On Wed, Dec 09, 2009 at 02:54:05PM -0800, Jordan Vaughan wrote:

I need someone to review my fix for

6882732 unpacking archive with extended file attributes reports errors

The webrev is accessible via

http://cr.opensolaris.org/~flippedb/onnv-s10c



lgtm.
ed


Thanks Ed.
___
zones-discuss mailing list
zones-discuss@opensolaris.org


Re: [zones-discuss] Solaris10-Branded Zones Webrev: CR 6882732

2009-12-09 Thread Jordan Vaughan

On 12/ 9/09 03:45 PM, Jerry Jelinek wrote:

Jordan Vaughan wrote:

I need someone to review my fix for

6882732 unpacking archive with extended file attributes reports errors

The webrev is accessible via

http://cr.opensolaris.org/~flippedb/onnv-s10c


Jordan,

Nice job, this looks good to me.

Thanks,
Jerry


Thanks Jerry!
___
zones-discuss mailing list
zones-discuss@opensolaris.org