Virtualbox addition in FreeBSD -current guest OS?
Mark Johnston
markjdb at gmail.com
Fri Apr 26 17:44:11 UTC 2013
On Fri, Apr 26, 2013 at 11:07:35AM -0400, Glen Barber wrote:
> On Fri, Apr 26, 2013 at 11:02:10AM -0400, Mark Johnston wrote:
> > On Fri, Apr 26, 2013 at 10:49:55AM -0400, Glen Barber wrote:
> > > On Fri, Apr 26, 2013 at 10:45:19AM -0400, Viren Shah wrote:
> > > > I was having problems compiling the virtualbox guest additions on a FBSD
> > > > -current (Apr 23 20:30 EDT) system. I changed all the VM_OBJECT_LOCKs to
> > > > VM_OBJECT_WLOCKs (and same for the UNLOCKS) and added rwlock.h to the
> > > > includes. That enabled it to compile but I'm having problems getting X
> > > > started (it just hangs) using those vbox modules for xorg. Log msg (see
> > > > attached) says "failed to initialize VirtualBox device (rc=-102)"
> > > >
> > > > Anyone having recently compiled the vbox ose-additions on a -current system
> > > > and had it work? I'm just trying to figure out if this is a
> > > > -current-related issue or a vbox related one.
> > > >
> > >
> > > This was fixed months ago, I think. Is your ports tree updated?
> >
> > As far as the compilation issue goes, the virtualbox-ose-kmod port is
> > indeed fixed but virtualbox-ose-additions is still broken on current
> > with the latest ports tree.
>
> *sigh*... Is this broken "again" or broken "still" ?
Looks like the latter based on the port's revision history. It was just
never fixed when the lock changed to a rwlock.
More information about the freebsd-current
mailing list