Re: [zones-discuss] bug? zone wont create device files during boot

[Dan Price]

On Mon 01 Oct 2007 at 11:28AM, Dan Price wrote:
> So, stay tuned.  We've been sorting this out for about a week now, and are
> at work on getting a patch out as fast as possible.  For contract
> customers, filing an escalation on bug 6608977 should get you access to
> binary relief (in the form of an IDR) as soon as it is available.
> 
> As you may know, there is a huge amount of new zones functionality in S10
> 8/07, so this regression is particularly humbling.  Again, please accept
> our apologies.

Just as a followup to this thread (I sent another mail to the alias
as well), I wanted to give a status update.  It appears that this defect
can now be corrected by applying 127111-03 (SPARC) or 125914-01 (x86).

As I mentioned before, we've got some changes coming in our test suites
to make sure we don't get hit by bugs like this in the future.  Thanks
again for your patience.

-dp

-- 
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[Dan Price]

On Fri 02 Nov 2007 at 07:23AM, Jerry Jelinek wrote:
> It sounds like you are hitting the following known bug:
> 
> 6608977 Can't add device to non-global zone in S10 update 4
> 
> It looks like this is fixed in patch 125914-01 for x86 and
> patch 127111-03 for sparc, although 127111-03 isn't quite released
> yet.

I just looked this up-- it appears this patch (127111-03) is now available.

-dp

-- 
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[Jerry Jelinek]

Pascal wrote:
> bash-3.00# cat /etc/release
>Solaris 10 8/07 s10s_u4wos_12b SPARC
>Copyright 2007 Sun Microsystems, Inc.  All Rights Reserved.
> Use is subject to license terms.
> Assembled 16 August 2007
> 
> zonecfg -z aap -f aap.cmdfile
> 
> 
> # aap.cmdfile
> create -b
> set zonepath=/zoneroot/aap
> set autoboot=true
> add device
> set match=/dev/rdsk/c3t600A0B8000269A56A93746F9BB09d0s2
> end
> add device
> set match=/dev/rdsk/c3t600A0B8000269A56A93946F9CD8Bd0s2
> end
> add device
> set match=/dev/rdsk/c3t600A0B8000292EFE444D4712D98Ad0s2
> end
> add device
> set match=/dev/rdsk/c3t600A0B8000292EFE440146F9CCE4d0s2
> end
> add fs
> set dir=/aoracrp
> set special=/dev/dsk/c3t600A0B8000269A56A98547296219d0s0
> set raw=/dev/rdsk/c3t600A0B8000269A56A98547296219d0s0
> set type=ufs
> end
> add net
> set address=10.2.0.99
> set physical=ce0
> end
> exit
> 
> zone is created succesfully, except that I can not see my raw devices in the 
> zone.
> 
> Is this still a bug?
> 
> As a workaround:
> Can I make links from my non global zone devicetree to the global zone device 
> tree?
> 
> lrwxrwxrwx   1 root root  67 Oct 18 15:59 
> /dev/rdsk/c3t600A0B8000269A56A93946F9CD8Bd0s2 -> 
> ../../devices/scsi_vhci/[EMAIL PROTECTED]:c,raw
> 
> ln -s  /devices/scsi_vhci/[EMAIL PROTECTED]:c,raw 
> /zoneroot/aap/dev/rdsk/c3t600A0B8000269A56A93946F9CD8Bd0s2
> 
> or must I use mknod (if yes, can you give an example of this .. )

It sounds like you are hitting the following known bug:

6608977 Can't add device to non-global zone in S10 update 4

It looks like this is fixed in patch 125914-01 for x86 and
patch 127111-03 for sparc, although 127111-03 isn't quite released
yet.

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

Re: [zones-discuss] bug? zone wont create device files during boot

[Pascal]

bash-3.00# cat /etc/release
   Solaris 10 8/07 s10s_u4wos_12b SPARC
   Copyright 2007 Sun Microsystems, Inc.  All Rights Reserved.
Use is subject to license terms.
Assembled 16 August 2007

zonecfg -z aap -f aap.cmdfile


