VirtualBox

Ticket #2777 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

vboxnetflt fails to compile; when done manually fails to work.

Reported by: davidwhodgins Owned by:
Priority: major Component: installer
Version: VirtualBox 2.1.0 Keywords:
Cc: Guest type: Windows
Host type: Linux

Description (last modified by frank) (diff)

After installing 2.1.0, using the rpm, with a host of Mandriva 2009.0 on an i586 system, the vboxnetflt module had not been compiled.

Manually compiling the module using ...

#!/bin/bash
downloaddir=/home/dave/software
rpmfile="VirtualBox-2.1.0_41146_mdv2008.0-1.i586.rpm"
tmpdir="/tmp/VirtualBox"
mkdir -p "$tmpdir"
cd "$tmpdir"
rpm2cpio "$downloaddir/$rpmfile">"$tmpdir/VirtualBox.cpio"
cpio -i --make-directories < VirtualBox.cpio
cd "usr/src/vboxdrv-2.1.0/vboxnetflt/"
make
sudo make install

allowed VirtualBox to be started, but any attempt at network access failed, with messages such as ...

Dec 17 16:23:43 hodgins kernel: br_netfilter: Argh!! br_nf_post_routing: bad mac.raw pointer.
Dec 17 16:23:43 hodgins kernel: [eth0][br0] head:f5be5c00, raw:f5be5c20, data:f5be5c20
Dec 17 16:23:43 hodgins kernel: Pid: 6177, comm: VirtualBox Not tainted 2.6.27.7-desktop-0.uc2mnb #1
Dec 17 16:23:43 hodgins kernel:  [<c0381e62>] ? printk+0x18/0x1e
Dec 17 16:23:43 hodgins kernel:  [<fa69771f>] br_nf_post_routing+0x8f/0x2b0 [bridge]
Dec 17 16:23:43 hodgins kernel:  [<c031eee9>] nf_iterate+0x69/0xa0
Dec 17 16:23:43 hodgins kernel:  [<fa692020>] ? br_dev_queue_push_xmit+0x0/0x70 [bridge]
Dec 17 16:23:43 hodgins kernel:  [<c031efb7>] nf_hook_slow+0x97/0xe0

showing up in /var/log/syslog.

I've rolled back to 2.0.6 for now. In addition, I've found that trying to submit this ticket using opera fails. I've switched to firefox, to submit this ticket.

Change History

comment:1 Changed 5 years ago by frank

  • Description modified (diff)
  • Summary changed from Install of 2.1.0_41146_mdv2008.0-1.i586.rpm fails to compile vboxnetflt, and when done manually fails to work. to vboxnetflt fails to compile; when done manually fails to work.

It would be very useful if you would could write what the problem was when you compiled the vboxnetflt module. And:

  • Do you have installed dkms on your Mandriva system?
  • Which Linux kernel is that?

comment:2 Changed 5 years ago by davidwhodgins

The rpm package install showed "Success". Attempting to start the service vboxdrv failed with a message indicating modprobe vboxnetflt had failed. After extracting the rpm scripts, I found that there was no attempt to compile the vboxnetflt kernel module. It didn't fail to compile, it just never was compiled. I manually compiled and installed the vboxnetflt module. I also had to manually restore and start the /etc/init.d/vboxnet script, as it was not created by the rpm install. I was then able to start Virtualbox, running xp pro as a guest. Network access failed, with the br_netfilter messages showing up in syslog, on the host.

dkms is installed, and works for the vboxdrv module, but was not setup for vboxnetflt.

I'm currently running the kernel 2.6.27.7-desktop-0.uc2mnb from the Mandriva 2009 testing repository. Having rolled back to VirtualBox 2.0.6, VirtualBox is working. It may be worth noting that I'm using bridging for network access. Another user has reported in the alt.os.linux.mandriva usenet group, that 2.1.0 is working (after manually installing vboxnetflt), using nat routing.

comment:3 Changed 5 years ago by frank

I think I've fixed the problem, please could you download the Mandriva package again and check if it works for you?

