Windows guests abort and give segfaults on VB 5.1.2 Ubuntu Linux 12.04

[toadwarble]

We have two computers, one with Xeon, Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz another with Intel(R) Core(TM) i7 CPU X 990 @ 3.47GHz

Both are running Ubuntua 12.04 LTs.

Since the upgrade to VB 5.1.2 we have found that Windows guests (we've tried W XP and W10, both 64-bit) periodically crash. The guest window just disappears without warning and the manager window reports that the guest has "aborted".

I see on "dmseg" output that I get lines of the form:

[384887.115231] EMT-3[7104]: segfault at 10 ip 00007f261161621d sp 00007f264241db80 error 4 in VBoxDD.so[7f2611502000+286000] [388546.537415] EMT-3[7167]: segfault at 10 ip 00007f9f5f61221d sp 00007f9fac75fb60 error 4 in VBoxDD.so[7f9f5f4fe000+286000] [464658.332045] EMT-3[9504]: segfault at 10 ip 00007f303e61421d sp 00007f3072ffdb60 error 4 in VBoxDD.so[7f303e500000+286000] [466938.255705] EMT-3[12007]: segfault at 7fb56413e75c ip 00007fb5a8289206 sp 00007fb5d6afab60 error 4 in VBoxDD.so[7fb5a8175000+286000]

(Those were on the Xeon machine)

and

[471102.107026] VirtualBox[24129]: segfault at 18 ip 00007f9f46e0de1f sp 00007ffe6f309940 error 4 in libQt5XcbQpaVBox.so.5[7f9f46da4000+145000] [471102.107038] VirtualBox[24181]: segfault at 18 ip 00007f6a4b68ee1f sp 00007ffdde5b9ad0 error 4 in libQt5XcbQpaVBox.so.5[7f6a4b625000+145000]

(Those were on the i7 machine)

I attach log files from both machines.

Reverting to VB 5.0 seems to make the problem go away.

[toadwarble]

Log file from Xeon machine last take immediately after a crash

[toadwarble]

Log file from i7 machine surrounding crash time.

[chrijm]

I too am seeing this issue and it can be very annoying, but it is not limited to the specific host or guest OS listed here. My VM's with Windows (7 & 10) as the guest will usually crash about once or twice a day, sometime more often. My VM with Oracle Linux as the guest has also crashed, but only once or twice since the 5.1 release. My host OS is OSX 10.11.6

[Don Hughes]

Same issue:

Aug 7 07:42:19 Gull2 kernel: EMT-3[10708]: segfault at 10 ip 00007f2ec1850709 sp 00007f2efe14ab90 error 4 in VBoxDD.so[7f2ec173d000+285000]

SuSE 13.2 64 bit host, Windows 10 guest.

Seems to happen when I am playing a video.

[Frank Mehnert]

don, can you provide a core dump? Unfortunately I cannot provide you a server for uploading so you might want to chose a server yourself and tell me the URL. Feel free to contact me via email at frank _dot_ mehnert _at_ oracle _dot_ com.

[Fuquay]

I too have exactly this issue. I've got a Windows 10 VM running on an Ubuntu host with Virtualbox 5.1.2.r108956 and up-to-date extensions and guest additions. The VM frequently crashes. There doesn't appear to be a specific trigger, but I can say that it appears to happen when I'm doing something (like clicking on a directory or within an application - provoking some kind of change on screen) rather than when the Windows OS is idle. The syslog reports the same message as above: segfault in VBoxDD.so. The Ubuntu host has an NVidia graphics card running version 361.42 of the NVidia drivers.

[Frank Mehnert]

Having a core dump would help a lot.

[Fuquay]

Frank, I sent you an email.

[Don Hughes]

I will enable dumps and update when I can collect one.

[Don Hughes]

Two system aborts today, but no dumps created. Used procedure outlined in the wiki

ulimit -c unlimited echo -n 1 | sudo tee /proc/sys/fs/suid_dumpable

using openbox as display manager.

[gpeddle]

I have the same experience of Windows 8.1 Guest aborting suddenly with syslog showing the crash as thread 14 EMT-3. This has been happening all summer, once or twice a week (I think, but I cannot be sure that it coincides with the upgrade to 5.1)

The host is running VirtualBox 5.1.2 r108956 and I have followed the new releases closely, usually installing within a week or so.

MacBook Pro (Retina, 15-inch, Mid 2014)
Model Name:	MacBook Pro
  Model Identifier:	MacBookPro11,3
  Processor Name:	Intel Core i7
  Processor Speed:	2.5 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 KB
  L3 Cache:	6 MB
  Memory:	16 GB

The crash log has this excerpt:

...
Time Awake Since Boot: 1300000 seconds

System Integrity Protection: enabled

Crashed Thread:        14  EMT-3

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000027
Exception Note:        EXC_CORPSE_NOTIFY

VM Regions Near 0x27:
--> 
    __TEXT                 00000001046d1000-00000001046d8000 [   28K] r-x/rwx SM=COW  /Applications/VirtualBox.app/Contents/MacOS/VirtualBoxVM
...

...
Thread 13:: EMT-2
0   libsystem_platform.dylib      	0x00007fff92fa9c49 _platform_bzero$VARIANT$Haswell + 41
1   VBoxDD.dylib                  	0x0000000112b09149 
...

[gpeddle]

Crash Log file from Windows8.1 Guest crash running VB 5.1.2 under MacOS

[Frank Mehnert]

This crash is most likely fixed with 5.1.4.

[Frank Mehnert]

Please reopen if still relevant with 5.1.4.

[Fuquay]

I've upgraded to 5.1.4r110228, and am still getting the crash. Re-opened.

[Frank Mehnert]

Fuquay, could you provide a core dump for 5.1.4?

[Fuquay]

Yes. I've just done so. I'll make it available to you as per our direct communication.

[Fuquay]

By the way, it appears that if I click around folders within Windows Explorer for long enough, I can provoke a crash. This is how I generate the dumps. It's also sometimes happens to me when using Microsoft Word 2016, but maybe this was because I was opening/saving a file, and Word embeds Windows Explorer in some fashion. Just now it happened to me while clicking on the screen as I was about to log in though. No obvious Windows Explorer link there.

[Fuquay]

The crashes are happening sufficiently frequently that the virtual machine is completely unusable. I'm going to have to switch back to the 5.0 branch of VirtualBox to see if that helps matters. (I was having display issues with that, but at least the whole VM didn't just crash.)

