Re: [zones-discuss] upgrading and zones
These links might help to add a little bit more to the explanation (this is my collection of all time favorite OpenSolaris zones related links here): http://blogs.sun.com/jerrysblog/entry/updating_zones_on_opensolaris_2008 http://blogs.sun.com/jerrysblog/entry/zones_on_opensolaris_2008_11 http://blogs.sun.com/dp/entry/a_field_guide_to_zones http://blogs.sun.com/observatory/entry/zones http://blogs.sun.com/observatory/en_US/entry/preconfiguring_zones http://blogs.sun.com/observatory/entry/zones_and_dns -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] upgrading and zones
Also, another important caveat / missing piece that I noticed is missing from all of the OpenSolaris Indiana Sun blogs and documentation I've looked at so far: to do resource caps on CPU and RAM memory in OpenSolaris I think you need to install the SUNWrcap package first like this: # pkg install SUNWrcap I couldn't get resource capped zones to install in a brand new Indiana install when I first started using OpenSolaris back in May 2008 and it took me a week to figure that one out. -- This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] upgrading and zones
On Sat, 06 Feb 2010 10:30:18 +0100, dick hoogendijk d...@nagual.nl wrote: Going from OpenSolaris b131 to b132.. Am I correct in this procedure: [1] pkg image-update (with zones attached) [2] after reboot to the new BE detach the zones [3] zoneadm attach -u zones precisely OR, do I have to detach -BEFORE- the pkg image -update? _after_ 'pkg image update' and _after_ the following reboot. that way, a new BE for the zone is created as well during 'pkg image update' corresponding to the new GZ BE. like this (done yesterday): osoldev.batschul./export/home/batschul.= zoneadm list -cp 0:global:running:/::ipkg:shared -:zone2:installed:/tank/zones/zone2:04d7381c-9216-eba9-a490-d7c667c5850d:ipkg:shared osoldev.batschul./export/home/batschul.= zfs list -t all ... rpool/ROOT/opensolaris-129 33.9M 193G 10.5G / rpool/ROOT/opensolaris-130 38.8M 193G 11.3G / rpool/ROOT/opensolaris-131 22.1M 193G 11.6G / rpool/ROOT/opensolaris-132 18.1G 193G 11.7G /tmp/tmp7MMWZf rpool/ROOT/opensolaris-...@install 1.72G - 3.98G - rpool/ROOT/opensolaris-...@2009-12-25-08:57:20 1.28G - 10.5G - rpool/ROOT/opensolaris-...@2010-01-23-12:56:07 1.44G - 11.3G - rpool/ROOT/opensolaris-...@2010-02-05-21:30:12972M - 11.6G - ... tank/zones/zone2 981M 183G36K /tank/zones/zone2 tank/zones/zone2/ROOT 981M 183G 31.5K legacy tank/zones/zone2/ROOT/zbe52.5K 183G 981M legacy tank/zones/zone2/ROOT/zbe-1 981M 183G 981M legacy tank/zones/zone2/ROOT/zb...@2010-02-05-21:30:17 121K - 981M - ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] upgrading and zones
On Sat, Feb 06, 2010 at 10:30:18AM +0100, dick hoogendijk wrote: Going from OpenSolaris b131 to b132.. Am I correct in this procedure: [1] pkg image-update (with zones attached) [2] after reboot to the new BE detach the zones [3] zoneadm attach -u zones OR, do I have to detach -BEFORE- the pkg image -update? do NOT detach BEFORE the image-update detach and attach -u AFTER the image-update ___ zones-discuss mailing list zones-discuss@opensolaris.org