# aap.cmdfile
create -b
set zonepath=/zoneroot/aap
set autoboot=true
add device
set match=/dev/rdsk/c3t600A0B8000269A56A93746F9BB09d0s2
end
add device
set match=/dev/rdsk/c3t600A0B8000269A56A93946F9CD8Bd0s2
end
add device
set match=/dev/rdsk/c3t600A0B8000292EFE444D4712D98Ad0s2
end
add device
set match=/dev/rdsk/c3t600A0B8000292EFE440146F9CCE4d0s2
end
add fs
set dir=/aoracrp
set special=/dev/dsk/c3t600A0B8000269A56A98547296219d0s0
set raw=/dev/rdsk/c3t600A0B8000269A56A98547296219d0s0
set type=ufs
end
add net
set address=10.2.0.99
set physical=ce0
end
exit

zone is created succesfully, except that I can not see my raw devices in the 
zone.

Is this still a bug?

As a workaround:
Can I make links from my non global zone devicetree to the global zone device 
tree?

lrwxrwxrwx   1 root root  67 Oct 18 15:59 
/dev/rdsk/c3t600A0B8000269A56A93946F9CD8Bd0s2 -> 
../../devices/scsi_vhci/[EMAIL PROTECTED]:c,raw

ln -s  /devices/scsi_vhci/[EMAIL PROTECTED]:c,raw 
/zoneroot/aap/dev/rdsk/c3t600A0B8000269A56A93946F9CD8Bd0s2

or must I use mknod (if yes, can you give an example of this .. )

Thanks.

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

Re: [zones-discuss] bug? zone wont create device files during boot

[Axel Blazejewski]

Hi,

is this bug solved already for SPARC as well?

Sunsolve mentions  Patch 127111-02, but the Patch Description does not
include 6608977.

I tried Solaris 10 08/07 with the recent patch cluster including
127111-02, but using match for device entries still does not work.


Best regards,
Axel

***
Axel Blazejewski
Account Consultant
Sun Microsystems GmbH
Brandenburgerstr. 2
40880 Ratingen
GERMANY

Tel:(++49 2102) 4511-532
Tel2:   (++49 174)  301 4078
Fax:(++49 2102) 499516
mailto:[EMAIL PROTECTED]
http://www.sun.de
***
Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 
Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering 



Dan Price wrote:
> On Mon 01 Oct 2007 at 01:14PM, John Chase wrote:
>   
>> This has just been escalated as a P1 bug in 8/07.
>>
>> 
>
> Indeed.  And please accept our apologies that this bug slipped out.  This
> was a case where a late performance fix wound up impacting correctness.
> We're still assessing why our test suite (and our engineering) did not
> catch this problem.
>
> S10 8/07 is also supposed to have a fix for device removal from zones.  I
> authored the original fix.  In the process of that fix being ported back
> to Solaris 10, it was merged with BrandZ code, and at that point that fix
> *also* became broken.  We're working on a fix for that, as well.
>
> So, stay tuned.  We've been sorting this out for about a week now, and are
> at work on getting a patch out as fast as possible.  For contract
> customers, filing an escalation on bug 6608977 should get you access to
> binary relief (in the form of an IDR) as soon as it is available.
>
> As you may know, there is a huge amount of new zones functionality in S10
> 8/07, so this regression is particularly humbling.  Again, please accept
> our apologies.
>
> Someone earlier stated that this was also broken in SXDE-- as far as
> I know that is *not* the case.  One of the reasons this has been a
> troublesome area is that in Nevada the /dev zones implementation is
> radically different from S10, due to the existence of the "devnames"
> project in Nevada.  Hence the S10 and Nevada code is pretty in this
> area.
>
> -dp
>
>   
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[Konstantin Gremliza]

Dan, I apologize. I'm still learning.
I replayed the whole damn thing and of course it works well and all
devices appear in the zone as configured.
I was just confused because looking at /zones/zone-a/dev still doesn't
show any of my device files.
You also wanted me to check ZONEPATH/dev which is still quite empty
although the files apear in /dev within the zone. 
As my little dtrace script shows the earlier implementation of devfsadm
-z  in READY state and the devfsadm -Z during the stop of
the zone have disappeared.
It has been replaced by a strange mount -o attrdir=ZONEPATH/dev ... I
didnt find anything in the man pages, so I guess I have to look into
the source ...

