PDA

View Full Version : VirtualBox ping from guest to host



wulfgarpro
9th December 2009, 06:31 AM
Hi,

I have VirtualBox v3.1.0 r55467 running on f12 2.6.31.6-162.fc12.i686. The guest is Windows XP SP3. I need to enable bridged mode for the virtual network interface on the guest.

Everytime I enable bridge mode the following error occurs.


Failed to start the virtual machine Windows XP.
Failed to open/create the internal network 'HostInterfaceNetworking-wlan0' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
One of the kernel modules was not successfully loaded. Make sure that no kernel modules from an older version of VirtualBox exist. Then try to recompile and reload the kernel modules by executing '/etc/init.d/vboxdrv setup' as root (VERR_SUPDRV_COMPONENT_NOT_FOUND).

When I run '/etc/init.d/vboxdrv setup' i get the following compilation error:


Stopping VirtualBox kernel module [ OK ]
Removing old VirtualBox netadp kernel module [ OK ]
Removing old VirtualBox netflt kernel module [ OK ]
Removing old VirtualBox kernel module [ OK ]
Recompiling VirtualBox kernel module [ OK ]
Starting VirtualBox kernel module [FAILED]
(modprobe vboxnetflt failed. Please use 'dmesg' to find out why)

dmesg gives me nothing. I have scoured the web .. and even asked on #vbox and #fedora .. cant get any help.

Any ideas ?

wulfgarpro.

Hlingler
9th December 2009, 06:42 AM
How did you install VBox: binary or RPM ? On F12 Host: are packages gcc, kernel-[PAE-]devel (as appropriate), and dkms installed ?? Probably wouldn't hurt to have also: gcc-c++, make, cpp, ccache, autoconf, automake, kernel-headers . Please post results:
rpm -qa | grep -i kernel | sort

V

P.S. Here's a helpful link that I bookmarked: http://www.virtuatopia.com/index.php/Understanding_and_Installing_VirtualBox_Guest_Addi tions

wulfgarpro
9th December 2009, 09:04 AM
RPM .. ill ensure these additionals are installed. I do have guest additions installed.

wulfgarpro.

---------- Post added at 07:04 PM CST ---------- Previous post was at 07:02 PM CST ----------

Sorry, results of command:


abrt-addon-kerneloops-1.0.0-1.fc12.i686
abrt-plugin-kerneloopsreporter-1.0.0-1.fc12.i686
kernel-2.6.31.5-127.fc12.i686
kernel-2.6.31.6-145.fc12.i686
kernel-2.6.31.6-162.fc12.i686
kernel-devel-2.6.31.5-127.fc12.i686
kernel-devel-2.6.31.6-145.fc12.i686
kernel-devel-2.6.31.6-162.fc12.i686
kernel-firmware-2.6.31.6-162.fc12.noarch
kernel-headers-2.6.31.6-162.fc12.i686

wulfgarpro
10th December 2009, 01:57 AM
Hm. Still no progress on this. I have tried re-installing the latest RPM for VBox .. still no change.

Any ideas ?

wulfgarpro.

Hlingler
10th December 2009, 03:15 AM
Please attach (do NOT post) file /var/log/vbox-install.log (from F12 Host machine) to a post.

V

wulfgarpro
10th December 2009, 04:44 AM
Attached.

wulfgarpro.

Hlingler
10th December 2009, 09:50 PM
Something appears to be amiss with either kernel-devel-2.6.31.6-162.fc12.i686 or kernel-headers-2.6.31.6-162.fc12.i686 :
make KBUILD_VERBOSE=1 -C /lib/modules/2.6.31.6-162.fc12.i686/build SUBDIRS=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 modules
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)This message (or similar) is repeated several times, although it also appears that the software attempted to compile anyway.

Please run:
rpm -V kernel kernel-devel kernel-headers

and report results.

V

wulfgarpro
10th December 2009, 10:59 PM
Please see the below:


rpm -V kernel kernel-devel kernel-headers
S.5....T. /boot/initramfs-2.6.31.5-127.fc12.i686.img
S.5....T. /boot/initramfs-2.6.31.6-145.fc12.i686.img
S.5....T. /boot/initramfs-2.6.31.6-162.fc12.i686.img


wulfgarpro.

Hlingler
10th December 2009, 11:15 PM
No problems. Hmm... I wonder if it's a problem with that specific kernel[-devel|headers], or the newest VBox build. Either way, I would expect to see other people with similar problems, yet I don't recall seeing any.

My only further suggestion is to either downgrade VBox to previous stable, or update kernel* (preferably from updates-testing), then see what happens. I personally have not yet upgraded VBox to 3.1.0 r55467, and it looks like I won't be either. :D

Unless someone else has suggestions... <bump>

V