Talk:VirtualBox

From Gentoo Linux Wiki

Jump to: navigation, search

[edit] rx/tx issue

the config guide does not work for me. i am using dhcp for my physical dev. the physical dev works without a problem. the vbox0 does not. it seems to be that i can tx from vbox0 -> outside world but not rx from outside world --> vbox0

any guesses what i could have done wrong ? and can someone put some better captchas on this side, it is hard to read. maybe increase resolution ---

[edit] kernel 2.6.24

patch for 2.6.24 kernels does not work

  • It looks like virtualbox-bin requires alsa-lib to be installed. Else I get an "error while loading shared libraries: libasound.so.2" in ~/.VirtualBox/VBoxSVC.log
  • furthermore libsdl needs to be compiled with the "X" USE-flag, else you get "Failed to start VM execution (VERR_INTERNAL_ERROR)" when trying to start a machine
  • someone please add needed kernel configurations for bridging and tun/tap support

---

This configuration does not work for me. My only modification to the /etc/init.d/net was the authors suggestion for using DHCP with the br0 interface. Here is what happens: When I boot, the bridge is created first and an error is generated indicating that the vbox0 interface does not exist. I can get it to work by manually destroying the bridge (/etc/init.d/net.br0 stop), initializing the vbox0 interface, and restarting the bridge. The bridge is then successfully created. It is like the depend line is being completely ignored by the /etc/init.d/net.lo script and is not being considered when startup dependencies are calculated. Regardless, there are other issues. VirtualBox complains that the /dev/net/tun device cannot be opened in a read/write mode and offers some suggestions to correct the problem. Using 'chmod 0666 /dev/net/tun' as recommended by the error dialog allows the virtual machine to be started (in my case, Server 2k3 Enterprise Ed.) This is not a permanent fix since I use udev, but custom udev rules is another topic entirely. Once the virtual machine starts and I login, I am greeted by the yellow triangle over the network interface icon in the systray, indicating that I have 'Limited connectivity to network'. AKA Windows has failed garner an response from my DHCP server. I manually add a static IP to the interface only to find that there is no indication that the bridge is working properly. I can ping myself but not the host machine or my gateway. Any help would be greatly appreciated.

It doesn't work with the first udev rule proposed in bridge networking.

I have to execute this command first to make it work : tunctl -t vbox0 -u <username>

[edit] multilib

virtualbox-1.5.0-r1 does not work on amd64/nomultilib profile (in other words, it relies on multilib) it is not masked in that profile though

configure says:

Checking for 32-bit support: 

 Cannot compile 32-bit applications (missing headers and/or libraries)!
 Check the file configure.log for detailed error information.

--88.234.86.66 04:39, 26 September 2007 (UTC)


after installing dev86 rpm, you won't have this err message.

Retrieved from "http://www.gentoo-wiki.com/Talk:VirtualBox"
Personal tools