VirtualBox

Ticket #3754 (closed defect: fixed)

Opened 11 months ago

Last modified 2 months ago

vboxnet0 causes ndp,nwam startup to fail -> fixed in 2.2.2

Reported by: gwr Assigned to:
Priority: major Component: network
Version: VirtualBox 2.2.0 Keywords: nwam
Cc: gordon.ross@sun.com Guest type: Solaris
Host type: Solaris

Description

After installing VirtualBox 2.2.0 on Solaris Nevada (snv_111) these services fail during boot:

svc:/network/routing/ndp:default svc:/network/physical:nwam

I'm not really sure why this is happening, but I've posted fairly complete details in this thread on networking-discuss: http://www.opensolaris.org/jive/thread.jspa?threadID=99651

It looks like something doesn't like the vboxnet0 i/f.

I've marked this "major" as it prevents network startup.

Attachments

nwam.txt (2.7 kB) - added by gwr on 2009-04-16 17:39:08.
service states and data
nwam-vboxnet1.log (18.0 kB) - added by gwr on 2009-04-21 23:06:03.
debug log from nwam

Change History

2009-04-16 17:39:08 changed by gwr

  • attachment nwam.txt added.

service states and data

2009-04-17 09:31:30 changed by ramshankar

Could you post the output of sudo ifconfig -a here please?

2009-04-20 13:54:13 changed by ereitmaier

I have the same problem, hereby my ifconfig -a output:

root@opensolaris:~# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

e1000g0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2

inet 0.0.0.0 netmask ff000000 ether 0:15:b7:c:bb:ed

wpi0: flags=1000802<BROADCAST,MULTICAST,IPv4> mtu 1500 index 3

inet 0.0.0.0 netmask 0 ether 0:1b:77:3e:5a:dd

vboxnet0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 4

inet 0.0.0.0 netmask ff000000 ether 0:8:27:4e:b5:49

lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1

inet6 ::1/128

e1000g0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2

inet6 fe80::215:b7ff:fe0c:bbed/10 ether 0:15:b7:c:bb:ed

root@opensolaris:~#

2009-04-20 15:05:15 changed by ramshankar

I wasn't able to reproduce this with NWAM and vboxnet0 on OpenSolaris? 08.11. Could you try one thing please.

Change /etc/nwam/llp to have 

vboxnet0     static 1.1.1.1

and see if that helps?

2009-04-21 08:59:19 changed by ereitmaier

That helped. I need to say that I am using punchin to connect to SWAN, so that might be related.

2009-04-21 17:44:18 changed by gwr

That work-around (change /etc/nwam/llp - as described above) lets "nwam" startup without any problems. Thank-you very much!

2009-04-21 17:54:02 changed by ramshankar

Okay, the current behaviour for vboxnet is it doesn't require DHCP on the host as when you use host-only networking and start a VM with VirtualBox, the IP you assign in the global Preferences in VirtualBox would be assigned to vboxnet0 regardless of what IP it vboxnet has. So putting a 1.1.1.1 static IP there for nwam should be fine.

Thank you for the feedback.

2009-04-21 22:57:58 changed by gwr

Putting this line in /etc/nwam/llp also works OK:

vboxnet0 static 0.0.0.0

Maybe better than the above suggestion?

2009-04-21 23:06:03 changed by gwr

  • attachment nwam-vboxnet1.log added.

debug log from nwam

2009-04-21 23:27:26 changed by ramshankar

Yes that actually looks better, anything to prevent nwam/dhcpagent from kicking in. Thanks again for trying with 0.0.0.0.

2009-04-22 18:17:29 changed by gwr

Oops, posted too soon on this: (doesn't work)

> vboxnet0 static 0.0.0.0

It has to be non-zero, or nwam still tries to do dhcp on the i/f. Just need to pick something that can't interfere with any legitimate destination addresses, i.e. 127.1.1.1

2009-04-28 13:43:42 changed by sandervl73

  • status changed from new to closed.
  • resolution set to fixed.

2009-04-28 13:43:51 changed by sandervl73

  • summary changed from vboxnet0 causes ndp,nwam startup to fail to vboxnet0 causes ndp,nwam startup to fail -> fixed in 2.2.2.

2010-01-12 15:42:15 changed by Barron123

Resource: go to my pc


Contact – Privacy policy