Virtualbox Segfault on Startup

reefland · 2014-09-13 16:29:05

I'm aware of thread https://bbs.archlinux.org/viewtopic.php?id=185841 but I'm not getting a kernel panic nor am I using NTFS.

Core i7 based desktop, 16GB ram, loading VM image over NFS stored on FreeNAS. Configuration has been in place for many months without issues. After recent pacman update I started running into this problem.

VirtualBox starts up fine. Within about 10 seconds of starting the VM I get the message below and the window simply closes.

This is all I'm showing:

[54193.536689] capability: warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
[54199.509258] device enp3s0 entered promiscuous mode
[54217.509587] EMT-0[4260]: segfault at 618 ip 00007fbb534b9da1 sp 00007fbb77453cb0 error 4 in VBoxDD.so[7fbb5340d000+178000]

uname -a:
Linux dldsk01 3.16.2-1-ARCH #1 SMP PREEMPT Sat Sep 6 13:12:51 CEST 2014 x86_64 GNU/Linux

yaourt -Qs virtualbox:

community/virtualbox 4.3.16-1
community/virtualbox-host-modules 4.3.16-1

transcendev · 2014-09-13 18:08:12

I don't have an answer, but I'm having the exact same problem and getting that same message.

infiniphunk · 2014-09-13 19:00:57

I'm also having a bizarre problem with VirtualBox all of a sudden after this last update.

bartonc · 2014-09-13 19:04:22

I was beginning to think that this was unique to my system which is:
* Windows 7 Pro guest (aero enabled)
* 9.9.1. 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
$ dmesg | grep -Ei "virtualbox|vbox|promiscuous"

[    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.
I've posted in the Board index ‹ General ‹ VirtualBox on Linux Hosts forum
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)

@transcendev and @infiniphunk
Pleage give us your specs. Maybe there's some commonality we can key in on. Thank you.

Last edited by bartonc (2014-09-13 20:06:09)

transcendev · 2014-09-13 19:04:43

I'm trying a complete re-install to see if that helps...though, I'm guessing it's something about the latest update itself.

bartonc · 2014-09-13 19:13:28

Do this first!
sudo pacman -U /var/cache/pacman/pkg/virtualbox-4.3.14-3-x86_64.pkg.tar.xz

Last edited by bartonc (2014-09-13 19:15:19)

transcendev · 2014-09-13 19:16:21

Unfortunately, I'd already cleared my cache...I keep running low on space. Don't suppose you could email me that package!? Re-install didn't work.

transcendev · 2014-09-13 19:17:26

Nevermind, found in an archive. We'll see if that fixes things.

transcendev · 2014-09-13 19:19:45

Downgrading worked a treat. Thanks for the idea!

Mr Green · 2014-09-13 19:51:35

I had to downgrade for one minute I thought my awesome isos were borked....

midixinga · 2014-09-13 23:01:27

bartonc wrote:

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

You know that virtualbox-extension-pack is removed in AUR ?
You should use virtualbox-ext-oracle.

I don't know, if this helps

bartonc · 2014-09-13 23:54:35

midixinga wrote:

You know that virtualbox-extension-pack is removed in AUR ?
You should use virtualbox-ext-oracle.
I don't know, if this helps

This is indeed the answer. Thank you.
I had guessed by reading my own post.
New VirtulalBox Extensions in AUR
That did the trick. I'm current on all packages an things are working again.

bulletmark · 2014-09-14 05:06:19

@midixinga, thanks for that tip.

Geez, this change wasn't well managed? All our VM's suddenly start aborting until we stumble across a random post in the forums. This change should have warranted a post on the Arch news page I would think.

I also found that I suddenly lost my membership of the vbosusers group, presumably related to this change also.

bartonc · 2014-09-14 06:33:52

bartonc wrote:

This is indeed the answer. Thank you.
I had guessed by reading my own post.
New VirtulalBox Extensions in AUR
That did the trick. I'm current on all packages an things are working again.

I even got a mod on the Oracle forum to state

I can tell you that the extension pack *must* match the running version