[Don Hughes]

Upgraded to 5.1.4. Guest system aborted while I was upgrading the guest's extensions.

[Frank Mehnert]

Just for the record: I've got a core dump from Fuquay and it shows that there is a crash in the audio backend. We are working on a fix.

[pentagonik]

@Fuquay I'm not able to reproduce this so far. Did you find a (more) reproducible way in the meantime?

[Don Hughes]

My aborts have all occurred when switching between different windows - usually multiple full screen .RDP sessions. I do not believe that there was any audio involved.

I have not been able to generate a core dump. Is there something other than what is in the wiki that I need to do?

[wacher]

Same issue here. I can't provide core, sorry, I've already downgraded from 5.1.4 to to 5.0.26 which seems to be good and stable.

VBox log shows nothing, not even the TERMINATED or ERROR status. Anyway, the last modification time of log file is earlier (with several minutes) than the crash occurred.

The symptoms are exactly same what are described in #comment4, nothing specific, sometimes just a click somewhere (in excel, Firefox, whatever). Frequency: from "once a day" to "twice in ten minutes".

Segfaults in my dmesg: [120689.153911] nspr-3[11266]: segfault at 14 ip 00007f8899e0d38e sp 00007f8807dc97d0 error 4 in VBoxRT.so[7f8899cbe000+23b000] [285727.663401] EMT-1[9002]: segfault at 10 ip 00007fe8ba610fe1 sp 00007fe8f941ab60 error 4 in VBoxDD.so[7fe8ba4fc000+289000]

Host: LinuxMint 17.3 Guest: W10 build 14905 (Insider)

[toadwarble]

I've got it all set up on a laptop and I'll jig around with that today and try go get a core dump.

[toadwarble]

Got laptop with Ubuntu 16.04 on it and VB 5.1.4

Ramped up ulimit -c, fixed core_pattern

Had it crash a few times but no core.

Running from chmod 777 directories hasn't crashed since grrrr.

[toadwarble]

Well this is weird.

I've had the thing running all day W7 on VB 5.1.4 on a laptop with Ubuntu 16.04 on it.

Previously it was crashing all the time.

I started a terminal process, set ulimit -c sky-high, created a directory, cd-ed to it, did chmod 777 . and ran virtualbox and from that process kicked off W7.

