From http://www.opensolaris.org/os/project/crossbow/CrossbowRelease08-2006/GettingStarted/ one can use the typical procedure with zonecfg:test0> add net zonecfg:test0:net> set physical=vnic2 to add an interface to a zone. After booting the zone, will we have then vnic2:1 or will the interface itself be used and placed into the new stack instance ? This would make the setup a bit easier and more clear. Detlef
Hi Detlef, If the Zone is configured to have its exclusive network stack, it will have full access to the interface itself, vnic2. Nicolas. Detlef Drewanz wrote:> From > http://www.opensolaris.org/os/project/crossbow/CrossbowRelease08-2006/GettingStarted/ > > one can use the typical procedure with > > zonecfg:test0> add net > zonecfg:test0:net> set physical=vnic2 > > to add an interface to a zone. After booting the zone, will we have then > vnic2:1 or will the interface itself be used and placed into the new > stack instance ? This would make the setup a bit easier and more clear. > > Detlef > _______________________________________________ > crossbow-discuss mailing list > crossbow-discuss at opensolaris.org > http://opensolaris.org/mailman/listinfo/crossbow-discuss-- Nicolas Droux, Solaris Kernel Networking Sun Microsystems, Inc. http://blogs.sun.com/droux
Thanks Nicolas, I tried to test by myself but failed with b46. On my ferrari 3400 I get dladm: VNIC creation failed: No such file or directory (unknown diagnostic) from dladm create vnic -d bge0 -m 0:1:2:3:4:5 -b 10000 2 Or is this an other issue ? Detlef On 08/25/06 18:13, Nicolas Droux wrote:> Hi Detlef, > > If the Zone is configured to have its exclusive network stack, it will > have full access to the interface itself, vnic2. > > Nicolas. > > Detlef Drewanz wrote: > >> From >> http://www.opensolaris.org/os/project/crossbow/CrossbowRelease08-2006/GettingStarted/ >> >> one can use the typical procedure with >> >> zonecfg:test0> add net >> zonecfg:test0:net> set physical=vnic2 >> >> to add an interface to a zone. After booting the zone, will we have >> then vnic2:1 or will the interface itself be used and placed into the >> new stack instance ? This would make the setup a bit easier and more >> clear. >> >> Detlef >> _______________________________________________ >> crossbow-discuss mailing list >> crossbow-discuss at opensolaris.org >> http://opensolaris.org/mailman/listinfo/crossbow-discuss > >-- Detlef Drewanz OS Ambassador Sun Microsystems GmbH Phone: (+49 30) 747096 856 Komturstrasse 18a Fax: (+49 30) 747096 878 D-12099 Berlin mailto:detlef.drewanz at sun.com http://blogs.sun.com/solarium
To answer my own question - just found it: I missed to clear bfu conflicts. b46 uses in /etc/name_to_major nge 188 but crossbow wanted vnic 188 So I hacked this file to change this and disabled nge for me. Also minor_perm needed to add vnic:* 0666 root sys Now it works to create the device. Detlef On 08/28/06 16:52, Detlef Drewanz wrote:> Thanks Nicolas, > I tried to test by myself but failed with b46. > > On my ferrari 3400 I get > dladm: VNIC creation failed: No such file or directory (unknown diagnostic) > > from dladm create vnic -d bge0 -m 0:1:2:3:4:5 -b 10000 2 > > Or is this an other issue ? > > Detlef > > On 08/25/06 18:13, Nicolas Droux wrote: > >> Hi Detlef, >> >> If the Zone is configured to have its exclusive network stack, it will >> have full access to the interface itself, vnic2. >> >> Nicolas. >> >> Detlef Drewanz wrote: >> >>> From >>> http://www.opensolaris.org/os/project/crossbow/CrossbowRelease08-2006/GettingStarted/ >>> >>> one can use the typical procedure with >>> >>> zonecfg:test0> add net >>> zonecfg:test0:net> set physical=vnic2 >>> >>> to add an interface to a zone. After booting the zone, will we have >>> then vnic2:1 or will the interface itself be used and placed into the >>> new stack instance ? This would make the setup a bit easier and more >>> clear. >>> >>> Detlef >>> _______________________________________________ >>> crossbow-discuss mailing list >>> crossbow-discuss at opensolaris.org >>> http://opensolaris.org/mailman/listinfo/crossbow-discuss >> >> >> >-- Detlef Drewanz OS Ambassador Sun Microsystems GmbH Phone: (+49 30) 747096 856 Komturstrasse 18a Fax: (+49 30) 747096 878 D-12099 Berlin mailto:detlef.drewanz at sun.com http://blogs.sun.com/solarium