But...
There seems to be a regression on the Oracle side that break Direct3D.
I run Windows 7 VM with 3D acceleration on and use the "tick [] Direct3D Support checkbox then answer {No} in the virtualbox-guest-iso setup dialog" trick in order to get Aero working.
That breaks with this update. I'm currently reverting back to 4.3.14-4. We'll see how that goes.

UPDATE: I've got Aero back after reverting the virtualbox package to 4.3.14-4 and doing a custom PKGBUILD of virtualbox-ext-oracle .
I've commented in the Oracle forum here
NOTE: virtualbox-host-modules version is still 4.3.16-1.

In summary:

$ pacman -Qi $(pacman -Qsq virtualbox) | grep -Ei "name|version"
Name           : virtualbox
Version        : 4.3.14-4
Name           : virtualbox-ext-oracle
Version        : 4.3.14-1
Name           : virtualbox-guest-iso
Version        : 4.3.14-1
Name           : virtualbox-host-modules
Version        : 4.3.16-1

I do know that virtualbox-guest-iso 4.3.16-1 works, but I've downgraded for greater consistancy.
Hope all this helps someone,
Barton

Last edited by bartonc (2014-09-14 08:02:50)

midixinga · 2014-09-14 07:45:52

bartonc wrote:

There seems to be a regression on the Oracle side that break Direct3D.
I run Windows 7 VM with 3D acceleration on and use the "tick [] Direct3D Support checkbox then answer {No} in the virtualbox-guest-iso setup dialog" trick in order to get Aero working.
That breaks with this update. I'm currently reverting back to 4.3.14-4. We'll see how that goes.

Hmm, I have:

community/virtualbox 4.3.16-1
local/virtualbox-ext-oracle 4.3.16-1
community/virtualbox-guest-iso 4.3.16-1
community/virtualbox-host-modules 4.3.16-1

and also run Windows 7 as guest.
But I installed the virtualbox guest editions ISO with basic 3D Support in safe mode

For me that works, Aero is enabled, dxdiag says: 3D Acceleration: enabled

bartonc · 2014-09-14 08:36:40

midixinga wrote:

Hmm, I have:
community/virtualbox 4.3.16-1
local/virtualbox-ext-oracle 4.3.16-1
community/virtualbox-guest-iso 4.3.16-1
community/virtualbox-host-modules 4.3.16-1
and also run Windows 7 as guest.
But I installed the virtualbox guest editions ISO with basic 3D Support in safe mode
For me that works, Aero is enabled, dxdiag says: 3D Acceleration: enabled

Thanks. I gave the old safe mode install a shot to no avail.
Answering {Yes} to "Install Basic blah blah" has never worked for me.
Answering {No} is what works for me and that doesn't require safe mode.
=> Reverting back to 4.3.14-something (again). <=

FYI My Desktop with Aero on

Last edited by bartonc (2014-09-14 09:06:05)

Mr Green · 2014-09-14 11:26:35

Usaully grab extension pack from Virtualbox site, so problem might be down it not being the right version. Will try it later see if that solves the problem. As with anything outside of repos or in aur it not supported by arch itself...

midixinga · 2014-09-14 11:49:53

bartonc wrote:

Thanks. I gave the old safe mode install a shot to no avail.
Answering {Yes} to "Install Basic blah blah" has never worked for me.
Answering {No} is what works for me and that doesn't require safe mode.
=> Reverting back to 4.3.14-something (again). <=
FYI My Desktop with Aero on

