Page 1 of 1

determining bridge network device using vboxmanage

Posted: 24. May 2009, 21:08
by jfayre
Hello,
I am using Virtualbox 2.2.2 on a Windows Vista host. I am blind, and as a result, the virtualbox GUI does not work for me. I am trying to use vboxmanage to establish a ubuntu virtual machine. The only part I am stuck on is how to set my bridged network device. I know the command line to do this, but I don't know what to put in for the network device. As I understand it, the GUI gives you a drop-down list of devices to choose from. How can I do this from the command-line if I don't know the device name? Is there a way to list detected network devices from the command-line. I looked at the docs, but couldn't find anything.

Re: determining bridge network device using vboxmanage

Posted: 24. May 2009, 21:39
by baf
I think that:

Code: Select all

VBoxManage --nologo list bridgedifs
Gives what you need

Code: Select all

Name:            en0: Ethernet
GUID:            00306e65-0000-4000-8000-001b632e0a89
Dhcp:            Disabled
snipped here

For me it should be

Code: Select all

en0: Ethernet

Re: determining bridge network device using vboxmanage

Posted: 27. May 2009, 02:34
by nick.kirby
Hello, I'm having that exact same issue:

When I run the command:

vboxmanage list bridgedifs the output is:

NVIDIA nForce 10/100/1000 Mbps Ethernet - there is no en0 or any reference to a linux-style eth0 name.

I have tried entering the full string above into the bridgedadapter1 parameter

(like this: --bridgeadapter1 "NVIDIA nForce 10/100/1000 Mbps Ethernet")

and it does appear within the console output, however the VM fails to start and instead returns:

Result Code:
VBOX_E_HOST_ERROR (0x80BB0008)
Component:
Console
Interface:
IConsole {9511bc54-15ee-4ddf-808e-472aba03809c}

I would be grateful if someone could kindly point me towards what I should be setting this interface value to and where I am going wrong.

Many thanks.

Re: determining bridge network device using vboxmanage

Posted: 27. May 2009, 02:36
by nick.kirby
Well I'll be a turnip. I was missing a space at the end of the adapter name.