comment:4 Changed 5 years ago by davidwhodgins

The install goes smoothly now. I'm still getting errors trying to access the net using xp pro as the guest, and using bridging on the host. The only errors are in syslog, such as ...

Dec 18 16:51:56 hodgins perl: [RPM] VirtualBox-2.1.0_41146_mdv2008.0-1 installed Dec 18 16:53:07 hodgins kernel: vboxdrv: Trying to deactivate the NMI watchdog permanently... Dec 18 16:53:07 hodgins kernel: vboxdrv: Successfully done. Dec 18 16:53:07 hodgins kernel: vboxdrv: Found 1 processor cores. Dec 18 16:53:07 hodgins kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. Dec 18 16:53:07 hodgins kernel: vboxdrv: Successfully loaded version 2.1.0 (interface 0x000a0008). Dec 18 16:53:10 hodgins perl: [RPM] VirtualBox-2.0.6_39765_mdv2008.0-1 removed Dec 18 16:53:43 hodgins kernel: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) Dec 18 16:54:32 hodgins kernel: br_netfilter: Argh!! br_nf_post_routing: bad mac.raw pointer. Dec 18 16:54:32 hodgins kernel: [eth0][br0] head:f4210800, raw:f4210820, data:f4210820 Dec 18 16:54:32 hodgins kernel: Pid: 24668, comm: VirtualBox Not tainted 2.6.27.7-desktop-0.uc2mnb #1 Dec 18 16:54:32 hodgins kernel: [<c0381e62>] ? printk+0x18/0x1e Dec 18 16:54:32 hodgins kernel: [<faa9f71f>] br_nf_post_routing+0x8f/0x2b0 [bridge] Dec 18 16:54:32 hodgins kernel: [<c031eee9>] nf_iterate+0x69/0xa0 Dec 18 16:54:32 hodgins kernel: [<faa9a020>] ? br_dev_queue_push_xmit+0x0/0x70 [bridge] Dec 18 16:54:32 hodgins kernel: [<c031efb7>] nf_hook_slow+0x97/0xe0 Dec 18 16:54:32 hodgins kernel: [<faa9a020>] ? br_dev_queue_push_xmit+0x0/0x70 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9a0c8>] br_forward_finish+0x38/0x60 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9a020>] ? br_dev_queue_push_xmit+0x0/0x70 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9efa7>] br_nf_forward_finish+0x107/0x110 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9a090>] ? br_forward_finish+0x0/0x60 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9f0a0>] br_nf_forward_arp+0xf0/0x100 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9eea0>] ? br_nf_forward_finish+0x0/0x110 [bridge] Dec 18 16:54:32 hodgins kernel: [<c031eee9>] nf_iterate+0x69/0xa0 Dec 18 16:54:32 hodgins kernel: [<faa9a090>] ? br_forward_finish+0x0/0x60 [bridge] Dec 18 16:54:32 hodgins kernel: [<c031efb7>] nf_hook_slow+0x97/0xe0 Dec 18 16:54:32 hodgins kernel: [<faa9a090>] ? br_forward_finish+0x0/0x60 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9a13b>] br_forward+0x4b/0x70 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9a090>] ? br_forward_finish+0x0/0x60 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa99fcb>] br_flood+0x9b/0xd0 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9a0f0>] ? br_forward+0x0/0x70 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9a00d>] br_flood_forward+0xd/0x10 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9acda>] br_handle_frame_finish+0x12a/0x140 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9abb0>] ? br_handle_frame_finish+0x0/0x140 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9ae3d>] br_handle_frame+0x14d/0x1c0 [bridge] Dec 18 16:54:32 hodgins kernel: [<faa9abb0>] ? br_handle_frame_finish+0x0/0x140 [bridge] Dec 18 16:54:32 hodgins kernel: [<c0303630>] netif_receive_skb+0x140/0x530 Dec 18 16:54:32 hodgins kernel: [<c02fa2be>] ? kfree_skb+0x1e/0x40 Dec 18 16:54:32 hodgins kernel: [<fab124dc>] ? tun_net_xmit+0xfc/0x1a0 [tun] Dec 18 16:54:32 hodgins kernel: [<c0303a8b>] process_backlog+0x6b/0xe0 Dec 18 16:54:32 hodgins kernel: [<c03033cd>] net_rx_action+0xed/0x210 Dec 18 16:54:32 hodgins kernel: [<c0135512>] do_softirq+0x92/0x120 Dec 18 16:54:32 hodgins kernel: [<c01355fd>] do_softirq+0x5d/0x60 Dec 18 16:54:32 hodgins kernel: [<c030181a>] netif_rx_ni+0x2a/0x30 Dec 18 16:54:32 hodgins kernel: [<fb182a3d>] vboxNetFltPortOsXmit+0x8d/0xb0 [vboxnetflt] Dec 18 16:54:32 hodgins kernel: [<fb18337c>] vboxNetFltPortXmit+0x4c/0x1b0 [vboxnetflt] Dec 18 16:54:32 hodgins kernel: [<c0149adb>] ? up+0x2b/0x40 Dec 18 16:54:32 hodgins kernel: [<c01232da>] ? dequeue_entity+0x2a/0xb0 Dec 18 16:54:32 hodgins kernel: [<c012348b>] ? set_next_entity+0x12b/0x160 Dec 18 16:54:32 hodgins kernel: [<c03845b8>] ? _spin_lock+0x8/0x10 Dec 18 16:54:32 hodgins kernel: [<fb03a3de>] ? RTSpinlockRelease+0xe/0x20 [vboxdrv] Dec 18 16:54:32 hodgins kernel: [<fb0329ea>] ? SUPR0ObjAddRefEx+0xfa/0x1c0 [vboxdrv] Dec 18 16:54:32 hodgins kernel: [<fb034c95>] ? supdrvIOCtl+0x725/0x2050 [vboxdrv] Dec 18 16:54:32 hodgins kernel: [<c023e575>] ? copy_from_user+0x35/0x130 Dec 18 16:54:32 hodgins kernel: [<c0385609>] ? iret_exc+0x809/0x976 Dec 18 16:54:32 hodgins kernel: [<fb0312a3>] ? VBoxDrvLinuxIOCtl+0xf3/0x1d0 [vboxdrv] Dec 18 16:54:32 hodgins kernel: [<c0385609>] ? iret_exc+0x809/0x976 Dec 18 16:54:32 hodgins kernel: [<fb0311b0>] ? VBoxDrvLinuxIOCtl+0x0/0x1d0 [vboxdrv] Dec 18 16:54:32 hodgins kernel: [<c01a9dfe>] ? vfs_ioctl+0x5e/0xa0 Dec 18 16:54:32 hodgins kernel: [<c0385609>] ? iret_exc+0x809/0x976 Dec 18 16:54:32 hodgins kernel: [<c01a9e9e>] ? do_vfs_ioctl+0x5e/0x2e0 Dec 18 16:54:32 hodgins kernel: [<c0385609>] ? iret_exc+0x809/0x976 Dec 18 16:54:32 hodgins kernel: [<c01aa183>] ? sys_ioctl+0x63/0x70 Dec 18 16:54:32 hodgins kernel: [<c0103e1b>] ? sysenter_do_call+0x12/0x2f Dec 18 16:54:32 hodgins kernel: [<c0385609>] ? iret_exc+0x809/0x976 Dec 18 16:54:32 hodgins kernel: [<c0385609>] ? iret_exc+0x809/0x976 Dec 18 16:54:32 hodgins kernel: =======================

There have been no changes in the network setup in either the guest, or the host, which were working with 2.0.6.

comment:5 Changed 5 years ago by davidwhodgins

Problem solved.

I switched to Nat routing, which still failed, during which I noticed it was set to use vbox0, with br0 listed as an alternative. I then switched back to Host Interface, and br0 was the only option listed. Selecting that, now has networking working.

Thanks, Dave Hodgins

comment:6 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use