I've run Word, Google Chrome, BBC news with audio chat, Explorer including with a shared folder, a couple of games and CD image on a memory stick (the laptop doesn't have a CD drive) all at the same time and separately and it's stopped crashing.

Yet the mod time on the directory hasn't changed.

Maybe it's something weird about probing the current directory?

I only chmoded it to make sure of getting a core dump.

Found a bug in Ubuntu that the "core_pattern" if you remove "apport" is core.%e.$p it should be core.%e.%p

Anyhow hope that helps.

[aferngas]

Same issue here with all 5.1 versions until r110228 (Qt5.6.1). Both package alternatives: OSE (virtualbox) & BIN (virtualbox-bin). Version 5.0.24 works fine.

Host: ArchLinux Kernel: 64Bits 4.7.1-1 Guest: Windows 7 Pro 64Bits

Segfaults in my dmesg:

[ 3720.789603] EMT-1[1469]: segfault at 10 ip 00007f3a6b6200b0 sp 00007f3ab03f4b30 error 4 in VBoxDD.so[7f3a6b51e000+267000]

[ 5980.080732] EMT-1[2051]: segfault at 10 ip 00007fdfcf6200b0 sp 00007fe0144f6b30 error 4 in VBoxDD.so[7fdfcf51e000+267000]

[ 8691.968488] EMT-1[2883]: segfault at 10 ip 00007ff21d71cd2f sp 00007ff246690b30 error 4 in VBoxDD.so[7ff21d61b000+267000]

[19522.091993] EMT-1[4486]: segfault at 48 ip 00007f50a4c1058a sp 00007f50d12c9b90 error 4 in VBoxDD.so[7f50a4b11000+267000]

[20207.063162] EMT-1[4663]: segfault at 10 ip 00007f40a129b0b0 sp 00007f40ca192b30 error 4 in VBoxDD.so[7f40a1199000+267000]

[29681.216334] EMT-1[5715]: segfault at 10 ip 00007f150425b0b0 sp 00007f15414f8b30 error 4 in VBoxDD.so[7f1504159000+267000]

This error occurs apparently without any type of pattern, totally random.

[Frank Mehnert]

aferngas, thanks for the core dump. That crash is about the audio code. Could you try the latest "development test build" (please scroll that page down) from here and check if the crash still happens?

If the crash still happens, any idea how to reproduce the crash reliably? So far we are unable to reproduce it. The test builds contain fixes for a potential problem but as we could not reproduce it, it's hard to say if the fix is sufficient. Thank you!

[stevebamber]

i've been having constant crashes under 5.1.4 - Windows 2012 Server Guest running on Windows 7

uninstalling guest additions was the only way to keep the guest running on 5.1.4

since upgrading to 5.1.x revision 110354 from the Test Builds page though it does seems far more stable, hopefully the fix applied to the audio code has done the trick

[Ken Hagan]

I was seeing the same symptoms, in my case aborting every hour or two at apparently random moments. I haven't tried the test build, but I changed my VM settings to uncheck the "Enable audio" box and I haven't seen the problem since, which is now about 8 hours of usage. (Touch wood...)

If disabling audio means that we completely avoid the suspect part of the audio code, then my experience is consistent with this code being the root cause.

[pentagonik]

@Ken Hagan Please try enabling audio again with using the latest "development test build" as Frank described above. This would help us judging whether we can assume having the problem fixed or not. Thank you!

[pentagonik]

I've made some fix in the hope that we can shed some more light on this issue.

Could you please supply the verbose VBox.log file as shown here: Investigating audio problems

The test build can be downloaded from the Testbuilds page.

Scroll down to the Development Snapshots section and download the build appropriate for your host platform.

Could you please try this and provide the usual VBox log files afterwards then?

This test build is not intended for production use!

Thank you!

[Ken Hagan]

I am grabbing 110417 (the snapshot) now. Ta.

[Ken Hagan]

