On 08/05/10 07:03, joerg.schill...@fokus.fraunhofer.de wrote:
Frank Batschulat (Home)frank.batschu...@sun.com wrote:
the problem with exporting the tape device to a NGZ, which although
not supported can be achived as you mention,
is that there's no way to exclusive assign that particular tape
On 07/02/10 13:47, Richard L. Hamilton wrote:
That is...is there a mechanism provided to do this?
As an afterthought, this also applies to non-global zones, although
one can stick something in the oem-banner eeprom variable that is identically
visible on all the zones, which is not the case on
On 06/30/10 04:34, Warren Zeeman wrote:
Hello,
IHAC who wants to duplicate a global zone, as a zone on another server !!!
Does anybody have any thoughts on the easiest way to achieve this ?
We call this p2v (physical to virtual). Its been in opensolaris
for quite a while now, so if you
On 05/30/10 16:45, Ian Collins wrote:
I've tracked down the cause. It was my backup copy of the zone ZFS tree
on another pool:
backup/zoneRoot 1.64G 89.3G 26K /backup/zoneRoot
backup/zoneRoot/svn 439M 89.3G 24K /backup/zoneRoot/svn
backup/zoneRoot/svn/ROOT 439M 89.3G 21K legacy
On 05/26/10 17:14, Ian Collins wrote:
I have just restarted a b133 host with several zones and no none of them
will boot. They all report:
# zoneadm -z svn boot
zone 'svn': ERROR: no active dataset.
zone 'svn':
zoneadm: zone 'svn': call to zoneadmd failed
I've seen this mentioned as an issue
On 05/28/10 15:16, Ian Collins wrote:
On 05/29/10 12:25 AM, Jerry Jelinek wrote:
On 05/26/10 17:14, Ian Collins wrote:
I have just restarted a b133 host with several zones and no none of them
will boot. They all report:
# zoneadm -z svn boot
zone 'svn': ERROR: no active dataset.
zone 'svn
On 05/19/10 12:47, Philippe Bürgisser wrote:
Hi,
I followed the guide
(http://docs.sun.com/app/docs/doc/819-2450/gcgnc?l=ena=view) from sun to move
a working zone into a new server with the same configuration.
I executed those commands :
tar xf myzone.tar -- to /export/zones/myzone
zonecfg
On 03/17/10 08:21 AM, Piotr Jasiukajtis wrote:
Hi,
After upgrade from 111b to b134 non local zone is not able to run properly.
Was this a newly installed zone or one that
existed from before the upgrade? If it was
a pre-existing zone, did you upgrade the
software inside the zone to be in
On 03/17/10 09:16 AM, Piotr Jasiukajtis wrote:
The zone was installed and running before the update. System was
upgraded by using 'pkg image-update'. No different actions ware done.
In that case, the zone is in an undefined state and
unusable. See:
On 02/26/10 07:03, Jesse Reynolds wrote:
Hello
I have an amd64 server running OpenSolaris 2009-06. In December I created one
container on this server named 'cpmail' with it's own zfs dataset and it's been
running ever since. Until earlier this evening when the server did a kernel
panic and
On 02/26/10 07:37, Jerry Jelinek wrote:
On 02/26/10 07:03, Jesse Reynolds wrote:
Hello
I have an amd64 server running OpenSolaris 2009-06. In December I
created one container on this server named 'cpmail' with it's own zfs
dataset and it's been running ever since. Until earlier this evening
On 02/26/10 07:56, Jesse Reynolds wrote:
Thanks Jerry!
Yes, dataset=mailtmp looks wrong. I guess it's possible I altered the
configuration and hadn't rebooted it.
So, assuming that the manifest is out of date or wrong, what's the best way to fix it?
Can I edit /etc/zones/cpmail.xml directly,
On 02/22/10 09:40, Frank Batschulat (Home) wrote:
May I have 2 code reviewers for the following minor changes for:
PSARC/2010/008 Remove zoneadm install sub-option -x nodataset
6880288 retire zoneadm install -x nodataset option
6890415 zoneadm install fails but returns 0
On 02/19/10 06:53, Frank Batschulat (Home) wrote:
May I request 2 code reviewers for the changes for:
6914152 zonecfg fails when less(1M) is missing
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6914152
http://cr.opensolaris.org/~batschul/zpager/
Frank,
This looks fine to me.
On 02/19/10 11:32, Frank Batschulat (Home) wrote:
Thanks Jerry, that is indeed a valid concern, I changed it to be:
snip
PAGER /usr/bin/nonsense does not exist (No such file or directory).
snip end
I included the real error string in case of permission errors where the
file does indeed exist
On 01/27/10 12:30, Marcel Hofstetter wrote:
Jerry Jelinek wrote:
usr/src/lib/brand/native/zone/sw_support.c
1115
1116 } else if (strcmp(buf, SUNW_PKG_ALL_ZONES) ==
0) {
1117 infop-zpi_all_zones = B_TRUE;
1118
My thought
On 01/25/10 04:30, Paul van der Zwan wrote:
I have upgraded my Opensolaris system to b131 and followed the zoneadm
detach/attach -u procedure to upgrade my zones
to b131 as well. Unfortunately I am running into bug 6912829 ( causes panic on
zoneadm halt ) quite often.
Downgrading the global
On 01/25/10 06:12, Paul van der Zwan wrote:
Ok that’s what I did. Detach first and then the image-update.
I saw a workaround for the panics so downgrading may be less important, but
I’ll have
to change my procedure the next update.
Do you know of an ‘official’ zones/beadm/image-update doc that
On 01/22/10 04:57, Frank Batschulat (Home) wrote:
Hiya, I observed that zone datasets are mounted even though no zones are
running.
this strikes me like a bug ? aren't they supposed to be mounted only when the
zone boots ?
No, it was a bug that they weren't mounted except when the zone was
On 01/18/10 19:25, Karl Rossing wrote:
I made the change as per
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6905313
What changes? As of this morning the bug has no workaround or suggested fix
listed?
I'm still getting the following error:
bash-4.0# zoneadm -z model attach
On 01/19/10 14:00, Edward Pilatowicz wrote:
perhaps it would make sense to add some tokens to the comments in
brand_asm.h like:
32-BIT INTERPOSITION STACK
32-BIT LCALL/INT STACK
64-BIT INTERPOSITION STACK
64-BIT LCALL/INT STACK
and then in the comments
Jordan Vaughan wrote:
I need someone to review my fix for
6909222 reboot of system upgraded from 128 to build 129 generated error
from an s10 zone due to boot-archive
My webrev is accessible via
http://cr.opensolaris.org/~flippedb/onnv-s10c
Jordan,
This looks ok to me but don't we need
Jordan Vaughan wrote:
On 01/ 4/10 07:26 AM, Jerry Jelinek wrote:
Jordan Vaughan wrote:
I need someone to review my fix for
6909222 reboot of system upgraded from 128 to build 129 generated
error from an s10 zone due to boot-archive
My webrev is accessible via
http://cr.opensolaris.org
Jordan Vaughan wrote:
On 01/ 4/10 09:54 AM, Jerry Jelinek wrote:
Jordan Vaughan wrote:
On 01/ 4/10 07:26 AM, Jerry Jelinek wrote:
Jordan Vaughan wrote:
I need someone to review my fix for
6909222 reboot of system upgraded from 128 to build 129 generated
error from an s10 zone due to boot
Jordan Vaughan wrote:
Maybe I'm not understanding the bug's evaluation but it seems to say
that the problem is caused by the presence of boot archive files.
Jerry
Jerry,
It is. However, bootadm(1M) infers the existence of boot archives from
the existence of
Edward Pilatowicz wrote:
so we're actually changing our stack pointer after entry into the
kernel, so it's no longer necessarily matching the interrupt stack that
the processor switched in automatically and saved the parameters on.
notably we don't do this for 32-bit kernels. this means that
Edward Pilatowicz wrote:
so now you have:
---8---
#define V_U_EIP (CLONGSIZE * 0)
...
GET_V(%rsp, 1, V_SSP, %rax) /* get saved stack pointer */
SET_V(%rax, 0, V_U_EIP, %r15) /* save new return addr in %eip */
---8---
but why can't this be identical to the 32-bit
Jerry Jelinek wrote:
Because its not right above, all of the other register values are
also pushed on the stack, so we need to go through the SSP to get
to the right spot. I can add a comment explaining this but the
32bit and 64bit stacks are not identical.
Ed,
Actually, what I said above
Edward Pilatowicz wrote:
- CALC_TABLE_ADDR() a little clunky. (it has seperate 32 and 64
versions, it assumes the syscall number is in eax/rax, and it has a
side effect of munging the syscall number.) how about defining just one
version of CALC_TABLE_ADDR() as:
---8---
#define
Edward Pilatowicz wrote:
On Thu, Dec 17, 2009 at 09:39:34AM -0700, Jerry Jelinek wrote:
Edward Pilatowicz wrote:
- CALC_TABLE_ADDR() a little clunky. (it has seperate 32 and 64
versions, it assumes the syscall number is in eax/rax, and it has a
side effect of munging the syscall number
Frank Batschulat (Home) wrote:
Hey Ed, Steve, Jordan, Jerry,
I got it in writing from Veritas Engineering that they do not have any heartburn
over using fsck -o p on VxFS and inside the zone and also by testing in the
lab I
confirmed it behaves as expected and similar to UFS:
snip end
# uname
Jordan Vaughan wrote:
--
usr/src/lib/brand/sn1/sn1_brand/amd64/sn1_handler.s
44: Shouldn't this function be named sn1_handler_table?
Jordan,
Good catch, I'll fix that.
Thanks,
Jerry
___
zones-discuss mailing list
Ed,
I've posted an updated webrev to address your comments.
http://cr.opensolaris.org/~gjelinek/webrev.6768950/
Let me know if you have any other comments or see anything
with the changes I made.
Thanks,
Jerry
___
zones-discuss mailing list
Ed,
Edward Pilatowicz wrote:
On Wed, Dec 16, 2009 at 10:46:57AM -0700, Jerry Jelinek wrote:
Ed,
I've posted an updated webrev to address your comments.
http://cr.opensolaris.org/~gjelinek/webrev.6768950/
usr/src/uts/intel/brand/sn1/sn1_brand_asm.s
- i'd think the is 0 = syscall = MAX
Ed,
Thanks for reviewing this. My responses to your comments are
in-line.
Edward Pilatowicz wrote:
On Tue, Dec 15, 2009 at 08:39:12AM -0700, Jerry Jelinek wrote:
I have an initial code review for the fix for bug:
6768950 panic[cpu1]/thread=ff084ce0b3e0: syscall_asm_amd64.s:480
Frank Batschulat (Home) wrote:
friends, may I request code review for the earth-shattering fix to:
6495558 zoneadm -z zone boot should not only check but repair filesystems
http://cr.opensolaris.org/~batschul/onnv-vplat/
backround:
Evaluation
when booting a zone, zoneadm ( ie.
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:
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
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:
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
Robert Hartzell wrote:
My normal procedure is to image-update, reboot, check that everything is
working then update each zone. This has always worked because the zones
would still be running. All my external services are running in zones
(dns, smtp, http, ftp) so when I reboot I have no dns
Robert Hartzell wrote:
I have upgraded 3 systems from 127 to 128a and all the zones basically
have the same error. autofs is in maintenance with 17 dependent services
not running. I haven't upgraded the zones because they are in production
and don't want to have to recreate all 7 of them
John D Groenveld wrote:
In message 4b141dac.7060...@sun.com, Jerry Jelinek writes:
The workaround for what?
On snv_127, zfs receive does not mount the zbe and zoneadm attach
fails until its mounted:
# uname -v
snv_127
# zfs receive -d rpool /var/tmp/foo.snapshot
# zonecfg -z foo create
Edward Pilatowicz wrote:
hey all,
i need a review for the following bugfix:
http://cr.opensolaris.org/~edp/onnv-zmount3/
6901952 zoneadm fails with unable to determine default brand
Ed,
This looks fine to me.
Jerry
___
zones-discuss mailing list
Edward Pilatowicz wrote:
hey all,
so with my recent zoneadm mount putback i broke the native brand on
nevada. i've got a webrev with the one line fix here:
http://cr.opensolaris.org/~edp/onnv-zmount2
6898056 native zones no longer boot: zone 'public': missing or invalid brand
Ed, looks
Edward Pilatowicz wrote:
hey all,
i've got a webrev that needs review:
http://cr.opensolaris.org/~edp/pkg-on-nightly/
it's a fix for:
11392 'zoneadm .. install' only uses preferred publisher
http://defect.opensolaris.org/bz/show_bug.cgi?id=11392
this fix let's me
Ketan wrote:
Is it possible to restrict physical memory in solaris zone with
zone.max-locked-memory just like we can do with rcapd ? I do not want to
used rcapd
No, locked memory is not the same thing as
the total physical memory used by a zone.
The only way to cap physical memory is with
Yesterday we integrated support for solaris10
branded zones into ON. In case you're not
watching the putback notifications, the heads-up
message is here:
http://onnv.sfbay.sun.com/links/flagdays/pages/2009102201.html
We've divided this project up into phases, so whats
there now is Phase I. It
Jerry Jelinek wrote:
Yesterday we integrated support for solaris10
branded zones into ON. In case you're not
watching the putback notifications, the heads-up
message is here:
http://onnv.sfbay.sun.com/links/flagdays/pages/2009102201.html
Sorry, I posted an internal link here. The external
Ed,
Thanks for reviewing this again. I took most of your
input. For the questions you had or the things I
didn't take, I have responded below.
Edward Pilatowicz wrote:
- could you propegate back your common changes to the original file?
I don't want to complicate this project with the
Jordan,
Thanks for reviewing this again. I took most of your
input. For the things I didn't take, I have responded
below.
Jordan Vaughan wrote:
usr/src/uts/common/brand/solaris10/s10_brand.c
1260-1261,1286-1287,1313,etc.: Couldn't we make arg1 a zoneid_t, arg2 an
int, arg3 a char *, and
Ed,
Edward Pilatowicz wrote:
On Tue, Oct 06, 2009 at 09:47:40AM -0600, Jerry Jelinek wrote:
Ed,
Thanks for reviewing this again. I took most of your
input. For the questions you had or the things I
didn't take, I have responded below.
Edward Pilatowicz wrote:
- could you propegate back
Peter Memishian wrote:
also, i would have though you'd commited to doing this work when you
decided to fork the sn1 brand code instead of making it common.
I was wondering about this too. Indeed, there seems be a sizeable amount
of duplicated code now. Why is this the right design?
Ed,
Edward Pilatowicz wrote:
On Tue, Oct 06, 2009 at 12:15:23PM -0600, Jerry Jelinek wrote:
Ed,
Edward Pilatowicz wrote:
On Tue, Oct 06, 2009 at 09:47:40AM -0600, Jerry Jelinek wrote:
Ed,
Thanks for reviewing this again. I took most of your
input. For the questions you had or the things
Peter Memishian wrote:
I was wondering about this too. Indeed, there seems be a sizeable amount
of duplicated code now. Why is this the right design?
Because the sn1 brand is an internal brand for testing
and is not delivered to customers. Once the solaris10
brand is
Ed,
Edward Pilatowicz wrote:
really? i'd have to disagree. i was actually expecting that when
nevada dies we'd have to update the sn1 brand to work on opensolaris. i
always thought you forked the code because that was faster than
re-factoring it to be common.
No, that wasn't my thinking,
Jordan Vaughan wrote:
I have a few nits and questions aside from Ed's.
Jordan,
Thanks for looking this over. I'll address these once
I finish going through Ed's comments.
Thanks again,
Jerry
___
zones-discuss mailing list
Edward Pilatowicz wrote:
i'm not done yet, but i've attached what i've got so far.
Ed,
Thanks for your comments. I'll start to work through
these while we're waiting for the rest of your input and
respond if there is anything we're not going to address.
Thank again,
Jerry
Will Fiveash wrote:
As an aside it would be nice if the pkg image-update command provided
an option to update all zones configured in the BE being updated.
There is no option because it will eventually do that
automatically, just like upgrading s10 today will also
upgrade all zones. We're
Edward Pilatowicz wrote:
- also, since the s10 brand is derived from the sn1 brand, could you
please ensure that all the new s10 brand that are being created are
derived from the corresponding sn1 brand files? ie, the s10 brand files
which are derived from sn1 brand files should be created via
Will Fiveash wrote:
This is in the FAQ.
http://www.opensolaris.org/os/community/zones/faq/#os
I wish the info was more detailed/explicit. How do I use zones
attach/detach to do an image-update on the zone exactly?
# zoneadm -z myzone foo detach
# zoneadm -z myzone foo attach -u
Also I
Miles Benson wrote:
Hi All,
I'm not sure what I'm seeing is by design or by misconfiguration. I created a filesystem
tank/zones to hold some zones, then created a specific zone filesystem
tank/zones/basezone. Then built a zone, setting zonepath=/tank/zones/basezone.
If I zlogin to
Miles Benson wrote:
Hi Jerry,
Ok, that makes sense. And I've checked and you're right, it's all in the
non-global zone. My mistake and I'm glad I was wrong.
However, I think the thing which set me off on the wrong track in the first
place was the zfs list output showing the available space.
Edward Pilatowicz wrote:
hey jerry,
do you have an updated ws+webrev where the s10 files were created using
hg cp? (i'm waiting for that before doing a review.)
also, when were you planning to integrate? (so i can avoid a last
minute rush.)
Ed,
I wasn't aware that this was holding you up.
Will Fiveash wrote:
On Mon, Sep 28, 2009 at 12:20:53PM -0600, Jerry Jelinek wrote:
Will Fiveash wrote:
This is in the FAQ.
http://www.opensolaris.org/os/community/zones/faq/#os
I wish the info was more detailed/explicit. How do I use zones
attach/detach to do an image-update on the zone
William A. Fiveash wrote:
My questions are:
- Should the zones have been updated when I did the pkg -R /mnt
image-update to BE opensolaris_123?
- If not, how can I fix the zones so that when I boot them while
running the opensolaris_123 BE they have 123 level packages and if
We've completed the development for the Phase I
work on the solaris10 brand. I've posted a
full webrev at:
http://cr.opensolaris.org/~gjelinek/webrev.646/
Let me know if there are any comments.
Thanks,
Jerry
___
zones-discuss mailing list
Peter Memishian wrote:
We've completed the development for the Phase I
work on the solaris10 brand. I've posted a
full webrev at:
http://cr.opensolaris.org/~gjelinek/webrev.646/
Let me know if there are any comments.
I see that ip-type=exclusive is regarded as experimental
Gael wrote:
Hello
I have been experimenting a few ways to speed up patching a bunch of
machines running whole zones (parallel patching, zoneadm attach -u).
I have encountered one issue with the attach -u way... Before initiating a
case with sun, I was wondering if it was a well known issue...
Edward Pilatowicz wrote:
hey all,
just a quick heads up.
it's been on my todo list for a very long time (and i figured that i
really should get it done before the xwiki migration), so i finally
merged all the brandz community content into the zones community. you
can see all the moved content
I've uploaded prebuilt SVr4 pkgs onto the project page
for the solaris10 brand that we're building.
http://opensolaris.org/os/project/s10brand/
I'll do this from now on as we sync to each nevada build.
The current pkgs are meant to be used with b118. The
OpenSolaris dev repository should be
Brian Leonard wrote:
I've been struggling to use the sysidcfg file to preconfigure my zones in
2009.06. I've read a couple of other posts where folks have also struggled
(http://opensolaris.org/jive/thread.jspa?messageID=307290,
http://opensolaris.org/jive/thread.jspa?messageID=319155).
Ben wrote:
Hi all,
I have an OpenSolaris server (home server for file serving and SunRay) and am
currently virtualising OpenSolaris inside VirtualBox to segregate applications.
This is a little resource intensive and I'd like to look at zones as an
alternative.
Last time I talked to an
Jerry Jelinek wrote:
...
added for the next release. To work around this, the
easiest thing to do is to detach and reattach each
zone using the 'update on attach' option (-a) which
will cause the zone to be updated to be in sync with
the global zone.
Sorry for the typo, the option is -u
I need a code review for the fix for:
ssh dumping core on maramba
There is a webrev at:
http://cr.opensolaris.org/~gjelinek/webrev.crypto/
Thanks,
Jerry
___
zones-discuss mailing list
zones-discuss@opensolaris.org
Jordan Vaughan wrote:
I have a few nits. Some of them (such at [3]) might be ridiculously
trivial, so I won't complain if you don't take them into account.
Jordan,
Thanks for reviewing this. I'll make all of the simplifications
you suggested.
Thanks again,
Jerry
Ian wrote:
Hiya,
I've just upgraded my 2008.11 system but the only way I could get it to upgrade
was by detaching all my zones or beadm refused to create a new BE.
Now that I'm in 2009.06, I used zoneadm -z web attach -F and I can see the zone
claims to be installed when using zoneadm list
Ketan wrote:
whats the difference between setting zone capped-memory from zoncfg and setting
rctl: name: zone.max-locked-memory .. if changed the zone.max-locked-memory with prctl it does not change in rcapstat .. but if change with rcapadm it reflects in rcapstat o/p
The capped-memory
I have posted the current source for the solaris10
brand on the project page at:
http://www.opensolaris.org/os/project/s10brand/
This source is synced to ONNV b116. Its a compressed
tar archive which you can unpack into an ONNV workspace
which has been synced to b116. If anyone has any
Devin Ceartas wrote:
Yikes! Seriously, no sparse zones? That wasn't in the Bible book I don't
think. This is a pretty big deal! Is this list the best place to follow
to learn such things?
Yes, this has been discussed on this alias in the past.
Also, Dan Price blogged about this here:
gz wrote:
Double Yiekes!!.
All my customers use an SOE of sparce zones (With Solaris 10 of course)
so if that is really the case it will be a problem for them to migrate
to OpenSolaris if/when that becomes neccessary.
Something like this could have serious concequences down the track and
Hung-Sheng Tsao wrote:
guess is that the memory sharing benefits of sparse zones
are relatively small in most cases.
May be I am wrong here, it seems that with sparse zone and single
binary for all zone
there must be same memory sharing!!!
I don't know what single binary you are talking
Steffen Weiberle wrote:
I have been doing all on Solaris next testing using Nevada, as all the
tools I know work, and my understanding of installation and
configuration applies to that as well as Solaris 10. Now I am playing
with 2009.06 and some 'simple' things don't work as expected. I
Christine Tran wrote:
On Mon, May 18, 2009 at 9:59 AM, Jerry Jelinek gerald.jeli...@sun.com wrote:
Thanks for the write-up. It is helpful for us to
know what peoples concerns are for the sparse vs. whole
root configurations.
Our application make and destroy zones as needed. We've built up
Steffen Weiberle wrote:
I originally could only imagine the reason for not doing the mounts when
the zone is not booted is to avoid a huge set of ZFS mounts for zones
that are not running. However, I see three ZFS file systems for a zone,
and this is without any Live Upgrade (beadm) operation.
I've been spending some time researching ideas for how we could upgrade
Solaris 10 once its installed in a solaris10 branded zone on S.next.
We won't need this capability until S10u9 is released, but I want to make
sure we do whatever we need to do now in order to enable this for the future.
I
Ellard Roush wrote:
Hi Jerry,
This document provides a lot of useful information.
The section solaris10 Brand: What's Not Emulated
you repeat some old information that is no longer correct.
One point to note is that TX will continue to
be incompatible with branded zones.
That statement
Enclosed is a first draft of a spec. for the S10
brand which we plan to submit for a PSARC
inception review. Please send us any comments
or questions.
Thanks,
Jerry
---
S10C: A Solaris 10 Branded Zone for Solaris.Next
Gerald Jelinek, Jordan Vaughan
Hernan Saltiel wrote:
Hi!
Will there be an adoption toolkit, to let the people use the S10 brand while
testing it, and starting the migration process?
I'm not sure I understand the question. Are you asking
if the source code will be available before S.next is
released? If so, then yes, we're
Hernan Saltiel wrote:
No, I'm talking about the Solaris migration toolkit, available in the past
to certify pre-Solaris 10 binaries against the new versions.
They were a couple of Perl scripts (solcat, for example). They were a binary
interface certification set of scripts.
They were a good
Menno Lageman wrote:
Thanks, that clears it up. Adding some text at the start of the
Versioning section that newer versions of the brand will provide
compatibility for older versions of the brand would help I think.
Thanks, I'll add that clarification.
Jerry
Mike Gerdts wrote:
Any thoughts on supporting live upgrade? That is, I would like live
upgrade within the branded zone to work as it does for a S10 global
zone. I don't care about it from the upgrade standpoint, but it is a
very helpful tool for patching. Having a zfs zonepath is an
Mike Gerdts wrote:
I suspect that making live upgrade work within a zone would be
significantly easier if ZFS was a prerequisite. It looks as though
the ipkg brand already has support for mounting the appropriate
dataset on boot and attach. Delegated datasets can be snapshotted and
cloned
solarg wrote:
thanks for all reply, but can you suggest a way to lower the space
occupied by a such zone? the problem with os2008.11 is that everything
is installed at initial setup, but having zones occupying more than 5Gb
is very bad!
This is incorrect. Only a small subset of packages are
solarg wrote:
hello all,
i'm wondering how to create a sparse zone in os2008.11:
Sparse zones are not currently supported on opensolaris.
This is tracked as:
2550 Support for sparse root zones
- in solaris 10, just use create instead of create -b does a
sparse zone
- in os2008.11, you have
Dan Price wrote:
Belatedly, a big +1. Jerry, if you have not already, I can take this
to the OGB for creation.
Thanks Dan. I think we have enough votes now. I will
see about getting this set up this week. If I need a
hand, I'll let you know.
Thanks again,
Jerry
Robert,
Robert Milkowski wrote:
+1 !!!
Thanks for voting for this.
Do you plan to provide S10 brand zone on top of Solaris 10 too?
This would much simplify patching and reduce downtimes when S10 zones
are being used under Sun Cluster. Actually when it comes to patching
S8/S9 branded zones
I would like to propose a project to be sponsored by
the zones community. This project would create a
solaris10 branded zone for use on OpenSolaris.
We will use the BrandZ infrastructure to deliver a
solaris10 brand. This will be provided as an adoption
and compatibility aid to enable users
Ben Rockwood wrote:
Sounds like a necessary brand and a good idea.
I admit, I'm curious what needs to be emulated? I would think that
Solaris 10 zones would work just fine under OpenSolaris as native
branded zones.
Ben,
There are a few differences in the kernel between s10
and opensolaris.
Ben Rockwood wrote:
One issue I did smack into that I don't fully understand yet is the
syseventd service failing within the zone. I'm still trying to hash out
how to solve that.
Ben,
The sysevent service should not run in the ngz.
This is delivered in a hollow pkg with svr4 pkging.
You
1 - 100 of 289 matches
Mail list logo
