virtualbox.org

We are having trouble using VirtualBox 3.1.6 on a Mac OS X Server 10.6.2, using a Bridged Adapter.
We have configured a bonding interface 'bond0' using 2 ethernet cards we have, eth0, eth1
When starting the VM we almost instantly get the following message:

---
Failed to start virtual machine VM_01.
Malformed host interface networking name 'bond0'
(VERR_INTERNAL_ERROR)
Unknown error creating VM (VERR_INTERNAL_ERROR).
---

Note that we get this error even with a valid VM (Ubuntu, imported) and a non-initialized VM (Windows for example) so it doesn't have to do with the VM itself.

We have tried to force the bridged adapter using the following command:
VBoxManage modifyvm TestHost1 --nic1 bridged --bridgeadapter1 'bond0: interface name' --nictype1 Am79C973

After executing the command we can start the VM without error but we cannot use DHCP and if we use a fixed IP we can only access the host machine.

Also, our networking setup is working fine. We have been able to make it work using Parallels Server. The bond0 is detected, the VM starts and we can access our network and Internet using DHCP.

Any idea on what can cause this problem? How to resolve it?
Thanks.




ifconfig:

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:24:36:f3:d6:d6
media: autoselect (1000baseT <full-duplex>) status: active
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:24:36:f3:d6:d6
media: autoselect (1000baseT <full-duplex>) status: active
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control>
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:25:4b:ff:fe:fb:83:34
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
bond0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::224fef3:d6d6%bond0 prefixlen 64 scopeid 0x7
inet 10.0.10.50 netmask 0xffffff00 broadcast 10.0.10.255
ether 00:24:36:f3:d6:d6
media: autoselect (1000baseT <full-duplex>) status: active
supported media: autoselect
bond interfaces: en1 en0
vboxnet0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 0a:00:27:00:00:00

Hi there.

I found a way of making VBoxManage accept a bond interface: use "bond0:" as the name for the --bridgeadapter1 parameter.

I should add I still had access issues after this, ie pinging the outside world or visaversa didn't work very well. YMMV.