Comment 11 for bug 246067

i've experienced the very same problem. in fact virtualbox often closes with the virtual machine "booting" and leaves log files in my home folder. the most recent one contains this information (if it's of any help) :

Log created: 2008-07-14T15:46:37.801203000Z
Executable: /usr/lib/virtualbox/VirtualBox
Arg[0]: /usr/lib/virtualbox/VirtualBox
Arg[1]: -comment
Arg[2]: Development
Arg[3]: -startvm
Arg[4]: 8584ee88-3448-4011-bb9a-616db97c989f
internal REM fatal error: rc=VERR_INTERNAL_ERROR cpu_outb

!!Assertion Failed!!
Expression: <NULL>
Location : /build/buildd/virtualbox-ose-1.5.6-dfsg/src/recompiler/VBoxRecompiler.c(4679) remAbort
internal REM fatal error: rc=VERR_INTERNAL_ERROR cpu_outb

whenever the virtual machine does not get closed, this error appears:
Code 3c 62 20 00 6f 64 65 3a 20 00 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 3d 0a 00 31 61 2f 30 78 32 30 0a 00 30 20 74 61 73 <6B> 3d 63 30 34 33 63 33 34 30 20 74 61 73 6b 2e 74 69 3d 63 30
EIP: {<c04ee7eb>] printk_buf.24875+0x2b/0x400 SS:ESP 0068:c046f780
Kernel panic - not syncing: Fatal exception in interrupt

host: hardy 8.04 , kubuntu, using virtualbox. if i can be of any further assistance please let me know.

ANDREA

btw: i get 0 success rate with the options previously mentioned, i have not even once been able to correctly boot using 2.6.26 ...