Opened 15 years ago
Closed 14 years ago
#6511 closed defect (fixed)
VirtualBox 3.1.x bridge mode does not work with Intel Atom 330 and RTL8168c card
Reported by: | syscon | Owned by: | |
---|---|---|---|
Component: | network | Version: | VirtualBox 3.1.6 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
Host Linux VM: Windows XP
When VB starts and Network card set in Bridge Mode the network does not start and I can not shut down the Windows-XP In addition my keyboard in Linux terminal windows does not respond, only mouse is working (no keyboard) and the only way I can shut down Linux box is to pull the power cord.
I duplicate the VM and it works OK in NAT and Bridge mode with the same router on my other Quad-core machine; but on Intel Atom 330 with RTL8168c network card only NAT mode is working. According to this page: Realtek RTL8169 supports "Promiscuous Mode" http://developer.novell.com/yes/70604.htm I hope the same direr is in Linux kernel.
dmesg |grep vbox [ 5.884216] vboxdrv: Trying to deactivate the NMI watchdog permanently... [ 5.884226] vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance [ 5.884230] vboxdrv: counter framework which can generate NMIs is active. You have to prevent [ 5.884234] vboxdrv: the usage of hardware performance counters by [ 5.884237] vboxdrv: echo 2 > /proc/sys/kernel/perf_counter_paranoid [ 5.884244] vboxdrv: Found 4 processor cores. [ 5.884652] vboxdrv: fAsync=0 offMin=0x678 offMax=0x4d7c [ 5.885581] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 5.885592] vboxdrv: Successfully loaded version 3.1.6 (interface 0x00100001).
Change History (3)
comment:1 by , 15 years ago
comment:2 by , 14 years ago
I presume this is some custom/rare Linux distro.
Please close this bug.
-Technologov
comment:3 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
SOLVED! The modules in: /etc/modules.autoload.d/kernel-2.6 I had them in wrong order: I had it: vboxdrv vboxnetadp vboxnetflt
such a simple mistake and it caused such a strange problems, it should be: vboxdrv vboxnetflt vboxnetadp