New host interface in version 2.1.2

betatester · Post by **betatester** » 26. Jan 2009, 10:00

Hello.

I'm testing the new version 2.1.2 in Windows XP Professional (SP3) as host. I was using version 2.0.6, and the version 2.1.2 installed over. When I run the guest machine with Windows XP too (with new host interface configured in the guest machine link to the physical interface), the host machine reboots unexpectedly.

I uninstalled version 2.1.2, deleted .Virtualbox (settings) and reinstalled them. The result was the same. Then I change the network guest machine settings to NAT and then works perfectly.

I created new host interface with the Microsoft loopback adapter, and I configured the guest machine with host interface to this virtual adapter. When I run guest, the host machine no longer reboots. When I make ping from host to guest don't work (and another service). From guest to host yes (it seems as the net filter don't work).

Any suggestions to resolve new host interface problems?

Post by **TerryE** » 26. Jan 2009, 15:34

Hi, have a search on this. Once of the issue is bridges left over from the 2.0.6 install. You need to clear down these before installing 2.1.2

betatester · Post by **betatester** » 27. Jan 2009, 09:10

Yes. I installed 2.1.2 over 2.0.6. But i uninstalled version 2.1.2 after problems. I deteled the directory c:\documents and settings\...\.VirtualBox and i reinstalled 2.1.2.
I need make something? what do you mean with "clear down"?

Thank you very much.

bobrnautus · Post by **bobrnautus** » 27. Jan 2009, 11:25

I have similar problem, If I use Host interface for network connecting and select Realtek RTL8139 Family PCI Fast Ethernet NIC in virtualbox settings (network adapter to bridge to), there is BSOD after I run virtual machine- IRQ not less or equal. If I create network bridge and select it in virtualbox settings, there is no reboot and network works as expected.

It seems new virtualbox host interface driver works well on virtual network adapters, or network bridges, but it doesn't work well on real network adapter for me. Tested on Windows XP SP3 Czech.

Feature request: What about to reenable old method of networking using tap-win32 adapter as alternate networking method?

betatester · Post by **betatester** » 27. Jan 2009, 11:58

Hello. Your problem is exactly the same as mine. I have a Realtek RTL8139 too (i have Windows XP SP3).
I think that reenable old method tap-win32 is not possible with new version 2.1.2. You have to downgrade to 2.0.6 (i'm not sure, but i don't find documentation about them).
I created a virtual interface with Microsoft Loopback Adapter. Then in the configuration of virtual guest machine i use in the host interface the virtual adapter. Finally if you need internet in the guest machine you can share connection of the real interface (internet) with the virtual, an then in the guest machine dns and gateway make to point to IP adress of the virtual interface in the host.
I have do this in another machine and works perfectly. If in another guest machine makes same, you will also have connection between them (virtual net with internet)

.
But in computer with the problem, the host machine don't see virtual machines. If i make a ping from host machine with ip 192.168.0.1 to virtual machine with ip 192.168.0.2 (two connected through the virtual interface) then don't work (from virtual machine to real host yes).
It seems as if the new net filter of virtualbox driver in the interface don't works (and it is enabled).

Post by **Sasquatch** » 28. Jan 2009, 01:19

Hmm, I have that realtek adapter in my laptop. I will try it later. Have to upgrade that one from 2.0.6 I think. I will be careful to remove any 2.0.6 remains before the upgrade.

Hmm, I do need a VM for it I think

. Hopefully, it works with my external hard drive. Haven't tried that in a long time.

neo314 · Post by **neo314** » 28. Jan 2009, 09:21

I'm seeing the same problem with a twist. I am hunting for information on host networking for Ubuntu guest on XP host WHEN ubuntu was installed using NAT (not sure if or how that might matter but of course it might).

From what I am ready, perhaps I am seeking a solution that does not exist...

Also using vbox 2.1.2

shinji · Post by **shinji** » 28. Jan 2009, 18:52

I have not personally seen this issue. Looks like it may be the adapter. Does everyone have a RTL8139?

I have a Intel 3945ABG Wireless and Broadcom 440x Ethernet adapter. Both work fine. Then again I havn't tried XP guest on XP host. Just linux guests on my XP host right now. They all worked fine and have good connectivity on both adapters.

neo314 · Post by **neo314** » 28. Jan 2009, 20:22

Actually I think my problem was solved by a reboot. And after the reboot, I had a glitch with Firefox that made me think I was not connected.

Post by **Sasquatch** » 28. Jan 2009, 22:23

I tried my laptop today, but while working on it, it got borked really bad. Now I can only login in safe mode. Both my user and Administrator can no longer log in. I think it has something to do with the disk check it wanted to do all this time. Didn't go to Windows that often, and in a few months, it's going for a full reinstall with Ubuntu Jaunty, no more Windows.

betatester · Post by **betatester** » 1. Feb 2009, 15:26

It is possible that problems may be due to having installed VirtualBox and VMware on the same machine? New host interface (net filter) is incompatible with VMware drivers installed simultaneously?

Post by **Sasquatch** » 1. Feb 2009, 15:32

I don't have VMWare. I think it had something to do with the fact that my system hung and almost crashed when removing the TAP interfaces. Not a real VB issue, it can happen with VMWare too, or any other application that works with system files. I don't mind, because I don't use that install anymore.

willyp · Post by **willyp** » 1. Feb 2009, 18:15

Solution:

For al the realtec users who have a BSOD. Please download the latest driver from

http://www.realtek.com.tw/downloads/dow ... Down=false

[ this is the realtec website]

Then update the your realtec network driver. After this driver update, there should be no problem anymore (at least for me, the problem is fixed)

bobrnautus · Post by **bobrnautus** » 8. Feb 2009, 13:27

If I install new realtec driver, there is no BSOD anymore, but there is another problem. If I run only host computer, everything is OK, but if I start virtualbox, host computer cannot reach network anymore, but guest computer can use network without problems. Only solution that works for me is creating network bridge and bind virtualbox to network bridge.... I wasn't able to find anything else.

betatester · Post by **betatester** » 13. Feb 2009, 10:27

I have not updated the driver for the network card because they never gave me problems, only with VirtualBox. I discovered that the second problem that I described (creating a virtual machine virtual interface was not seen by the host) was because of VMware. I installed VirtualBox and VMware on the same machine. When I installed VirtualBox VMware does not work as well (filter network). It appears that both drivers for the host interface are in conflict. Uninstall the driver of VirtualBox and VMware interface and went back to install the driver and returned to work for VMware. But if you installed the VirtualBox does not work and not VMware.

virtualbox.org

New host interface in version 2.1.2

New host interface in version 2.1.2

VMware and VirtualBox on same machine

New driver doesn't help