Thanks again,

Konstantin

# more /etc/release  
              Solaris Express Developer Edition 9/07 snv_70b X86
   Copyright 2007 Sun Microsystems, Inc.  All Rights Reserved.
    Use is subject to license terms.
    Assembled 30 August 2007
# zoneadm -z zone-a list zone-a -v
ID NAME STATUS PATH   BRAND   
IP    
 - zone-a   installed  /zones/zone-a  native  
shared

# ls /zones/zone-a/dev/lockstat 
/zones/zone-a/dev/lockstat: No such file or directory

# zonecgf -z zone-a 'add device;set match=/dev/lockstat;end'
# zonecgf -z zone-a info 
zonename: zone-a
...
device:
    match: /dev/lockstat
...

# zoneadm -z zone-a boot
# zoneadm list -cv
  ID NAME STATUS PATH  
BRAND    IP    
   0 global   running    / 
native   shared
   1 zone-a   running    /zones/zone-a 
native   shared
   - zone-b   installed  /zones/zone-b 
native   shared 

NO SUCH FILE:

# ls /zones/zone-a/dev
cpu   dtrace    fd    pts   rmt   sad   swap 
term  zconsole

BUT HERE IT IS:

# zlogin zone-a ls /dev
arp conslog console cpu crypto cryptoadm dsk dtrace dtremote fd kstat
lockstat log logindmux msglog null poll pool ptmx pts random rdsk rmt
sad stderr stdin stdout swap ...


# zone_state.d

  TIME ZONE  ID STATE
 11280.463 1   zone-a SHUTTDING_DOWN
 12282.011 EXIT:   1 init[993]
 12284.484 1   zone-a EMPTY
 12284.697 1   zone-a DOWN
 12357.223 1   zone-a DYING
 12357.312 EXIT:   1 zsched[981]
 12357.397 1   zone-a DEAD
 12364.892 2   zone-a READY

THIS IS NEW TO ME:
 12377.392 EXEC: mount -o attrdir=/zones/zone-a/dev /dev
/zones/zone-a/root/dev

 12391.944 EXEC: mount -o ro,nosub,nodevices /lib
/zones/zone-a/root/lib
 12400.040 EXEC: mount -o ro,nosub,nodevices /platform
/zones/zone-a/root/platform
 12406.763 EXEC: mount -o ro,nosub,nodevices /sbin
/zones/zone-a/root/sbin
 12412.863 EXEC: mount -o ro,nosub,nodevices /usr
/zones/zone-a/root/usr
 12448.600 2   zone-a BOOTING
 12449.042 2   zone-a RUNNING
 12453.645 FORK:   2 init[1560]
^D^C

script done on Wed Oct 03 15:19:25 2007

Dan Price schrieb:

  On Tue 02 Oct 2007 at 07:35AM, Konstantin Gremliza wrote:
  
  

Someone earlier stated that this was also broken in SXDE-- as far as
I know that is *not* the case.  One of the reasons this has been a
troublesome area is that in Nevada the /dev zones implementation is
radically different from S10, due to the existence of the "devnames"
project in Nevada.  Hence the S10 and Nevada code is pretty in this
area.

-dp


Before I posted this to [zone-discuss] I tried again on SXDE 09/07, and the
same problem occured.
Adding a device match will not create any device files in ZONEPATH/dev.

  
  
Konstantin, we'll go back and retest SXDE 9/07, although at present we
don't have a bug for this problem open against SXDE.  As I said, the
code is basically completely different in that area between SXDE and
S10, so it would have to be a new and different bug.

My desktop is a SPARC box running build 72 (which AFAIK is SXDE 9/07)
and I don't see this there; this is an example of adding, then
removing a pseudo device in a basic test:
  
  # uname -a 
  SunOS snowdog 5.11 snv_72 sun4u sparc SUNW,A70
  # ls -l /aux/foo/root/dev/lockstat
  /aux/foo/root/dev/lockstat: No such file or directory
  # zonecfg -z foo 'add device; set match=/dev/lockstat; end'
  # zoneadm -z foo reboot
  # ls -l /aux/foo/root/dev/lockstat
  crw-r--r--   1 root sys   89,  0 Oct  3 02:55 /aux/foo/root/dev/lockstat
  # zonecfg -z foo 'remove device match=/dev/lockstat'
  # zoneadm -z foo reboot
  # ls -l /aux/foo/root/dev/lockstat
  /aux/foo/root/dev/lockstat: No such file or directory

