VBoxHeadless crashed with SIGSEGV

[Bruce Pieterse]

Crashes occasionally with vagrant and the vagrant halt command. I have seen this in earlier releases of vagrant as well (>= 1.8.0).

Vagrant 1.9.8

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: virtualbox 5.1.26-dfsg-2
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 13 10:18:56 2017
ExecutablePath: /usr/lib/virtualbox/VBoxHeadless
InstallationDate: Installed on 2017-04-02 (163 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
ProcCmdline: /usr/lib/virtualbox/VBoxHeadless --comment web-pos --startvm 5fe7e347-d163-4c33-895b-8934bc5a1eae --vrde config
SegvAnalysis:
 Segfault happened at: 0x7fa93ad09f77: movzbl (%rcx,%rdx,1),%r15d
 PC (0x7fa93ad09f77) ok
 source "(%rcx,%rdx,1)" (0x0001696a) not located in a known VMA region (needed readable region)!
 destination "%r15d" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: virtualbox
StacktraceTop:
 ?? () from /usr/lib/virtualbox/ExtensionPacks/VNC/linux.amd64/VBoxVNC.so
 ?? () from /usr/lib/virtualbox/components/VBoxC.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
 ?? () from /usr/lib/virtualbox/VBoxDD.so
Title: VBoxHeadless crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-08-10 (33 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 VNCServerImpl::VRDEUpdate (hServer=0x7fa9280041b0, uScreenId=<optimized out>, pvUpdate=0x7fa914b7f188, cbUpdate=<optimized out>) at /build/virtualbox-doDr0C/virtualbox-5.1.26-dfsg/src/VBox/ExtPacks/VNC/VBoxVNC.cpp:838
 Display::i_displayVBVAUpdateProcess (pInterface=<optimized out>, uScreenId=0, pCmd=0x7fa914b7f188, cbCmd=<optimized out>) at /build/virtualbox-doDr0C/virtualbox-5.1.26-dfsg/src/VBox/Main/src-client/DisplayImpl.cpp:4281
 vbvaFlushProcess (pVBVAData=0x7fa92c4eaa90, pVGAState=0x7fa94bc21100, uScreenId=0) at /build/virtualbox-doDr0C/virtualbox-5.1.26-dfsg/src/VBox/Devices/Graphics/DevVGA_VBVA.cpp:440
 vbvaFlush (pVGAState=0x7fa94bc21100, pCtx=0x7fa92c4eaa58) at /build/virtualbox-doDr0C/virtualbox-5.1.26-dfsg/src/VBox/Devices/Graphics/DevVGA_VBVA.cpp:521
 VBVAUpdateDisplay (pVGAState=pVGAState@entry=0x7fa94bc21100) at /build/virtualbox-doDr0C/virtualbox-5.1.26-dfsg/src/VBox/Devices/Graphics/DevVGA_VBVA.cpp:2847

[Gianfranco Costamagna (costamagnagianfranco)]

Hello, is it reproducible?

[Bruce Pieterse (octoquad)]

I have noticed that it only occurs with a single vagrant image in one of my projects. I currently have six different vagrant images. When I have some time available, I'll see if I can reproduce the crash reliably and share the steps.

[Launchpad Janitor (janitor)]

[Expired for virtualbox (Ubuntu) because there has been no activity for 60 days.]

[Bruce Pieterse (octoquad)]

I never got this crash again after upgrading to Vagrant 2.0.0.