[Solved] Virtualbox 2.1 on Etch cant connect Internet?

[nr5]

Hello!

I just installed Virtualbox 2.1 on Debian 4.0 Etch. All went well until i start windows server 2003 in the VM and log in, there is no connection to the Internet... Windows is using a static IP address and everything is up like it should, I even try "Repairing" the connection inside Windows and it said "all is well, contact network admin if u have issues" so Im guessing the problem is not within windows (was working with older version of virtualbox).

My Network settings in Virtualbox are Host Interface using eth0. I even tried changing to NAT but it dosnt help... Im not sure what to do ?

Anyone have a suggestion??

[bugsbunny]

post the output of:
In the host (debian)
#ifconfig
#route

On the windows box, from a command prompt:
ipconfig /all
(I'm pretty sure that's the command, going from memory).

[nr5]

From ifconfig

Code: Select all

$ sudo ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1D:7D:05:79:17 
          inet addr:192.168.0.101  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::21d:7dff:fe05:7917/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:599 errors:0 dropped:0 overruns:0 frame:0
          TX packets:465 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:62397 (60.9 KiB)  TX bytes:97014 (94.7 KiB)
          Interrupt:177 Base address:0x6000

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


From route

Code: Select all

$ sudo route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0


And from windows, ipconfig /all

Code: Select all

ipconfig /all

Windows IP Configuration

   Host Name .......................: win server
   Primary Dns Suffix ...........:
   Node Tyoe .......................: Unknown
   IP Routing Enabled ...........: No
   WINS Proxy Enabled .........: No

Ethernet adapter Local Area connection:

   Connection-specific DNS Suffix ...:
   Description ...............................: AMD PCNET Family PCI Ethernet Adapter
   Physical Address ........................: 00-01-20-E1-43-53
   DHCP Enabled ...........................: No
   IP Address ................................: 192.168.0.104
   Subnet Mask .............................: 255.255.255.0
   Default gateway ........................: 192.168.0.1


I also noticed a funny thing, when i log on to the router i can see the attached devices, 192.168.0.101 (debian host) AND Windows server thats running in Virtualbox 192.168.0.104...

Im unable to ping 192.168.0.104 or connect to it in any way...

I also noticed that my debian hos dropped its connection to the local network compleatly once or twice... but i could still see 192.168.0.104 (virtualbox windows) as an attached device in my router :S

If its any clue, i also noticed this message:

Code: Select all

Message from syslogd@o2 at Sat Dec 20 19:22:16 2008 ...
o2 kernel: Oops: 0000 [1] SMP

Message from syslogd@o2 at Sat Dec 20 19:22:16 2008 ...
o2 kernel: CR2: ffffffffffffff58

Message from syslogd@o2 at Sat Dec 20 19:22:16 2008 ...
o2 kernel: Oops: 0000 [2] SMP

Message from syslogd@o2 at Sat Dec 20 19:22:16 2008 ...
o2 kernel: CR2: ffffffffffffff58


But that only came up when I enable the new "Enable 3D Acceleration" so im guessing it has nothing to do with it.

[bugsbunny]

You said you have host bridged networking enabled as the networking option, correct? From the windows box can you ping:
192.168.0.101
192.168.0.1

and, from the host, can you ping
192.168.0.104

[bugsbunny]

assuming you can ping, and if the router has a web interface, can you get to the web interface from the windows box?

[nr5]

Code: Select all

You said you have host bridged networking enabled as the networking option, correct?

Hosted Interface eth0 yes (if thats the same thing)

From the windows box can you ping:
192.168.0.101
192.168.0.1

No I get "Request timed out"

and, from the host, can you ping
192.168.0.104

Same "Destination Host Unreachable"

I also found this in log/messages

Code: Select all

Dec 20 19:22:16 o2 kernel:  <6>device eth0 entered promiscuous mode
Dec 20 19:22:16 o2 kernel: audit(1229797336.346:2): dev=eth0 prom=256 old_prom=0 auid=4294967295
Dec 20 19:27:26 o2 kernel: device eth0 left promiscuous mode
Dec 20 19:27:26 o2 kernel: audit(1229797646.454:3): dev=eth0 prom=0 old_prom=256 auid=4294967295
Dec 20 19:28:23 o2 kernel: device eth0 entered promiscuous mode
Dec 20 19:28:23 o2 kernel: audit(1229797703.612:4): dev=eth0 prom=256 old_prom=0 auid=4294967295
Dec 20 19:38:22 o2 kernel: device eth0 left promiscuous mode
Dec 20 19:38:22 o2 kernel: audit(1229798302.242:5): dev=eth0 prom=0 old_prom=256 auid=4294967295