(Please note that I'm not advising that anyone add /dev/lockstat to
their zone; I simply used it as a test case).

Perhaps you could post your SXDE test case?

-dp

- 
Daniel Price - Solaris Kernel Engineering - [EMAIL PRO

Re: [zones-discuss] bug? zone wont create device files during boot

[Enda O'Connor ( Sun Micro Systems Ireland)]

Jerry Jelinek wrote:
> Enda O'Connor ( Sun Micro Systems Ireland) wrote:
>> I tried build 74,
>> add device
>> set match=/dev/dsk/c0t0d0s7
>> end
>> add device
>> set match=/dev/rdsk/c0t0d0s7
>> end
>>
>> rebooted zone and device is there ( verified it wasn't before hand )
>> We need the user case that fails.
> 
> Enda,
> 
> I thought the original email used a wildcard match like this:
> 
> set match=/dev/*dsk/c1t15d0s*
> 
> I just tried that on build 74 and it worked fine though, so I agree
> that we need more info.
> 
> Jerry
Hi Jerry
hadn't spotted the wildcard :-)
but it does appear to work non the less.

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

Re: [zones-discuss] bug? zone wont create device files during boot

[Jerry Jelinek]

Enda O'Connor ( Sun Micro Systems Ireland) wrote:
> I tried build 74,
> add device
> set match=/dev/dsk/c0t0d0s7
> end
> add device
> set match=/dev/rdsk/c0t0d0s7
> end
> 
> rebooted zone and device is there ( verified it wasn't before hand )
> We need the user case that fails.

Enda,

I thought the original email used a wildcard match like this:

set match=/dev/*dsk/c1t15d0s*

I just tried that on build 74 and it worked fine though, so I agree
that we need more info.

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

Re: [zones-discuss] bug? zone wont create device files during boot

[Enda O'Connor ( Sun Micro Systems Ireland)]

Dan Price wrote:
> On Tue 02 Oct 2007 at 07:35AM, Konstantin Gremliza wrote:
>>
>> Someone earlier stated that this was also broken in SXDE-- as far as
>> I know that is *not* the case.  One of the reasons this has been a
>> troublesome area is that in Nevada the /dev zones implementation is
>> radically different from S10, due to the existence of the "devnames"
>> project in Nevada.  Hence the S10 and Nevada code is pretty in this
>> area.
>>
>> -dp
>>
>>
>> Before I posted this to [zone-discuss] I tried again on SXDE 09/07, and the
>> same problem occured.
>> Adding a device match will not create any device files in ZONEPATH/dev.
> 
> Konstantin, we'll go back and retest SXDE 9/07, although at present we
> don't have a bug for this problem open against SXDE.  As I said, the
> code is basically completely different in that area between SXDE and
> S10, so it would have to be a new and different bug.
> 
> My desktop is a SPARC box running build 72 (which AFAIK is SXDE 9/07)
> and I don't see this there; this is an example of adding, then
> removing a pseudo device in a basic test:
>   
>   # uname -a 
>   SunOS snowdog 5.11 snv_72 sun4u sparc SUNW,A70
>   # ls -l /aux/foo/root/dev/lockstat
>   /aux/foo/root/dev/lockstat: No such file or directory
>   # zonecfg -z foo 'add device; set match=/dev/lockstat; end'
>   # zoneadm -z foo reboot
>   # ls -l /aux/foo/root/dev/lockstat
>   crw-r--r--   1 root sys   89,  0 Oct  3 02:55 
> /aux/foo/root/dev/lockstat
>   # zonecfg -z foo 'remove device match=/dev/lockstat'
>   # zoneadm -z foo reboot
>   # ls -l /aux/foo/root/dev/lockstat
>   /aux/foo/root/dev/lockstat: No such file or directory
> 
> (Please note that I'm not advising that anyone add /dev/lockstat to
> their zone; I simply used it as a test case).
> 
> Perhaps you could post your SXDE test case?
> 
> -dp
> 
> - 
> Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - 
> blogs.sun.com/dp
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org

Hi
I tried build 74,
add device
set match=/dev/dsk/c0t0d0s7
end
add device
set match=/dev/rdsk/c0t0d0s7
end

rebooted zone and device is there ( verified it wasn't before hand )
We need the user case that fails.

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

Re: [zones-discuss] bug? zone wont create device files during boot

[Dan Price]

On Tue 02 Oct 2007 at 07:35AM, Konstantin Gremliza wrote:
> 
> 
> Someone earlier stated that this was also broken in SXDE-- as far as
> I know that is *not* the case.  One of the reasons this has been a
> troublesome area is that in Nevada the /dev zones implementation is
> radically different from S10, due to the existence of the "devnames"
> project in Nevada.  Hence the S10 and Nevada code is pretty in this
> area.
> 
> -dp
> 
> 
> Before I posted this to [zone-discuss] I tried again on SXDE 09/07, and the
> same problem occured.
> Adding a device match will not create any device files in ZONEPATH/dev.

Konstantin, we'll go back and retest SXDE 9/07, although at present we
don't have a bug for this problem open against SXDE.  As I said, the
code is basically completely different in that area between SXDE and
S10, so it would have to be a new and different bug.

My desktop is a SPARC box running build 72 (which AFAIK is SXDE 9/07)
and I don't see this there; this is an example of adding, then
removing a pseudo device in a basic test:
  
  # uname -a 
  SunOS snowdog 5.11 snv_72 sun4u sparc SUNW,A70
  # ls -l /aux/foo/root/dev/lockstat
  /aux/foo/root/dev/lockstat: No such file or directory
  # zonecfg -z foo 'add device; set match=/dev/lockstat; end'
  # zoneadm -z foo reboot
  # ls -l /aux/foo/root/dev/lockstat
  crw-r--r--   1 root sys   89,  0 Oct  3 02:55 
/aux/foo/root/dev/lockstat
  # zonecfg -z foo 'remove device match=/dev/lockstat'
  # zoneadm -z foo reboot
  # ls -l /aux/foo/root/dev/lockstat
  /aux/foo/root/dev/lockstat: No such file or directory

(Please note that I'm not advising that anyone add /dev/lockstat to
their zone; I simply used it as a test case).

Perhaps you could post your SXDE test case?

-dp

- 
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[Konstantin Gremliza]

  
Someone earlier stated that this was also broken in SXDE-- as far as
I know that is *not* the case.  One of the reasons this has been a
troublesome area is that in Nevada the /dev zones implementation is
radically different from S10, due to the existence of the "devnames"
project in Nevada.  Hence the S10 and Nevada code is pretty in this
area.

-dp

  


Before I posted this to [zone-discuss] I tried again on SXDE
09/07, and the same problem occured. 
Adding a device match will not create any device files in ZONEPATH/dev.

regards,

Konstantin


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

Re: [zones-discuss] bug? zone wont create device files during boot

[Gael]

On 10/1/07, EndaO'Connor <[EMAIL PROTECTED]> wrote:
>
> Dan Price wrote:
> > On Mon 01 Oct 2007 at 02:10PM, Gael wrote:
> >
> >> Thanks for the answer Dan, will the relief be a replacement for the
> binary
> >> itself or a full new kernel patch ? Trying to identify the impact on
> our
> >> environment (ie reboot vs no reboot)
> >>
> >
> > I'm not sure about reboot vs. no reboot, but I believe the patch will be
> > to libzonecfg.  The bug is simply a logic error in the library, in the
> > function which decides whether or not a device should be made available
> > to the zone, or not.
> >
> > -dp
> >
> >
> If it's just libzonecfg, we should be able to get away with a very
> simple patch, no reboot etc.
> Should not be a KU.
>
> Enda
>
>
 I was able to get the database zone fixed here by recreating all  raw
devices into /zones/db/dev/*dsk/ with mknod and the /devices entries in the
GZ.


Regards

Gael
-- 
Gael Martinez
Unix Delivery Services - Solaris Managed Services (aka Zones)
UnitedHealth Group IT, Enterprise Shared Services
6150 Trenton Lane, MN013-N300, Plymouth, 55442, MN
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[EndaO'Connor]

Dan Price wrote:
> On Mon 01 Oct 2007 at 02:10PM, Gael wrote:
>   
>> Thanks for the answer Dan, will the relief be a replacement for the binary
>> itself or a full new kernel patch ? Trying to identify the impact on our
>> environment (ie reboot vs no reboot)
>> 
>
> I'm not sure about reboot vs. no reboot, but I believe the patch will be
> to libzonecfg.  The bug is simply a logic error in the library, in the
> function which decides whether or not a device should be made available
> to the zone, or not.
>
> -dp
>
>   
If it's just libzonecfg, we should be able to get away with a very 
simple patch, no reboot etc.
Should not be a KU.

Enda

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

Re: [zones-discuss] bug? zone wont create device files during boot

[Dan Price]

On Mon 01 Oct 2007 at 02:10PM, Gael wrote:
> Thanks for the answer Dan, will the relief be a replacement for the binary
> itself or a full new kernel patch ? Trying to identify the impact on our
> environment (ie reboot vs no reboot)

I'm not sure about reboot vs. no reboot, but I believe the patch will be
to libzonecfg.  The bug is simply a logic error in the library, in the
function which decides whether or not a device should be made available
to the zone, or not.

-dp

-- 
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[Gael]

Thanks for the answer Dan, will the relief be a replacement for the binary
itself or a full new kernel patch ? Trying to identify the impact on our
environment (ie reboot vs no reboot)

Regards.


On 10/1/07, Dan Price <[EMAIL PROTECTED]> wrote:
>
> On Mon 01 Oct 2007 at 01:14PM, John Chase wrote:
> >
> > This has just been escalated as a P1 bug in 8/07.
> >
>
> Indeed.  And please accept our apologies that this bug slipped out.  This
> was a case where a late performance fix wound up impacting correctness.
> We're still assessing why our test suite (and our engineering) did not
> catch this problem.
>
> S10 8/07 is also supposed to have a fix for device removal from zones.  I
> authored the original fix.  In the process of that fix being ported back
> to Solaris 10, it was merged with BrandZ code, and at that point that fix
> *also* became broken.  We're working on a fix for that, as well.
>
> So, stay tuned.  We've been sorting this out for about a week now, and are
> at work on getting a patch out as fast as possible.  For contract
> customers, filing an escalation on bug 6608977 should get you access to
> binary relief (in the form of an IDR) as soon as it is available.
>
> As you may know, there is a huge amount of new zones functionality in S10
> 8/07, so this regression is particularly humbling.  Again, please accept
> our apologies.
>
> Someone earlier stated that this was also broken in SXDE-- as far as
> I know that is *not* the case.  One of the reasons this has been a
> troublesome area is that in Nevada the /dev zones implementation is
> radically different from S10, due to the existence of the "devnames"
> project in Nevada.  Hence the S10 and Nevada code is pretty in this
> area.
>
>-dp
>
> --
> Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] -
> blogs.sun.com/dp
>



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

Re: [zones-discuss] bug? zone wont create device files during boot

[Dan Price]

On Mon 01 Oct 2007 at 01:14PM, John Chase wrote:
> 
> This has just been escalated as a P1 bug in 8/07.
> 

Indeed.  And please accept our apologies that this bug slipped out.  This
was a case where a late performance fix wound up impacting correctness.
We're still assessing why our test suite (and our engineering) did not
catch this problem.

S10 8/07 is also supposed to have a fix for device removal from zones.  I
authored the original fix.  In the process of that fix being ported back
to Solaris 10, it was merged with BrandZ code, and at that point that fix
*also* became broken.  We're working on a fix for that, as well.

So, stay tuned.  We've been sorting this out for about a week now, and are
at work on getting a patch out as fast as possible.  For contract
customers, filing an escalation on bug 6608977 should get you access to
binary relief (in the form of an IDR) as soon as it is available.

As you may know, there is a huge amount of new zones functionality in S10
8/07, so this regression is particularly humbling.  Again, please accept
our apologies.

Someone earlier stated that this was also broken in SXDE-- as far as
I know that is *not* the case.  One of the reasons this has been a
troublesome area is that in Nevada the /dev zones implementation is
radically different from S10, due to the existence of the "devnames"
project in Nevada.  Hence the S10 and Nevada code is pretty in this
area.

-dp

-- 
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
___
zones-discuss mailing list
zones-discuss@opensolaris.org

Re: [zones-discuss] bug? zone wont create device files during boot

[John Chase]

This has just been escalated as a P1 bug in 8/07.


-JOhn



Gael wrote:

Hello,
 
Glad to see I'm not crazy, noticed the same issue following a few 
upgrades this week end and working on a case with Sun support. I was 
able to cpio the devices from the global zones for all except two (all 
are raw devices)


Regards
 
On 10/1/07, *Konstantin Gremliza* <[EMAIL PROTECTED] 
> wrote:


Hi,

a collegue of mine mentioned a problem in both Solaris 10 >= 11/06
and Solaris Express 09/07.

Setting a device match in * zonecfg *like this works fine:
*
zonecfg> add device
zonecfg:device> set match=/dev/*dsk/c6t0d0s*
zonecfg:device> end *

But
*
zoneadm -z zone boot *

wont create the necessary device files in * ZONEPATH/dev *.

In my understanding this part of * zoneadmd *which would call *
devfsadm -z  * which it still does. But in the end there is
no device file created?

I tried to look at the source of devfsadm.c but couldnt find the
-z switch, so I'm stuck here.

This is not really a problem to me as I could easily create the
device files by simply copying them. I'd rather like to submit
this as a bug.

Thanks,

Konstantin Gremliza





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




--
Gael Martinez


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


--

**


   John Chase 
   /___/\  (Technical Support OS Group)

  _\_ \\ \ Sun Support Services
 _\__\ \\ /
/   / \/_/ /   Sun Microsystems Inc.

/___/ / __\//\  1 Network Drive BLDG 4
\___\//\ __/ /  Burlington, MA 01803-0903
 /__/ / /\ /   M/S UBUR04-268
 \___/ \\ \EMail:  [EMAIL PROTECTED]
  \   \ \\ 1-800-USA4-SUN 
   \___\/


**

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

Re: [zones-discuss] bug? zone wont create device files during boot

[Gael]

Hello,

Glad to see I'm not crazy, noticed the same issue following a few upgrades
this week end and working on a case with Sun support. I was able to cpio the
devices from the global zones for all except two (all are raw devices)

Regards

On 10/1/07, Konstantin Gremliza <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> a collegue of mine mentioned a problem in both Solaris 10 >= 11/06 and
> Solaris Express 09/07.
>
> Setting a device match in *zonecfg *like this works fine:
> *
> zonecfg> add device
> zonecfg:device> set match=/dev/*dsk/c6t0d0s*
> zonecfg:device> end*
>
> But
> *
> zoneadm -z zone boot*
>
> wont create the necessary device files in *ZONEPATH/dev*.
>
> In my understanding this part of *zoneadmd *which would call *devfsadm -z
> * which it still does. But in the end there is no device file
> created?
>
> I tried to look at the source of devfsadm.c but couldnt find the -z
> switch, so I'm stuck here.
>
> This is not really a problem to me as I could easily create the device
> files by simply copying them. I'd rather like to submit this as a bug.
>
> Thanks,
>
> Konstantin Gremliza
>
>
>
>
>
> ___
> zones-discuss mailing list
> zones-discuss@opensolaris.org
>



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

[zones-discuss] bug? zone wont create device files during boot

[Konstantin Gremliza]

Hi,

a collegue of mine mentioned a problem in both Solaris 10 >= 11/06
and Solaris Express 09/07. 

Setting a device match in zonecfg like
this works fine:

zonecfg> add device
zonecfg:device> set match=/dev/*dsk/c6t0d0s*
zonecfg:device> end

But 

zoneadm -z zone boot

wont create the necessary device files in ZONEPATH/dev.

In my understanding this part of zoneadmd which
would call devfsadm -z 
which it still does. But in the end there is no device file created?

I tried to look at the source of devfsadm.c but couldnt find the -z
switch, so I'm stuck here.

This is not really a problem to me as I could easily create the device
files by simply copying them. I'd rather like to submit this as a bug.

Thanks,

Konstantin Gremliza







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