id,summary,reporter,owner,description,type,status,priority,component,version,resolution,keywords,cc,guest,host
9029,VBox 4.0.8 segfaults under heavy load (segfault at 18 ip b5948f37 sp b6427f50 error 4 in VBoxREM32.so[b5934000+7d000]),sergiomacedo,,"I have a host with Core(TM)2 Quad CPU Q9400, 4GB RAM, with a guest using all four cores and 1.5GB RAM, with bridged interface. Both guest and host are Centos4-based, running kernel 2.6.27.45.
During tests with VBox 4.0.x, I'm executing some stress procedures on the guest (dledford-memtest script, a home made sequential disk write/read and a mprime instance for each core) and a ""ping -f -s 1500"" from the host to the guest.
Usually this procedure runs well for at least 24 hours, however, after VBox 4.0.x we can't keep the machine running under stress for half this time (for a test started at 14:57 local time, we had a crash near 23:30).
May or may not be related, but with VBox 4.0.2, the VM crashed as well and with VBox 4.0.6 the VM crashed WITHOUT the stress procedure... just letting it on was enough to get the same segfault (the host never is directly under stress and when there are other VMs running, they also aren't under stress).
The VBox.log is attached but it doesn't show much after boot time.
The crash messages are:
VBox 4.0.2
Apr 20 23:56:11 host kernel: VBoxHeadless[14083]: segfault at 18 ip b5d4af37 sp b65d5f50 error 4 in VBoxREM32.so[b5d36000+7d000]
VBox 4.0.2:
May 12 04:45:22 host kernel: VBoxHeadless[21710]: segfault at 18 ip b5e10f37 sp b659df50 error 4 in VBoxREM32.so[b5dfc000+7d000]
VBox 4.0.6:
May 30 20:16:01 host kernel: VBoxHeadless[2043]: segfault at 18 ip b5948f37 sp b6427f50 error 4 in VBoxREM32.so[b5934000+7d000]
VBox 4.0.8:
May 31 23:44:39 host kernel: VBoxHeadless[9942]: segfault at 18 ip b5d9cf37 sp b6620f50 error 4 in VBoxREM32.so[b5d88000+7d000]
If you need something else, please ask soon because I'll have to roll back the VMs to 3.2.12 as soon as possible.
",defect,closed,major,other,VirtualBox 4.0.8,fixed,segfault VBoxREM32,,Linux,Linux