[Solved] Virtualbox Segfault on Startup

[BartonC]

My system is:
* Arch Linux host
* Windows 7 Pro guest (aero enabled)
* Using a raw host hard disk from a guest
* UEFI running a VM that was created on an MBR machine a few years back
* Core i5 with 8GB RAM
* $ uname -a
Linux Bridger 3.16.2-1-ARCH #1 SMP PREEMPT Sat Sep 6 13:12:51 CEST 2014 x86_64 GNU/Linux
This is an ongoing discussion in the Arch users forum but I'm not allow to post URLs yet.
Index
» Applications & Desktop Environments
» Virtualbox Segfault on Startup


$ dmesg | grep -Ei "virtualbox|vbox|promiscuous"

Code: Select all

[    3.677087] vboxdrv: Found 4 processor cores.
[    3.677479] vboxdrv: fAsync=0 offMin=0x5a7 offMax=0x77ab
[    3.677556] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[    3.677557] vboxdrv: Successfully loaded version 4.3.16_OSE (interface 0x001a0007).
[    4.114823] vboxpci: IOMMU not found (not registered)
[   49.307100] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[   58.368772] device enp0s25 entered promiscuous mode
[   82.888110] EMT-3[739]: segfault at 618 ip 00007f4712038da1 sp 00007f47335fbca0 error 4 in VBoxDD.so[7f4711f8c000+178000]
[   82.962541] device enp0s25 left promiscuous mode

I downgraded ONLY the virtualbox package back to 4.3.14-3 to get running again so this may be an Oracle issue more than an Arch issue.
Installed packages are
virtualbox 4.3.14-3
virtualbox-extension-pack 4.3.12-1
virtualbox-guest-iso 4.3.16-1
virtualbox-host-modules 4.3.16-1

With the VM running again, I installed the guest ISO on the guest machine (no help there).
I've also tried disabling 3D accelleration to no avail.
(I have not tried disable the graphics whatnot that got aero working)

UPDATE: This is an ArchLinux packaging issue. I'll be discussing broken 4.3.16 Direct3D Support in a new topic once I find the correct place to post.

[BartonC]

The trouble lies in the line:

virtualbox-extension-pack 4.3.12-1

Arch package may need some tweaking if the Extension Pack is a new dependancy of the virtualbox package.
Thanks for any input that you all have...

[Perryg]

I can't talk about the Arch package as it is theirs and we don't support it, but I can tell you that the extension pack *must* match the running version.

[BartonC]

I can't talk about the Arch package as it is theirs and we don't support it, but I can tell you that the extension pack *must* match the running version.

Thank you for that info. It's interesting that I had gotten away with a broken package after the last update to .14.

PS I'm new to the forum. Is there a way to "mark as answer/answered"? I'm not seeing straight off.

[Perryg]

Edit the topic subject

[isudoajl]

The trouble lies in the line:

virtualbox-extension-pack 4.3.12-1

Arch package may need some tweaking if the Extension Pack is a new dependancy of the virtualbox package.
Thanks for any input that you all have...

8 years later this post save my life... Suddenly all my VMs stopped working, the problem was solved just updating the virtualbox-extension-pack.

[scottgus1]

The Extension Pack version must always match the Virtualbox version.