innotek Virtualbox crashes on WinXP install -- SOLVED

[rage007]

Howdy all. I was trying to get virtualbox to install Windows XP from an ISO on Mint 4.0. It would continually crash after grinding my machine to a near halt for 20min to an hour. Turns out that time was dependent on how large I made the disk.

The logs would provide strings like this prior to crash:

00:06:08.452 TM: Giving up catch-up attempt at a 91047054264 ns lag; new
total: 213802761262 ns
00:07:12.286 TM: Giving up catch-up attempt at a 62617010605 ns lag; new
total: 276419771867 ns
00:08:14.995 TM: Giving up catch-up attempt at a 60629632616 ns lag; new
total: 337049404483 ns
00:09:13.495 TM: Giving up catch-up attempt at a 61649589287 ns lag; new
total: 398698993770 ns

I found one message on the innotek forums that said using fixed size disks may cause that, but I was already using a dynamic one. Creating a new one did not help.

Finally I came across this post:
http://vbox.innotek.de/pipermail/vbox-t ... 02987.html

I was greedy in my setup and cranked the mem to 512mb and the video to 64mb. Taking those down to 192mb and 8mb resolved my issue. Works great now!

[Husse]

Then you must be low in memory on your box....
Always leave enough for the host system to run

[rage007]

Ahhh, that must have been it. My host system has 512 and I was allocating a gig. Well...I feel dumb.

[leo5111]

The VirtualBox kernel driver is not accessible to the current user. Make sure that the user has write permissions for /dev/vboxdrv by adding them to the vboxusers groups. You will need to logout for the change to take effect..
VBox status code: -1909 (VERR_VM_DRIVER_NOT_ACCESSIBLE).


Result Code:
0x80004005
Component:
Console
Interface:
IConsole {1dea5c4b-0753-4193-b909-22330f64ec45}

i get that when i try and start mine any ideas??