Opened 16 years ago
Closed 16 years ago
#4149 closed defect (invalid)
Problem starting vm with bridged networking
Reported by: | Steffen Genkinger | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 2.2.4 |
Keywords: | bridged networking | Cc: | |
Guest type: | Windows | Host type: | Linux |
Description
Hi there,
I have a clean installation of a Ubuntu 9.04 64-bit server without GUI. I installed Virtualbox 2.2.4 via apt-get by adding the Ubuntu/Debian repository to sources.list.
Then I followed the step by step instructions to set up a VM (Windows XP SP3) on a headless server. I would like to use bridged networking to make the VM completely available in my local network. I realised this via
VBoxManage modfifyvm "gvpc60" --nic1 bridged
At this point I a not sure, if I have to define the bridgeadapter with
VBoxManage modifyvm "gvpc60" --bridgeadapter1 foo
I did not do this, since I have no idea how to replace "foo".
Instead I directly tried to start the installation process of my VM by
VBoxHeadless --startvm gvpc60 VirtualBox Headless Interface 2.2.4 (C) 2008-2009 Sun Microsystems, Inc. All rights reserved. Listening on port 3389 Error: failed to start machine. Error message: Failed to open/create the internal network 'HostInterfaceNetworking-' (VERR_INTNET_FLT_IF_NOT_FOUND). Unknown error creating VM (VERR_INTNET_FLT_IF_NOT_FOUND)
I got the error message displayed above. Do you have a solution to this problem. BTW, when using nat as network configuration, the VM comes up without any problems.
Please find attached the result of ifconfig of my server, the xml and the logfile of Virtualbox.
Regards, Steffen
Attachments (3)
Change History (5)
by , 16 years ago
by , 16 years ago
Attachment: | gvpc60.xml added |
---|
by , 16 years ago
Attachment: | ifconfig.txt added |
---|
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Right. You have to attach the bridged network adapter to an existing NIC at the host.
Problem solved - no bug.
Just use the option --nic1 bridged and --bridgeadapter eth0 for VBoxManage modifyvm within one command line. The it works!