Think the changing of the promiscuous mode is whats causing debianhost to loose the connection... but thats not my main issue here

[bugsbunny]

I have to go and won't be back until at least late tomorrow, but I'd suggest you look at any firewall settings you may have on the windows box (that includes the default windows firewall if that's all you have). I'm almost certain the problem is inside Windows (almost, but not 100%).

The promiscuous mode stuff is fine, VB needs to set it that way in order to do it's thing. The entered should tie in with when you brought up a VB image, and the left with when you bring it down.

It shouldn't have any impact on your connection - unless your card is flaky somehow, then (a big) maybe.

From what I've seen so far VB is making the connection just fine, you can see the box, it's just isolated for some reason.

[ramoonas]

IMHO it is the best to set up bridged interface.

Look at this site:

http://wiki.debian.org/VirtualBox

there is a section there "Setting up bridged networking for VirtualBox", i followed it and it works very well for me.

[jellomizer]

I really hate saying this. But I am getting the same problem Including the kernel Messages.

Code: Select all

Message from syslogd@DevVMServer at Mon Dec 22 13:24:48 2008 ...
DevVMServer kernel: Oops: 0000 [1] SMP

Message from syslogd@DevVMServer at Mon Dec 22 13:24:48 2008 ...
DevVMServer kernel: CR2: ffffffffffffff58

Message from syslogd@DevVMServer at Mon Dec 22 13:24:48 2008 ...
DevVMServer kernel: Oops: 0000 [2] SMP

Message from syslogd@DevVMServer at Mon Dec 22 13:24:48 2008 ...
DevVMServer kernel: CR2: ffffffffffffff58


I think it is more kernel then a configuration issue. As the following happened when I upgraded.

1. After I installed the new version things seemed to work. Until I did a reboot and when I tried to run Virtrtualbox headless I would get a full kernel panic.

2. After I removed the old TAP settings the kernel panics stopped but now I cannot get bridged networking to work.

(2.1 is supposed to make it easier but it doesn't work)

I have tried uninstalling and reinstalling clearing all permissions and config files but still the same issue of it not booting up.

The Wiki doesn't seem to cover 2.1

[CellKill]

Installed from .deb package available on VirtualBox site and .run package.
Used AMD64 versions.

There is no visible error in VirtualBox, there is just no networking available between the guest and host systems.

VBoxManage -modifyvm <vmname>
-nic1 hostif
-hostifdev1 eth0
Both using ips in the same subnet.

The same error appears in a console message when starting the guest VM running Windows Server 2K8 Standard.

Code: Select all

Message from syslogd@over9000 at Wed Dec 24 03:34:53 2008 ...
over9000 kernel: Oops: 0000 [1] SMP

Message from syslogd@over9000 at Wed Dec 24 03:34:53 2008 ...
over9000 kernel: CR2: ffffffffffffff58

Message from syslogd@over9000 at Wed Dec 24 03:34:53 2008 ...
over9000 kernel: Oops: 0000 [2] SMP

Message from syslogd@over9000 at Wed Dec 24 03:34:53 2008 ...
over9000 kernel: CR2: ffffffffffffff58

Code: Select all

root@over9000:~# tail -n 70 /var/log/messages
Dec 24 03:25:49 over9000 -- MARK --
Dec 24 03:28:53 over9000 kernel: conftest[6062]: segfault at 00002b4e23c9204c rip 00002b4e2358fadb rsp 00007fff87752b70 error 4
Dec 24 03:34:51 over9000 kernel: device eth0 entered promiscuous mode
Dec 24 03:34:51 over9000 kernel: audit(1230111291.285:2): dev=eth0 prom=256 old_prom=0 auid=4294967295
Dec 24 03:34:53 over9000 kernel: PGD 203027 PUD 1030067 PMD 0
Dec 24 03:34:53 over9000 kernel: CPU 0
Dec 24 03:34:53 over9000 kernel: Modules linked in: vboxnetflt vboxdrv button ac battery ipv6 dm_snapshot dm_mirror dm_mod loop serio_raw evdev psmouse i2c_i801 i2c_core pcspkr ext3 jbd mbcache sd_mod ata_piix libata scsi_mod 8139too 8139cp mii generic jmicron ide_core r8169 ehci_hcd uhci_hcd thermal processor fan
Dec 24 03:34:53 over9000 kernel: Pid: 14, comm: events/0 Not tainted 2.6.18-6-amd64 #1
Dec 24 03:34:53 over9000 kernel: RIP: 0010:[<ffffffff8834772d>]  [<ffffffff8834772d>] :vboxnetflt:vboxNetFltLinuxXmitTask+0x1c/0x18e
Dec 24 03:34:53 over9000 kernel: RSP: 0018:ffff810227757e30  EFLAGS: 00010286
Dec 24 03:34:53 over9000 kernel: RAX: ffff81022842d8d8 RBX: 0000000000000000 RCX: ffff810227757ec8
Dec 24 03:34:53 over9000 kernel: RDX: ffff81022842d8d8 RSI: 0000000000000282 RDI: 0000000000000000
Dec 24 03:34:53 over9000 kernel: RBP: ffff810225ccaf30 R08: ffff810227756000 R09: ffff8101fe4c9cf8
Dec 24 03:34:53 over9000 kernel: R10: ffffffff8040775f R11: 0000000000000246 R12: ffff81022842d8c0
Dec 24 03:34:53 over9000 kernel: R13: fffffffffffffee8 R14: 0000000000000000 R15: ffffffff88347711
Dec 24 03:34:53 over9000 kernel: FS:  0000000000000000(0000) GS:ffffffff80522000(0000) knlGS:0000000000000000
Dec 24 03:34:53 over9000 kernel: CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Dec 24 03:34:53 over9000 kernel: CR2: ffffffffffffff58 CR3: 00000001fe379000 CR4: 00000000000026e0
Dec 24 03:34:53 over9000 kernel: Process events/0 (pid: 14, threadinfo ffff810227756000, task ffff81022773c830)
Dec 24 03:34:53 over9000 kernel: Stack:  0000000000000000 ffff81022773ca08 ffff810200000000 ffff810225ccaf28
Dec 24 03:34:53 over9000 kernel:  ffff810225ccaf30 ffff81022842d8c0 0000000000000282 ffffffff80249152
Dec 24 03:34:53 over9000 kernel:  ffffffffffffffff ffff81022842d8c0 ffffffff80245aec ffff81022857dd40
Dec 24 03:34:53 over9000 kernel: Call Trace:
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80249152>] run_workqueue+0x94/0xe5
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80245aec>] worker_thread+0x0/0x122
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80245bdc>] worker_thread+0xf0/0x122
Dec 24 03:34:53 over9000 kernel:  [<ffffffff8027c8e1>] default_wake_function+0x0/0xe
Dec 24 03:34:53 over9000 kernel:  [<ffffffff8023057c>] kthread+0xd4/0x107
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80258aa0>] child_rip+0xa/0x12
Dec 24 03:34:53 over9000 kernel:  [<ffffffff802304a8>] kthread+0x0/0x107
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80258a96>] child_rip+0x0/0x12
Dec 24 03:34:53 over9000 kernel:
Dec 24 03:34:53 over9000 kernel:
Dec 24 03:34:53 over9000 kernel: Code: 48 8b bf 58 ff ff ff 48 89 e6 e8 00 45 00 00 8a 83 64 ff ff
Dec 24 03:34:53 over9000 kernel:  RSP <ffff810227757e30>
Dec 24 03:34:53 over9000 kernel:  <1>Unable to handle kernel paging request at ffffffffffffff58 RIP:
Dec 24 03:34:53 over9000 kernel: PGD 203027 PUD 1030067 PMD 0
Dec 24 03:34:53 over9000 kernel: CPU 3
Dec 24 03:34:53 over9000 kernel: Modules linked in: vboxnetflt vboxdrv button ac battery ipv6 dm_snapshot dm_mirror dm_mod loop serio_raw evdev psmouse i2c_i801 i2c_core pcspkr ext3 jbd mbcache sd_mod ata_piix libata scsi_mod 8139too 8139cp mii generic jmicron ide_core r8169 ehci_hcd uhci_hcd thermal processor fan
Dec 24 03:34:53 over9000 kernel: Pid: 17, comm: events/3 Not tainted 2.6.18-6-amd64 #1
Dec 24 03:34:53 over9000 kernel: RIP: 0010:[<ffffffff8834772d>]  [<ffffffff8834772d>] :vboxnetflt:vboxNetFltLinuxXmitTask+0x1c/0x18e
Dec 24 03:34:53 over9000 kernel: RSP: 0018:ffff81022775fe30  EFLAGS: 00010286
Dec 24 03:34:53 over9000 kernel: RAX: ffff8102279d4558 RBX: 0000000000000000 RCX: ffff81022775fec8
Dec 24 03:34:53 over9000 kernel: RDX: ffff8102279d4558 RSI: 0000000000000282 RDI: 0000000000000000
Dec 24 03:34:53 over9000 kernel: RBP: ffff810225ccaf30 R08: ffff81022775e000 R09: 0000000000000000
Dec 24 03:34:53 over9000 kernel: R10: ffffffff8040775f R11: ffffffff8802e95b R12: ffff8102279d4540
Dec 24 03:34:53 over9000 kernel: R13: fffffffffffffee8 R14: 0000000000000000 R15: ffffffff88347711
Dec 24 03:34:53 over9000 kernel: FS:  0000000000000000(0000) GS:ffff81022842d940(0000) knlGS:0000000000000000
Dec 24 03:34:53 over9000 kernel: CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Dec 24 03:34:53 over9000 kernel: CR2: ffffffffffffff58 CR3: 0000000218ed6000 CR4: 00000000000026e0
Dec 24 03:34:53 over9000 kernel: Process events/3 (pid: 17, threadinfo ffff81022775e000, task ffff81022773d140)
Dec 24 03:34:53 over9000 kernel: Stack:  0000000000000000 ffff81022773d318 ffff810200000003 ffff810225ccaf28
Dec 24 03:34:53 over9000 kernel:  ffff810225ccaf30 ffff8102279d4540 0000000000000282 ffffffff80249152
Dec 24 03:34:53 over9000 kernel:  0000000000010000 ffff8102279d4540 ffffffff80245aec ffff81022857dd40
Dec 24 03:34:53 over9000 kernel: Call Trace:
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80249152>] run_workqueue+0x94/0xe5
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80245aec>] worker_thread+0x0/0x122
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80245bdc>] worker_thread+0xf0/0x122
Dec 24 03:34:53 over9000 kernel:  [<ffffffff8027c8e1>] default_wake_function+0x0/0xe
Dec 24 03:34:53 over9000 kernel:  [<ffffffff8023057c>] kthread+0xd4/0x107
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80258aa0>] child_rip+0xa/0x12
Dec 24 03:34:53 over9000 kernel:  [<ffffffff802304a8>] kthread+0x0/0x107
Dec 24 03:34:53 over9000 kernel:  [<ffffffff80258a96>] child_rip+0x0/0x12
Dec 24 03:34:53 over9000 kernel:
Dec 24 03:34:53 over9000 kernel:
Dec 24 03:34:53 over9000 kernel: Code: 48 8b bf 58 ff ff ff 48 89 e6 e8 00 45 00 00 8a 83 64 ff ff
Dec 24 03:34:53 over9000 kernel:  RSP <ffff81022775fe30>
Dec 24 03:42:01 over9000 kernel:  <6>device eth0 left promiscuous mode
Dec 24 03:42:01 over9000 kernel: audit(1230111721.857:3): dev=eth0 prom=0 old_prom=256 auid=4294967295
Dec 24 04:05:49 over9000 -- MARK --

Code: Select all

root@over9000:~# uname -a
Linux over9000.xx.com 2.6.18-6-amd64 #1 SMP Fri Dec 12 05:49:32 UTC 2008 x86_64 GNU/Linux

Code: Select all

root@over9000:~# lsmod
Module                  Size  Used by
vboxnetflt             91372  0
vboxdrv              1690028  1 vboxnetflt

[nr5]

Ok i solved it

The message "kernel: Oops" that appears when starting the virtual machine is a kernel bug so I figured i change my kernel.

I was first running kernel 2.6.18 and then upgraded to 2.6.25 but that gave me similar errors so i downgraded to 2.6.24 installing the kernel and sources and now it works great! No more kernel Oops and internet works perfectly.

[bugsbunny]

Latest kernel in sid/testing is 2.6.26-12 fwiw

Not sure if that works. Both 2.6.27 and 2.6.28 work fine though.