virtualbox.org

Hi all,

Im running Ubuntu 9.04 "Jaunty" amd64, using Virtualbox 2.2.4 PUEL. I setup a new VM with FreeBSD amd64 as guest OS. I add additional harddisks as raw disks (vmdk's). During heavy I/O, i continue to get segfaults. I also had this when version 2.2.2. The logs show:

[60327.316891] VirtualBox[21681]: segfault at 20 ip 00007f159fd66c32 sp 00007f1536ba5e10 error 4 in VBoxVMM.so[7f159fcbd000+12a000]
(..)
[164613.347935] VirtualBox[19352]: segfault at 20 ip 00007f5b68567c32 sp 00007f5afb112e10 error 4 in VBoxVMM.so[7f5b684be000+12a000]

These are two seperate segfaults. It takes about 30-60 minutes to trigger a segfault. During this time there is heavy disk I/O on the raw disks, i use AHCI as controller.
Also see the attachment, which is the log output of virtualbox.

So my question, what could be the reason of this? Could a guest "bsod" also trigger a segfault or is that simply something going wrong within Virtualbox itself? Should i file a bug report?
Thanks all!

I would say that since you were getting this before and now with version 2.2.4 you should file a bug report. Segfaults are nasty little buggers to run down. I usually get them when I have SELINUX (great idea but pain in the ...) installed and running. But with heavy IO's going on it could be something that the DEVs need to know about. Be sure to send the vbox.logs for all of the machines and it would be best if you could do this just after a fault. Send as much info as you can and a dump of the segfault would really help as well.

Link to the bugtracker is below my post and you will need to setup an account there as well. Sorry but they are not on this system.