Using dev snapshot 110417, attempt to provoke the problem.(I have no sure-fire way to do this, but I've had a go.

[Ken Hagan]

I presume that it would make sense for me to continue to use this version for a day or so.

[Andrew_W]

I'm having the same issue with VirtualBox 5.1.4 r110228 on OS X 10.11.6. I'm running a Windows 10 guest, and able to crash VirtualBox with a segmentation fault by simply opening a new email in Outlook and holding the backspace key in the VM.

Running VirtualBox with the --dbg flag, and within 2 seconds of holding the backspace key down VBox crashes with Segmentation Fault: 11. There is no other information in any of the application logs, in the console log the following:

Process: VirtualBoxVM [12962] Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM Identifier: org.virtualbox.app.VirtualBoxVM Version: 5.1.4 (5.1.4) Code Type: X86-64 (Native) Parent Process: VBoxSVC [9279] Responsible: VirtualBoxVM [12962] User ID: 501

Date/Time: 2016-09-06 13:19:34.119 -0400 OS Version: Mac OS X 10.11.6 (15G1004) Report Version: 11 Anonymous UUID: 83B79342-79EA-0039-673E-9F1133AC4AF1

Time Awake Since Boot: 23000 seconds

System Integrity Protection: enabled

Crashed Thread: 12 EMT-1

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000027 Exception Note: EXC_CORPSE_NOTIFY

I'll install 110417 to see if it's resolved there.

[Andrew_W]

Replying to Andrew_W:

I'm having the same issue with VirtualBox 5.1.4 r110228 on OS X 10.11.6. I'm running a Windows 10 guest, and able to crash VirtualBox with a segmentation fault by simply opening a new email in Outlook and holding the backspace key in the VM.

Running VirtualBox with the --dbg flag, and within 2 seconds of holding the backspace key down VBox crashes with Segmentation Fault: 11. There is no other information in any of the application logs, in the console log the following:

Process: VirtualBoxVM [12962] Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM Identifier: org.virtualbox.app.VirtualBoxVM Version: 5.1.4 (5.1.4) Code Type: X86-64 (Native) Parent Process: VBoxSVC [9279] Responsible: VirtualBoxVM [12962] User ID: 501

Date/Time: 2016-09-06 13:19:34.119 -0400 OS Version: Mac OS X 10.11.6 (15G1004) Report Version: 11 Anonymous UUID: 83B79342-79EA-0039-673E-9F1133AC4AF1

Time Awake Since Boot: 23000 seconds

System Integrity Protection: enabled

Crashed Thread: 12 EMT-1

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000027 Exception Note: EXC_CORPSE_NOTIFY

I'll install 110417 to see if it's resolved there.

I've been using 5.1.5 r110484 for about an hour now, and haven't been able to crash it. This fixes the issue for me.

[Mellon]

Same issue with Ubuntu 16.04 host and Windows 7 Pro guest (both 64 bit). Since upgrade to VB 5.1.x the guest freezes for some minutes and then crashes several times a day. I switched back to 5.0.26 and everything is fine again.

[pentagonik]

@Mellon Can you also please use the latest development snapshot (see comment 30) and try if this fixes it for you? Thanks!

[Teja Swaroop Bezawada]

Same issue with VB 5.1.4, Win 7 Guest, RHEL 7.2 Host.

Sep 9 06:31:38 <hostname> kernel: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) Sep 9 06:31:56 <hostname> kernel: SUPR0GipMap: fGetGipCpu=0x3 Sep 9 06:32:00 <hostname> kernel: vboxdrv: ffffffffa0b34020 VMMR0.r0 Sep 9 06:32:01 <hostname> kernel: vboxdrv: ffffffffa0c33020 VBoxDDR0.r0 Sep 9 06:32:20 <hostname> kernel: EMT-1[4750]: segfault at 6088 ip 00007f73f8e88e69 sp 00007f743c709b70 error 4 in VBoxDD.so[7f73f8d75000+287000]

[pentagonik]

@Teja Swaroop Bezawada Which VBox version are you running exactly?

[Don Hughes]

Running 5.1.5-110527. The VM has not aborted as before, but now the guest blue screens.

[stevebamber]

i've given up with 5.1.x and reverted to 5.0.26 - everything is stable again

5.1.x guest additions seem to be hopelessly flawed - as soon as they are installed guest becomes unstable

doesn't seem to be just the audio drivers either - regular crashing even with those disabled

[Ken Hagan]

I think people have a variety of problems here. *My* problem appears to be completely fixed by the test build recommended by frank and pentagonik. I've had precisely zero recurrences over the last fortnight of the problem that previously struck several times per day.

So *something's* been fixed. :)

[chrijm]

I'm still seeing the guest abort, mostly on Windows guests., on version 5.1.6 r110634. It seems to crash with various host types and guest types, but most common with Windows guests.

Always get NS_ERROR_FAILURE (0x80004005) and nothing really stands out in the logs

Ticket #15797 is similar/same issue.

[pentagonik]

Does the crash still happen for you using 5.1.24?