VBoxHeadless crashed with SIGSEGV

Bug #1241445 reported by Sean Young on 2013-10-18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)

Bug Description

The crash most likely occured while it was running one of the virtual machines in the BOINC project LHC@home, Test4Theory sub-project which uses virtual machines running in the headless VirtualBox client.

May be related to the many other SIGSEGVs reported for VirtualBox (will check the dump log and see if this is an obvious dup)

Ubuntu version:
Description: Ubuntu 12.04.3 LTS
Release: 12.04

Package: virtualbox
Package-Version: 4.1.12-dfsg-2ubuntu0.2

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: virtualbox 4.1.12-dfsg-2ubuntu0.2
ProcVersionSignature: Ubuntu 3.2.0-54.82-generic 3.2.50
Uname: Linux 3.2.0-54-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.5
Architecture: amd64
CrashCounter: 1
Date: Wed Oct 16 16:45:06 2013
ExecutablePath: /usr/lib/virtualbox/VBoxHeadless
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/lib/virtualbox/VBoxHeadless --comment boinc_wu_1378991704_35572_0 --startvm 65456ff1-cde3-478b-86a8-ddada2c26bce --vrde config
 PATH=(custom, no user)
 Segfault happened at: 0x7f7484bb0cb1: mov (%rax),%rax
 PC (0x7f7484bb0cb1) ok
 source "(%rax)" (0xffffffffffffffff) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: virtualbox
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxVMM.so
 ?? () from /usr/lib/virtualbox/VBoxRT.so
Title: VBoxHeadless crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: video

Sean Young (techsy730) wrote :
information type: Private → Public

 dnsproxy_query (pData=0x7f7458001240, so=0x7f7458001390, m=<optimized out>, iphlen=<optimized out>) at /build/buildd/virtualbox-4.1.12-dfsg/src/VBox/Devices/Network/slirp/dnsproxy/dnsproxy.c:276
 slirp_select_fill (pData=0x7f74781f7f90, pnfds=0x7f74698b2d78, polls=<optimized out>) at /build/buildd/virtualbox-4.1.12-dfsg/src/VBox/Devices/Network/slirp/slirp.c:960
 drvNATAsyncIoThread (pDrvIns=0x7f74781ebcd0, pThread=0x7f74781ee9e0) at /build/buildd/virtualbox-4.1.12-dfsg/src/VBox/Devices/Network/DrvNAT.cpp:748
 pdmR3ThreadMain (Thread=0x7f747820af70, pvUser=0x7f74781ee9e0) at /build/buildd/virtualbox-4.1.12-dfsg/src/VBox/VMM/VMMR3/PDMThread.cpp:787
 rtThreadMain (pThread=0x7f747820af70, NativeThread=<optimized out>, pszThreadName=<optimized out>) at /build/buildd/virtualbox-4.1.12-dfsg/src/VBox/Runtime/common/misc/thread.cpp:703

Changed in virtualbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in virtualbox (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers