Todd and Margo Chester wrote:

Todd and Margo Chester wrote:

...

Hi All,

I just removed Virtual Box 2.1.0 from my system.  When you

boot up an XP guest, you will get a kernel panic. See http://www.virtualbox.org/ticket/2827 for details.

I hope I saved someone else from the hassle I just

had to go through.

-T

Now for FSCK on my hard drive!

A duplicate of my bug was posted at VBOX: http://www.virtualbox.org/ticket/2829 on RHEL 5. He narrowed it down to "host interface" networking, which is exactly what I am using.

I made sure all my previous bridging was removed before install VB 2.1.0. (Yes, I had to put it back in before reverting. Good thing I take good notes!)

An update. It seems they got it fixed (in the next release) From ticket 2829:

12/29/2008 10:25:54 PM changed by aleksey ¶

Formatting of the previous message got ugly so I am reposting the corrected version:

The 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