Folks,
I also asked this question in opensolaris forums, but we did not get anywhere.
I am using Mac OSX Lion and 4.1.6 r74713 VBox.
I installed Solaris 11 on VirtualBox and I created a zone named "zdev1" by following the directions outlined here:
http://www.oracle.com/technetwork/artic ... 24494.html
Here is some information:
root@solaris11:~# uname -a
SunOS solaris11 5.11 11.0 i86pc i386 i86pc
root@solaris11:~# cat /etc/release
Oracle Solaris 11 11/11 X86
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Assembled 18 October 2011
root@solaris11:~# zoneadm list -civ
ID NAME STATUS PATH BRAND IP
0 global running / solaris shared
1 zdev1 running /zones/zdev1 solaris excl
But I can't get the zone networking to work for the life of me:
root@solaris11:~# zlogin zdev1
[Connected to zone 'zdev1' pts/2]
Oracle Corporation SunOS 5.11 11.0 November 2011
root@zdev1:~# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
net0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 192.168.1.13 netmask ffffff00 broadcast 192.168.1.255
ether 2:8:20:5:51:dc
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
inet6 ::1/128
net0: flags=20002004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
inet6 fe80::8fe05:51dc/10
ether 2:8:20:5:51:dc
Trying to ping the defaultrouter ( 192.168.1.254 )
root@zdev1:~# ping 192.168.1.254
no answer from 192.168.1.254
ofcourse trying out is not gonna work:
root@zdev1:~# ping 173.194.64.103
no answer from 173.194.64.103
I can ping to my self:
root@zdev1:~# ping localhost
localhost is alive
The zone info:
root@solaris11:~# zonecfg -z zdev1 info
zonename: zdev1
zonepath: /zones/zdev1
brand: solaris
autoboot: true
bootargs: -m verbose
file-mac-profile:
pool:
limitpriv:
scheduling-class:
ip-type: exclusive
hostid:
fs-allowed:
anet:
linkname: net0
lower-link: auto
allowed-address not specified
configure-allowed-address: true
defrouter not specified
allowed-dhcp-cids not specified
link-protection: mac-nospoof
mac-address: random
auto-mac-address: 2:8:20:5:51:dc
mac-prefix not specified
mac-slot not specified
vlan-id not specified
priority not specified
rxrings not specified
txrings not specified
mtu not specified
maxbw not specified
rxfanout not specified
I have the following information from Solaris 11 GZ:
I get the following information:
root@solaris11:~# dladm show-link
LINK CLASS MTU STATE OVER
net0 phys 1500 up --
zdev1/net0 vnic 1500 up net0
root@solaris11:~# ipadm show-addr
ADDROBJ TYPE STATE ADDR
lo0/v4 static ok 127.0.0.1/8
net0/v4 static ok 192.168.1.20/24
lo0/v6 static ok ::1/128
net0/v6 addrconf ok fe80::a00fe22:cf2f/10
Is this a known bug? Is there anything I can do to make networking work other than trying to use "shared" stack?
Solaris 11 Zone Networking Problems with ip-exclusive stack
-
- Posts: 7
- Joined: 12. Jan 2011, 15:50
- Primary OS: FreeBSD
- VBox Version: OSE self-compiled
- Guest OSses: Linux and Solaris
Re: Solaris 11 Zone Networking Problems with ip-exclusive st
Same problem as I posted.
As far as I have figured you have to use the shared-ip stack instead, as in Solaris 10. That works. Unless you want to always want to run tcpdump
As far as I have figured you have to use the shared-ip stack instead, as in Solaris 10. That works. Unless you want to always want to run tcpdump
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
Re: Solaris 11 Zone Networking Problems with ip-exclusive st
I'm not sure how this is related to VirtualBox in any way...
Oracle Corp.
-
- Posts: 7
- Joined: 12. Jan 2011, 15:50
- Primary OS: FreeBSD
- VBox Version: OSE self-compiled
- Guest OSses: Linux and Solaris
Re: Solaris 11 Zone Networking Problems with ip-exclusive st
That the new network model in Solaris don't work with Virtualbox is pretty related to Virtualbox.
-
- Oracle Corporation
- Posts: 793
- Joined: 7. Jan 2008, 16:17
Re: Solaris 11 Zone Networking Problems with ip-exclusive st
VirtualBox wired (Ethernet) bridging works on layer 2 (MAC addresses), it has no idea about IPs or any of the above layers. This looks like misconfiguration in the guest, hence the "unrelated to VirtualBox" status.
Oracle Corp.
-
- Posts: 7
- Joined: 12. Jan 2011, 15:50
- Primary OS: FreeBSD
- VBox Version: OSE self-compiled
- Guest OSses: Linux and Solaris
Re: Solaris 11 Zone Networking Problems with ip-exclusive st
It's related to Virtualbox since it works on a non-virtual machine.