Ok, I also tried the WDDm-Driver (whatever it means I hate Windows, especially the system control thing: I never know, what I'm doing)

It works, but it slows down Performance, Image:

https://dl.dropboxusercontent.com/u/901 … 3_16_1.png

hb860 · 2014-09-15 18:41:54

The same issue happened to me just now with Win8 guest VM.
Rolled back to 4.3.14-3
Damn.

bigcajun · 2014-09-17 05:45:44

Sorry if this turns out to be not related, but I had issues with my Windows XP (32-bit) guest after the upgrade to VirtualBox 4.3.16. It wouldn't boot even in Safe Mode. I looking at settings and, just to see, I turned off the EHCI setting for USB. That allowed my VM to boot again. When I toggled it back on (enabled EHCI), the VM crashed at startup again.

I downgraded VirtualBox back to 4.3.14 and my VM boots with EHCI enabled again. I suspect an upstream regression in 4.3.16.
Maybe this one: https://www.virtualbox.org/ticket/13320
or possibly this one: https://www.virtualbox.org/ticket/13085

Again, not sure if my issues and workarounds are related, just wanted to post what I had done.

UPDATE: As posters below state, I had an older version of the extension pack (4.3.10) manually installed. Updating that fixed my issues and I can boot my Windows VM with EHCI enabled.

Last edited by bigcajun (2014-09-19 16:03:36)

gkralik · 2014-09-18 09:49:16

Had the same segfault after upgrading to 4.3.16. Turns out I had manually installed the extension pack from the Virtualbox website and therefore I still had version 4.3.10 of the extension pack installed. After removing the pack and reinstalling version 4.3.16, everything works fine.

hb860 · 2014-09-18 16:23:20

gkralik wrote:

Had the same segfault after upgrading to 4.3.16. Turns out I had manually installed the extension pack from the Virtualbox website and therefore I still had version 4.3.10 of the extension pack installed. After removing the pack and reinstalling version 4.3.16, everything works fine.

Did the same, can confirm it works now.

skylla · 2014-09-20 10:21:54

hb860 wrote:

gkralik wrote:
Had the same segfault after upgrading to 4.3.16. Turns out I had manually installed the extension pack from the Virtualbox website and therefore I still had version 4.3.10 of the extension pack installed. After removing the pack and reinstalling version 4.3.16, everything works fine.
Did the same, can confirm it works now.

Same for me, but had the extension pack at version 4.3.2 (r90405). I guess the version hasn't been that important in the past, I went through versions 4.3.2, 4.3.4, 4.3.6, 4.3.8, 4.3.10, 4.3.12, and 4.3.14 with the same extension pack without any problems. Works now, thanks.

crobe2 · 2014-09-25 15:55:29

Thanks for this thread!

TheLetterN · 2014-09-26 22:12:10

Chiming in: installing virtualbox-ext-oracle from the AUR fixed the sefgaulting for me. Now I can run my VMs again, yay!

Arch Linux

#1 2014-09-13 16:29:05

Virtualbox Segfault on Startup

#2 2014-09-13 18:08:12

Re: Virtualbox Segfault on Startup

#3 2014-09-13 19:00:57

Re: Virtualbox Segfault on Startup

#4 2014-09-13 19:04:22

Re: Virtualbox Segfault on Startup

#5 2014-09-13 19:04:43

Re: Virtualbox Segfault on Startup

#6 2014-09-13 19:13:28

Re: Virtualbox Segfault on Startup

#7 2014-09-13 19:16:21

Re: Virtualbox Segfault on Startup

#8 2014-09-13 19:17:26

Re: Virtualbox Segfault on Startup

#9 2014-09-13 19:19:45

Re: Virtualbox Segfault on Startup

#10 2014-09-13 19:51:35

Re: Virtualbox Segfault on Startup

#11 2014-09-13 23:01:27

Re: Virtualbox Segfault on Startup

#12 2014-09-13 23:54:35

Re: Virtualbox Segfault on Startup

#13 2014-09-14 05:06:19

Re: Virtualbox Segfault on Startup

#14 2014-09-14 06:33:52

Re: Virtualbox Segfault on Startup

#15 2014-09-14 07:45:52

Re: Virtualbox Segfault on Startup

#16 2014-09-14 08:36:40

Re: Virtualbox Segfault on Startup

#17 2014-09-14 11:26:35

Re: Virtualbox Segfault on Startup

#18 2014-09-14 11:49:53

Re: Virtualbox Segfault on Startup

#19 2014-09-15 18:41:54

Re: Virtualbox Segfault on Startup

#20 2014-09-17 05:45:44

Re: Virtualbox Segfault on Startup

#21 2014-09-18 09:49:16

Re: Virtualbox Segfault on Startup

#22 2014-09-18 16:23:20

Re: Virtualbox Segfault on Startup

#23 2014-09-20 10:21:54

Re: Virtualbox Segfault on Startup

#24 2014-09-25 15:55:29

Re: Virtualbox Segfault on Startup

#25 2014-09-26 22:12:10

Re: Virtualbox Segfault on Startup

Board footer