Unfortunately, exclusive-stack solaris10-branded zones aren't supported yet. The zone will fail to configure and boot if you make it exclusive-stack.

Jordan


On 01/11/10 06:22 PM, HeCSa wrote:
Hi!

On Mon, 2010-01-11 at 16:21 -0800, xx wrote:
i am having trouble getting rid of the warning:
WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed 
in the global zone.

when i boot the zone - i get:
init...@dogpatch:~$ pfexec zoneadm -z csuite boot
WARNING: skipping network interface 'vnic0_3' which may not be present/plumbed 
in the global zone.

Have you configured the ip-type as exclusive for that zone?
Best regards,

HeCSa.



i know that it is present in the global zone:
init...@dogpatch:~$ dladm show-vnic
LINK         OVER         SPEED  MACADDRESS        MACADDRTYPE         VID
vnic0_0      etherstub0   0      2:8:20:9c:9d:1f   random              0
vnic0_1      etherstub0   0      2:8:20:bc:91:d5   random              0
vnic0_2      etherstub0   0      2:8:20:a1:e3:5e   random              0
vnic0_3      etherstub0   0      2:8:20:a4:32:81   random              0

it is not plumbed- so i tried to plumb it - i added /etc/hostname.vnic0_3, put 
an ip address in it, and rebooted - but then the zone boot complained that the 
vnic was in use by the global zone.

my zone id configured:
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

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

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

Reply via email to