#1049 closed System Defect (fixed)

virtualbox-ose segfaults

Reported by: gour Owned by:
Priority: major Milestone:
Component: System Configuration Version: 10.0-RELEASE
Keywords: Cc: trac-bugs@…


After latest pcbsd-base update Virtualbox stopped working, iow. it segfaults:

fish: Job 1, “VirtualBox ” terminated by signal SIGSEGV (Address boundary error) }}

or dmesg message

pid 98405 (VirtualBox), uid 1001: exited on signal 11

In the beginning I was told it's the memory issue. but after resolving that one Bernhard told me on #freebsd-vbox about possibility to use jkim's port (https://svn.redports.org/jkim/emulators/),
but I'm reluctant to do it considering that PC-BSD is shipping VirtualBox? with the base OS which is another questionable decision, imho.

The issues, according to http://lists.freebsd.org/pipermail/freebsd-emulation/2013-December/011171.html, seems to be mixing of gcc & clang-compiled code and the workaround explained here http://lists.freebsd.org/pipermail/freebsd-emulation/2013-November/011050.html is only for KDE users while I use i3 wm.

Please advise what to do?

Change History (4)

comment:1 Changed 18 months ago by kris

Are you using the EDGE or Production package set on 10.0? I'm using the latest Production here, and virtualbox is working just fine..

comment:2 Changed 18 months ago by gour

Are you using the EDGE or Production package set on 10.0?


comment:3 Changed 18 months ago by gour

Just to confirm that downgrading to Production solved my issue on both netbook & desktop machines, but it remains that Edge is severely broken in regard to Virtualbox.

Last edited 18 months ago by gour (previous) (diff)

comment:4 Changed 18 months ago by joshms

  • Resolution set to fixed
  • Status changed from new to closed

Kris replaced ports virtualbox-ose* with the jkim version from redports, should
fix the segfault issues we are seeing.


Note: See TracTickets for help on using tickets.