Page 1 of 1

HOST NETWORK INTERFACE FREEZES SYSTEM

Posted: 4. Apr 2009, 07:35
by CORTINAANTONIO
Hello ,

I have centos 5.2 64 bit installed. I installed virtualbox 2.1.2 with Windows 2003 server 64 bit. I was able to use the host network interface until I updated CENTOS. The VM freezes the entire system. Hard reboot is the only choice. If I do not use the Host Network Interface .. it works well. I tried installing Vbox 2.1.4 but no change.

Strange that it worked perfectly well before the update. I have looking for a fix so that I may continue to use the Host Network Interface. I have also followed certain groups about enabling the VT-x. It is all good. it is there. Log file and all .

Any suggestions ?

Re: HOST NETWORK INTERFACE FREEZES SYSTEM

Posted: 4. Apr 2009, 13:56
by vbox4me2
Try 2.1.4 or try using a different virtual NIC for the VM.

Re: HOST NETWORK INTERFACE FREEZES SYSTEM

Posted: 4. Apr 2009, 19:49
by CORTINAANTONIO
Thanks for the reply. Actually I am using 2.1.4 .. I applied the patch as per other listings The issue seems to be solved for now. I used this patch >

he problem appears with pre-2.6.20 kernels only. The fix will be included into the next maintenance release. Since netflt driver always comes with source code those who urgently need the fix may apply the following patch to src/vboxnetflt/linux/VBoxNetFlt-linux.c (the path is relative to your vbox installation directory):

1031c1031
< INIT_WORK(&pThis->u.s.XmitTask, vboxNetFltLinuxXmitTask, NULL);
---
> INIT_WORK(&pThis->u.s.XmitTask, vboxNetFltLinuxXmitTask, &pThis->u.s.XmitTask);

Then, kernel modules need to be re-built with

/etc/init.d/vboxdrv setup

Only thing missing was the word NULL .. the rest was easy sailing.

Re: HOST NETWORK INTERFACE FREEZES SYSTEM

Posted: 7. Apr 2009, 19:40
by CORTINAANTONIO
Seems it is not steady sailing after all .. same problem
I applied the fix ..
Did not help .. I am at a loss at this point

Re: HOST NETWORK INTERFACE FREEZES SYSTEM

Posted: 8. Apr 2009, 02:17
by pschneider
I have the same problem, the indicated workaround did not work for me, so I have file this ticket http://www.virtualbox.org/ticket/3649 for the issue.

Hope that is gets fixed soon, this is a show stopper.