FS#41951 - [virtualbox] Windows VMs result in "Aborted" status

Attached to Project: Arch Linux
Opened by DJ Lucas (DJ_Lucas) - Friday, 12 September 2014, 19:13 GMT
Last edited by Evangelos Foutras (foutrelis) - Sunday, 14 September 2014, 16:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Unable to start VirtualBox VMs with windows OS (or install from Windows boot media)
Version: 4.3.16-1
Logs: unavailable
Steps to reproduce: Unknown. Downgraded to 4.3.8-2 to get around it temporarily. Existing VMs are fine after downgrade. Ignored package for now.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Sunday, 14 September 2014, 16:31 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Incompatibility caused by older extension pack.
Comment by Janne Rönkkö (jroo) - Saturday, 13 September 2014, 07:55 GMT
I'm facing this issue also. Downgrading to VirtualBox 4.3.14 resolves the problem.

In fact, starting any VM (either Windows or Linux guest) the result is "Aborted". Resuming saved machine states worked fine, though.

The only log I'm able to find is from dmesg:
[ 538.984987] nspr-4[2382]: segfault at 35 ip 0000000000000035 sp 00007ff03a9a3668 error 14 in VirtualBox[400000+7000

Only one entry per one failure. Here is couple of more entries for other crashes:
[ 75.041984] EMT-0[1262]: segfault at 618 ip 00007f0008e71da1 sp 00007f004257dcb0 error 4 in VBoxDD.so[7f0008dc5000+178000]
[ 106.301299] EMT-1[1492]: segfault at 618 ip 00007f48436bada1 sp 00007f4881a7dca0 error 4 in VBoxDD.so[7f484360e000+178000]
[ 247.691857] EMT-0[1911]: segfault at 618 ip 00007f19174b9da1 sp 00007f19553aecf0 error 4 in VBoxDD.so[7f191740d000+178000]
Comment by Alex (nylocx) - Saturday, 13 September 2014, 18:35 GMT
I could solve that by issue by installing the new virtual box extension package from the VirtualBox site.
https://www.virtualbox.org/wiki/Downloads
Comment by onofre (onoakino) - Saturday, 13 September 2014, 18:39 GMT
---update---
Issue now resolved following Alex's suggestion to install the latest virtualbox extension pack.
It appears that the older extension pack (virtualbox-extension-pack-4.3.10-2) was incompatible with virtualbox 4.3.16.
After installing virtualbox-ext-oracle-4.3.16-1 from AUR, the issue went away.
Virtualbox 4.3.16 is now perfectly working just like before. Thank you Alex.

---end update---

After upgrading to the current version, I also got the "Aborted" issues when trying to run either Windows or Linux guests.

These are my dmesg log:

vboxdrv: Successfully loaded version 4.3.16_OSE (interface 0x001a0007).

EMT[1264]: segfault at 618 ip 00007ffa15bd1da1 sp 00007ffa48ca5ca0 error 4 in VBoxDD.so[7ffa15b25000+178000]
[ 232.056786] EMT[1351]: segfault at 618 ip 00007f87e1eaeda1 sp 00007f8814f38ca0 error 4 in VBoxDD.so[7f87e1e02000+178000]
[ 286.361331] EMT[1494]: segfault at 618 ip 00007ff4fb238da1 sp 00007ff5262ecca0 error 4 in VBoxDD.so[7ff4fb18c000+178000]
[ 389.311561] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
[ 405.276218] EMT[1725]: segfault at 618 ip 00007ff741f36da1 sp 00007ff774fbfca0 error 4 in VBoxDD.so[7ff741e8a000+178000]
[ 416.677509] EMT[1815]: segfault at 618 ip 00007fae8adb8da1 sp 00007faeb9e22ca0 error 4 in VBoxDD.so[7fae8ad0c000+178000]
Comment by Janne Rönkkö (jroo) - Sunday, 14 September 2014, 06:42 GMT
Updating virtualbox-extension-pack resolved the issue for me also. I had version 4.3.0 installed...

Loading...