Hello Ben, If you are wanting to investigate crashes, or to help us investigate them, the first thing to do is to build a debug version of VirtualBox from the svn sources. Debug versions produce a lot of assertions which may give information about the problem. You should then start VirtualBox in the debugger as follows. I assume that you have basic knowledge of using the GNU debugger here.
* Make sure that the kernel module is loaded and setup (if the binary version of VirtualBox is installed and works then that will be the case). * Start the VirtualBox server from a terminal prompt from the VirtualBox build directory: ~/VirtualBox/.../out$ LD_LIBRARY_PATH=. ./VBoxSVC * From another terminal prompt, from the same directory, start VirtualBox in the debugger: ~/VirtualBox/.../out$ LD_LIBRARY_PATH=. gdb --args ./VirtualBox -startvm [VM NAME] When you get an assertion, just continue, and the assertion should get logged. When the guest crashes, you can take a look at the various assertions, or post the log file (the one for that particular VirtualBox process). Regards, Michael ben scott wrote: > I have tried running an old game in both windows 2000 and XP > with Linux as the host and both ways it has crashed windows. The > default BSOD doesn't give much information. Would posting the info > be helpful and is there something I should do to get more information > about the crash? > > Thank you. _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
