guest OS (win XP) won't start at all with VB 3.0.2

[djg1971]

host OS = arch linux (kernel 2.6.30.2-1)
guest OS = windows XP

Ever since upgrading to 2.6.30 series kernel(s), the VirtualBox gui starts fine, but the guest OS will not boot.
from the log file, the problem seems to be in the guest OS recognizing its "hard drive" :

=============================================================================
00:00:03.769 Guest Log: BIOS: Booting from Hard Disk...
00:00:03.777 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=00000000 w=720 h=400 bpp=0 cbLine=0x0
00:00:04.224 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!
00:00:04.225 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!
00:00:04.225 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!
00:00:04.225 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!
00:00:04.226 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!
00:00:04.226 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!
00:00:04.227 Guest Log: BIOS: int13_harddisk: function 02, parameters out of range 0000/0000/0001!
00:00:11.509 Changing the VM state from 'RUNNING' to 'SUSPENDED'.
00:00:13.552 Console::powerDown(): A request to power off the VM has been issued (mMachineState=8, InUnini
t=0)
00:00:13.552 VRDP: TCP server closed.
00:00:13.560 ****************** Guest state at power off ******************
========================================================================

I tried to submit a bug ticket and to get some feedback from someone (anyone) about:

a) what is going on?
b) is anyone else observing this behavior?
c) is there anything I can do about it?
d) is anyone doing anything about it?

--> basically, will it ever work again, and if so is it likely to happen before 2010?

Very frustrating. Within the arch linux community, someone pointed to a link which suggests that there are known problems with the 2.6.30 series linux kernels and VirtualBox, but alas the posts are old, and otherwise there is no news.

Anyone have any comments?

[Perryg]

I seem to remember reading that other distros that used this version of the kernel had to disable NMI checking in the boot parm or something to that effect.
Try google.com and search for disable NMI and see if you can find something that you can do. I definitely know it is a kernel specific issue as I have read about this on the Ubuntu forum as well.