virtualbox.org

Using CentOS 5.2 64bit 4GB RAM. Install VirtualBox successfully but when try to add a VirtualHost Interface with the following command
VBoxAddIF vbox0 <user> br0 got the following error
-bash: VBoxAddIF: command not found

Try to find VBoxAddIF but all in Vain.

Any Help will be highly Appreciated.

--
Kunal Jain

Which Version of VBOX?

stefan.becker wrote:Which Version of VBOX?

VirtualBox-2.1.0_41146_rhel5-1.x86_64.rpm

Look into the Manual. Way for setup of an host adapter has changed with 2.10. Its only a mouseclick in the gui. Scripts are not needed anymore.

stefan.becker wrote:Look into the Manual. Way for setup of an host adapter has changed with 2.10. Its only a mouseclick in the gui. Scripts are not needed anymore.

Not able to figure out this. Can you tell me the steps to do it as a 32 bit version of VirtualBox 1.5 is running perfectly fine and i add the Vitrual Ethernet by VBoxAddIF command onlye

The command is missing since 2.10 because its not needed anymore.

For 2.10 look into the manual of 2.10.

For Versions before 2.10 look into the Manual of Versions before 2.10.

Here you find the Manuals in the version directorys:

http://download.virtualbox.org/virtualbox/

stefan.becker wrote:The command is missing since 2.10 because its not needed anymore.

For 2.10 look into the manual of 2.10.

For Versions before 2.10 look into the Manual of Versions before 2.10.

Here you find the Manuals in the version directorys:

http://download.virtualbox.org/virtualbox/

Try the new way of setting up networking but when in Network settings i choose Host Interface and then i select eth0 in the Host Interface box and press ok and when i run the GuestOS on my server then VirtualBox Hangs and OS too. then i have to reboot the server forcefully.

There are a few stability issues with the new HIF system. If you can't use it, please install 2.0.6.

Greetings Folks,

I have a bit of a rant about this at:

http://web-tech.ga-usa.com/2009/01/virt ... ing-tools/

Note that this 'solution' is to simply put the scripts back in place (from a previous version - which you will need to fetch and then extract the needed tools...)

In section 6.5 of the VirtualBox 2.1.2 PDF manual the changes to Host Interface Networking are described as being simplified (i.e. you don’t have to do all this VNIC tinkering.) The section goes on to say that you can still use TAP devices (but creating them is now not directly supported with a VirtualBox tool…)

My *fix* (not a real fix) - just a seemingly quick way to get my vbox-en NICS back was to copy VBoxTAP from VirtualBox 2.0.6 AND to create links for VBoxAddIF and VBoxDeleteIF. Note that VboxTAP (a shell script) uses VBoxTunctl (which is a compiled, binary file.) I am guessing that there are differences between the current version of VBoxTunctl and the previous version but, based on my limited testing things still seem to work.

1. -rwxr-xr-x 1 root root 8400 2008-09-12 14:00 VBoxTAP (shell script)
2. -rwxr-xr-x 1 root root 2384 2009-01-22 14:07 VBox
3. -rwxr-xr-x 1 root root 7600 2009-01-22 14:10 VBoxTunctl
4. lrwxrwxrwx 1 root root 13 2009-01-29 08:31 VBoxVRDP -> /usr/bin/VBox
5. lrwxrwxrwx 1 root root 13 2009-01-29 08:31 VBoxSDL -> /usr/bin/VBox
6. lrwxrwxrwx 1 root root 13 2009-01-29 08:31 VBoxManage -> /usr/bin/VBox
7. lrwxrwxrwx 1 root root 13 2009-01-29 08:31 VBoxHeadless -> /usr/bin/VBox
8. lrwxrwxrwx 1 root root 16 2009-01-29 14:19 VBoxDeleteIF -> /usr/bin/VBoxTAP
9. lrwxrwxrwx 1 root root 16 2009-01-29 14:19 VBoxAddIF -> /usr/bin/VBoxTAP

Note that the location of these tools may vary but they all need to be in your PATH (so you could install the three missing files into any location of choice as long as it is in your PATH...) On my system these tools are found in /usr/bin.


Dale

Why all the fuss with this? Why not just use the supported* method of normal TAP interfaces created with uml-utilities?

*meaning, not by VB itself, but the distro itself. VB will work just as well with this.

Not so much fuss as annoyance - once a tool and it's feature set start being used (and I'm guessing that there are hundreds of VirtualBox users affected by this change) then some consideration should be given when such changes are made.

Note that if your first use of TAP was via VirtualBox (and you had no previous exposure to it) then 'the magic' of the feature pretty much stays out of your understanding - all you care about is that it works...

Regarding the 'new, supported method' itself - I'm not so sure it was the best 'solution' - esp. since the NICs are flipped through promiscuous mode while being used...

For anyone interested - some possibly helpful info is listed below.

http://www.alyz.com/uml.xhtml - Site about UML (user-mode Linux)

"Additionally, in order for the UML guests to connect to the Internet, it is necessary to either set up routing on the UML host or add a network bridge to connect the UML guests directly to the outside network. This is described briefly under the TUN/TAP with a preconfigured tap device section in the documentation. Keep in mind that the setup described there is equally applicable to the other two configurations as well. Another write-up on setting up a network bridge can be found in this article."
http://edeca.net/articles/bridging/

A lot of users already complained about the pain it was to set up HIF, especially the lack of wifi support on that (it just wasn't supported by bridge-utils).
And now that they 'fixed' it, users are complaining that they wanted the old way with TAP interfaces. When are you users pleased?

You can still use the uml-utilities Tunctl command to create TAP interfaces and bridge them. What is the problem?

Sasquatch wrote:<snip>
You can still use the uml-utilities Tunctl command to create TAP interfaces and bridge them. What is the problem?

The problem is simple - lack of communication - most fuss over such changes can/could be alleviated by posting *helpful* information about how to work through such issues (when possible...)

Do you have any additional, helpful links on using TAP interfaces? (We can't assume that everyone knows what you might about the subject and we can't assume that they know how to find an answer beyond looking in these hopefully, helpful VirtualBox forums...)

I don't use it, so I don't have any experience with it. All I can advise, is to read the man page of the command (man tunctl). Users who use this other than the default HIF system of VB usually have a better understanding of networking and the commands that are involved.